project schedule

How to Create an Effective Project Schedule

February 15, 2018 by

Whilst planning your project schedule and timelines is no easy feat, getting the plan as right as possible before work commences is vital. After all, the plan will help you allocate resources, provide a baseline for performance management, and enable tracking as the project progresses.

Of course, if you do develop a well-considered plan, you also need to work hard to ensure your team sticks to it.

 

Plan and manage your project schedule in SharePoint with a free template

 

In this article, I’ll suggest a 10-step planning process and eight tips for helping your team maintain the schedule.

 

10 Steps for Developing Your Project Plan

1. Gather inputs

Before you plan, you should refer to the project statement to understand the scope and goals of the project, resources, stakeholder expectations, and proposed schedules.

If any risks were documented during the project initiation stage, review these risks so you can decide how much contingency to include in your schedule.

Next, check in with the proposed team to figure out who is responsible for the deliverables, required tasks and phases, and the expected duration of key tasks or phases.

You should also confirm if team members are working on multiple projects or have any upcoming vacation as these commitments could reduce availability.

 

2. Plan milestones and stages

With this information, you can plot key milestones and project phases. Milestones are a useful way to track project progress and help to keep the team motivated. Working towards smaller goals is much more realistic and manageable than striving for a final end-date with no checkpoints along the way.

 

3. Work Breakdown Structure

Armed with a broad overview of deliverables, key tasks, and milestones, develop your work breakdown structure. The WBS decomposes proposed work into smaller tasks, managed in chunks of time, for example, two weeks.

Every task has one owner. This improves accountability and resource management as you can quickly check if a task is too big for one person.  If any task doesn’t make sense, now is a good time to check with the task owner or project stakeholder!

Depending on the level of detail in the WBS, you may prefer just to use the document with your team whilst presenting a high-level timeline to project stakeholders.

 

4. Outline tasks

Next, develop an outline schedule for all tasks. If you are using project management software, check the options for developing and updating a schedule.

When plotting tasks, pay particular attention to any dependencies between tasks and between milestones.

A project dependency arises when a task, milestone, or activity is dependent on another task or milestone being completed before it can start or be completed.

There are four key dependency types to look for:

  • Mandatory Dependencies: These are dependencies that are logic driven e.g, a code module cannot be tested until it’s written.
  • Resource-based Planning Dependencies: These tasks could be accomplished faster or sooner if you had more resources.
  • Discretionary Dependencies: These tasks could be scheduled differently, but the project manager has opted for this schedule
  • External Dependencies: These are dependencies outside the control of the project team, but nonetheless, must be reflected in the project schedule. An example of an external dependency is the completion of a project milestone linked to the completion of a milestone within another project.

 

It is a good idea to develop a ‘dependency log’ to record and track dependencies. Information to record includes the project name, task description, and expected timelines.

 

5. Develop the critical path

The critical path charts one path through all tasks and is used to determine the fastest route to finishing the project. It’s essential to managing the execution of the project and reducing scope creep.

To develop the critical path, look at the duration and earliest and latest start and end dates for tasks, and any dependencies.

 

6. Estimate resources

Although you gathered some estimates from the team in an earlier step, it’s a good idea to compare the critical path and WBS against these inputs to confirm resource availability.

Elements to check include:

  • Conflicting project allocation using personal calendars or a resource allocation report in your project management software
  • Commitment to non-project activities
  • Personal vacations and national holidays
  • Dedicated hours to complete a task v the actual timeframe when combined with other responsibilities
  • Team skills and capabilities
  • Any requirements for outsourcing deliverables.

 

7. Document risks

During the project initiation phase and planning steps outlined above, you will likely encounter project risks, for example, task dependencies, or competing resource allocation.

Re-visit and document these risks along with any assumptions that could negatively influence the timelines. An example assumption is how long it will take senior stakeholders to provide critical feedback.

Use this information to add some contingency for dealing with delays, for example, an additional 20% to the overall timeline.

If you are not sure you have considered all risks or how much contingency to add, look at records and reports from similar projects completed within your organization.

 

8. Build the Project Schedule

At this point, you have:

  • Documented tasks and estimated durations, and milestones
  • Developed the work breakdown structure with tasks and owners
  • Identified dependencies using an initial schedule
  • Designed the critical path
  • Estimated resources
  • Noted risks and assumptions.

 

Using this information, plot the schedule for your project and assign tasks to your team!

 

9. Review and adjust with your team

It’s important to step back and review your plan with the team to check for any errors or adjustments needed.

Do dates match with resource allocation? Does every task have an owner? Is this the best person for the work? Have you allowed enough contingency time for risk management?

Depending on the schedule and stakeholder expectations, you may need to deal with the triple constraints of time, quality, and cost. Will you meet the agreed deadline by sacrificing quality or acquiring extra resources? Is it possible to deliver less but to the desired standard? You and the team should decide where to trade off now or later, and document these decisions.

 

10. Periodic Review

Once the project is underway, you will inevitably encounter unexpected delays and disruptions to your schedule.

Set aside some time to review and adjust the plan periodically to reflect these realities.

Depending on your project management software, it should be relatively easy to make these updates and communicate the changes with your team using automated reminders or a project dashboard.  Any significant revisions should be agreed with stakeholders to keep everyone in the loop.

 

8 Ways to Help Your Team Stick to the Schedule

Despite best intentions, your team will struggle to stay on schedule. Here a few suggestions to avoid too much deviation from the timelines!

  1. Assess your team’s strengths and weaknesses so you can assign people to the right tasks.
  2. Set goals with realistic timelines and manageable chunks of work.
  3. Host a kick-off meeting to ensure the team understands the plan before starting the project.
  4. Use collaboration tools for real-time communication, tracking and reporting.
  5. Celebrate milestones!
  6. Limit the number of tasks allocated to a team member at any time to encourage deep focus work and high-quality results.
  7. Set a feasible meeting schedule with your team, and make sure these meetings start and end on time.
  8. Ensure accountability by explaining how you will address missed deadlines with relevant team members.

 

Image credit

Pin It on Pinterest

Share This