How to Develop Schedule on Your Project, the True Way!

Develop Schedule processWhat is the single most important document you need to run a project?

Project plan? May be. Project schedule? Possibly. 🙂

Project Plan is like planning for the journey. Preventive maintenance of car, filling up gas, booking beach side vacation home, taking driving directions and route-map, packing bags, and stocking eatables for the journey.

Schedule is what you need when you actually start the journey. Knowing when to change gears, accelerate, brake, stop at gas station, refer to the route-map.

Steps to develop schedule can be tricky, and this post shows the right approach to it.

In this post we are going to cover –

  • How all Schedule management activities done so far comes together to produce the backbone of a project – Project Schedule
  • How the project schedule is developed using schedule method, tool, and model
  • 5 types of schedule
  • Critical path method (CPM) and Critical chain method (CCM)
  • Resource optimization techniques
  • How Leads and Lags are used when you develop schedule
  • How you can compress schedule without impacting critical path (and a mnemonic to remember it!)
  • How scheduling is done in Agile projects
  • and then some more!

This is a historic moment in your project – gathering all the ingredients to chalk out a schedule for your project.

Get a cup of coffee, sit back, and let’s get started!

It all comes together now!

To develop schedule you would need all the outputs created in previous Schedule Management Knowledge Area processes (and then some more) to come up with an effective schedule.

  • Schedule management plan (from Plan Schedule Management process)
  • Scope baseline (from Create WBS process)
  • Activity list, Activity attributes, Milestone list (from Define Activities process)
  • Project schedule network diagrams (from Sequence Activities process)
  • Project team assignments and Resource calendars (from Acquire Resources process)
  • Resource requirements (from Estimate Activity Resources process)
  • Duration estimates, Basis of estimates (from Estimate Activity Durations process)
  • Risk register (from Identify Risks process)
  • And then some more – Assumption log (from Develop Project Charter),
  • Lessons Learned Register (from Manage Project Knowledge process)
  • Agreements (from Conduct Procurements process)
  • Enterprise environmental factors – such as government standards, legal requirements, environmental laws…
  • Organizational process assets – things like holiday calendars, scheduling methodology, schedules from earlier similar projects, tips and lessons given by other project managers

You’ll also need to refer to the holiday calendar and important dates of customer organization while preparing schedule. Schedule gives start and end dates of activities and the milestone dates. If you have a release date coming up during a major holiday season you may not have required person to validate deliverables on customer side. This is important especially if you are running an Agile project.

Know that schedule does not come up right the first time.

We use an iterative approach to develop schedule.

Just because we use outputs from previous processes here we are not set to develop schedule at one go. When you work out the schedule you will unearth some of the inefficiencies in estimating resources or duration of activities. You will find that some activities need more/less time than originally estimated. Some additional resources might be required, or some resources might be redundant.

Some risks may be identified, thereby needing additional duration or resources. You may even get more understanding about few activities and their attributes!

This is one of the reasons why developing schedule becomes an iterative process.

When that happens you simply go back, update corresponding documents, and continue with developing schedule. Do not fret over these changes (which seem to elongate schedule preparation), be glad that you discovered them now. This is probably the golden time to discover any shortcomings in the outputs of previous processes. Cost of changes to schedule is higher as project progresses.

Once you have the schedule, you may discover external constraints such as the need to pull in a certain release date to match customer’s board meeting. There are couple of schedule compression techniques that may help you in doing this, but they come with related risks. We shall see them later.

Before jumping on to tools and techniques let us see the approach for developing schedule.

Also read: Click to discover an simple, uber-effective & free project scheduling tool and guide.

An approach to develop schedule

Study the diagram below. You will notice few components – Schedule method, Scheduling tool, Project specific data and Schedule model.

Schedule Development Methodology
Figure 1: Schedule development methodology

In short, this diagram indicates that you first decide on a scheduling method (such as Critical-path method or Critical-chain method), and use a scheduling tool that is a software based on this scheduling method and then feed project specific data (such as activities, dependencies, resources and durations) into it to create a schedule model. The resulting list of activities with start and end dates is the project schedule – against which project work status is periodically compared.

Let us look into a bit more of each of these components –

Scheduling method

This provides a framework within which schedule models are developed. As we saw earlier, Critical-path method (CPM) and Critical-chain method (CCM) are two popular scheduling methods.

Your organization may already have selected the scheduling method to use on the project. CPM is the most commonly practiced scheduling method.

Exam tip:
PMBOK standard assumes Critical Path Method (CPM) and not Critical Chain Method. In exam if nothing is specified then assume CPM.

Critical path method uses forward pass and backward pass to calculate early start and finish, and late start and finish respectively. Precedence diagramming method (PDM) is used to sequence activities for CPM.

Scheduling tool

Scheduling tool is used to assemble a schedule model and provide means of adjusting parameters.

Usually, scheduling tool has the following capabilities –

  • Select the type of relationship to apply between activities (such as Finish-to-Start, Start-to-Start)
  • Add lags and leads between activities
  • Apply resources and estimates to arrive at dates
  • Apply schedule compression techniques to shorten project duration

Schedule model

Feeding project specific data such as activities, dependencies, resources and estimates into scheduling tool creates a schedule model that is very specific to the project. This model is then used to create schedule that has planned completion dates.

Project schedule

This is a representation of activities, their precedence logic and constraints in order to get a start and end date for the project. While the project specific data within project tool is considered as project tool and the resulting list of activities with start and end dates is considered as project schedule. The same schedule model can create different representation of schedule such as in tabular format, activity bar charts with dates, network logic diagrams with dates and so on.

Five basic types of schedules are –

  • Early start schedule
  • Late start schedule
  • Baseline schedule
  • Resource-limited schedule
  • Target schedule

There are others but they are variations of the above five.

Wait! an awesome video is coming up teaching couple of ways to shorten schedule process…

These are some of the ways to develop schedule on the project

Schedule network analysis

Is a tool that employs rest of the tools and techniques such as critical path method, critical chain method, what-if analysis, and resource leveling to generate the project schedule.

Critical Path method (CPM)

Critical path is made up of series of activities from beginning of the project to the end, where each activity has a dependency over previous activity in such a way that delay in any one activity causes delay in all subsequent activities, causing the project to slip.

It is also defined as the longest sequence of activities that must be completed on time for the project to complete on its due date.

This project modeling technique was developed by Morgan Walker and James Kelly in later part of 1950s. Schedule network diagram is the base for Critical path method. This method helps you calculate the early start and finish, and late start and finishes of activities, without considering resource limitations. This is done by forward-passing and backward-passing through the network diagram respectively.

Knowing early and late starts and finishes of activities that are not on the critical path help you understand the flexibility you have in starting and finishing them without impacting start dates of activities on critical path. Activities on critical path have only one start and one end date (there is no early/late start or early/late end date).

Critical path defines the longest duration for a single network path on the project. Again, none of the activities on critical path can afford to slip without causing delay in the project.

[bctt tweet=”And hence Critical Path is the shortest time that the project can be completed in!” username=”pmexamsmartnote”]

We looked at John’s house building project as example to understand some of the processes – Define Activities, Sequence Activities and Estimate Activity Durations. You may want take couple of minutes and quickly run through them first.

We shall learn how to calculate early start, late start, early finish and late finish dates in the next lesson. In that lesson we shall also learn how to determine critical path on a project.

Here is the critical path for John’s home construction project –

Critical path example
Figure 3: Critical path for John’s home construction project

Click here to understand how to calculate critical path, float of an activity and early/late start and finish dates of activities, using schedule network diagrams.

Critical chain method (CCM)

This method of planning and managing projects was introduced by Eliyahu Goldratt. The essence of this method is to focus on resources of activities instead of start and end dates.

[bctt tweet=”Critical Chain method works based on the premise that resources should be 100% focused on tasks to complete them ASAP.” username=”pmexamsmartnote”]

Planning is done by working backwards from a completion date, with each task starting as late as possible. Typically the project is planned based on 2 types of estimates for every task – 50% probability based ‘best guess’ estimate for an activity, and 90-95% probability based ‘safe guess’ estimate.

In the project plan the ‘best guess’ estimate is considered. Resources are assigned to each task in an aggressive way while ensuring that they do not work on multiple tasks at any given point of time by resource leveling technique.

Now the longest chain of resource leveled tasks from beginning to end is identified as critical chain.

We saw that two types of estimates are taken for each activity – best guess and safe guess. Best guess is taken for project planning. What happens to safe guess estimates? Well, the difference between ‘best guess’ and ‘safe guess’ for all activities on critical chain is treated as buffer at the end of the project.

This sort of buffer is also provided for those paths that lead to (‘feed into’) critical chain path, and called as feeder buffer. This is done in order to make sure that any delay in those activities do not impact the critical chain.

Managing project primary done by watching buffer. Fever charts are created to watch the level of remaining buffer at any point in time. If rate of buffer consumption is low then project is on track. If rate of buffer consumption is high then corrective actions or recover plans are  brought into execution to avoid project slippage.

If you are using critical chain method for planning then it helps to not disclose all buffers to the team, especially the ones on activities. Sometimes people may tend to use the buffer without notice. The ‘cushion’ of knowledge of buffer may go against the principle of critical chain method. Where the onus is to complete the activity as soon as possible without considering its start/end dates.

Resource optimization techniques

There are two types – Resource leveling and Resource smoothing.

Resource leveling

This can be applied only for schedule prepared by using critical path method. This is a means of balancing over-allocated or under-allocated resources across different activities. This technique is also used due to resource constraints where certain critical resources are available only during certain time period and you need to adjust start dates of some activities to adjust to this resource availability.

The other scenario could be when only one person has a specific skill set and due to this two activities which otherwise could have been done in parallel, need to be now sequenced.

Due to resource leveling critical path may get longer, increasing project completion time. Resource leveling may also bring in a different network path to be the new critical path!

Resource smoothing

Resource smoothing is about utilizing free and total floats in order to juggle resources between different activities. Due to this technique there is no impact on critical path, hence project completion date remains unchanged. Since we play within the limit of available floats, we may not be able to optimize all the resources.

Check out: Use special discount code OCT20 to get the most popular PMP® preparation course that has helped over 49889+ pass the exam!

Data analysis

What-if scenario analysis

This is about finding out what impact will an adverse event have on project schedule. This is a step further from the assumptions we consider from project charter, scope statement, and requirements documentation. This is about trying to figure out what all can go wrong and what additional planning might be required to manage eventuality.

For a skilled-labor intensive project, what if there is a labor strike?

For a project that uses high end expensive machinery, what if there is a bad breakdown of the machinery?

For an infrastructure based project (like constructing a dam or bridge), what if there is a natural calamity like flood?

You get the idea.

Some projects use computer based Monte Carlo Analysis technique that model uncertainty based on given inputs using a specific algorithm.


Simulation is usually done using software, which calculates multiple project durations making different activity assumptions using a probability distributions to account for uncertainty. Monte Carlo analysis is one such simulation technique.

Leads and Lags

We saw how leads and lags are applied, in Sequence Activities process.

Do you love mnemonics? Watch this video to understand Lead and Lag in a way that you will NEVER ever forget! 🙂

[su_button url=”” style=”3d” background=”#f66c10″ color=”#fefcfc” size=”8″ wide=”yes” center=”yes” icon=”icon: heart” icon_color=”#f52223″ text_shadow=”1px 0px 0px #645757″]Liked this video? Subscribe to get such brain-friendly PMP® videos![/su_button]

Schedule compression

Important thing to keep in mind is that schedule compression should not change the project scope.

There are 2 types of schedule compression techniques available when it comes to develop schedule on the project.


Crashing is simply putting more resources on activities to reduce duration, and hence bring in overall project completion date. Analysis is done to determine how activities can be completed quicker by incurring least amount of additional cost.

This will help only when the nature of activity allows to add more resources and reduce duration. This method of schedule compression may increase project cost and risk. And it may impact quality if execution is not managed properly.

Few examples are – asking team to work additional hours, or getting new resources to work on tasks, or paying people to complete tasks quickly.

Let us consider the earlier example. John could get multiple excavators and more people to quickly dispose the dug soil, hasten Dig Earth task and start the Pour Footings task early.

Fast tracking

Fast tracking is about running multiple activities, or even project phases, in parallel to each other (or with some overlap) in order to reduce project duration.

This technique will not work when two activities have hard dependency (you cannot test a component unless it is manufactured). This can also be a risky approach because when activities are done in parallel their dependencies are managed by making certain assumptions. If assumptions are proven to be wrong, there will be rework, leading to additional cost and lost time.

In our example, John could start on excavation as soon as base planning is complete, and continue blueprinting and excavation in parallel. However, if planning exercise changes foundation plan then there may be rework of excavation. This may increase cost as well.

[bctt tweet=”Use this mnemonic to remember Fast tracking and Crashing: Schedule compression techniques!” username=”pmexamsmartnote”]

Do you love mnemonics? Watch this video to understand Fast tracking & Crashing in a way that you will NEVER ever forget! 🙂

[su_button url=”” style=”3d” background=”#f66c10″ color=”#fefcfc” size=”8″ wide=”yes” center=”yes” icon=”icon: heart” icon_color=”#f52223″ text_shadow=”1px 0px 0px #645757″]Come, join me in PM Exam Last Mile Prep Program & get certified in 6-8 weeks![/su_button]

Here are the 3 questions you must ask yourself before crashing a schedule –

PMIS – Project Management Information System

PMIS plays an important part when it comes to develop schedule. This includes scheduling software which can provide flexibility in not just coming up with a schedule but also changing dates and constraints. Schedule compression can also be done using the software and impact on critical path can be visualized.

Pass PMP exam before the new & harder exam rolls in..

Work one-on-one with Shiv every week, fast track your progress, and pass with confidence.

[su_button url=”” style=”3d” background=”#f66c10″ color=”#fefcfc” size=”7″ wide=”yes” center=”yes” icon=”icon: heart” icon_color=”#f52223″ text_shadow=”1px 0px 0px #645757″]Click to join the most brain-friendly PMP® preparation program, today![/su_button]

Agile release planning

Over 70.5% of organizations report using Agile approaches either as a short term or long term project management method, Project Management Institute reports.

That’s a brave move over from traditional method a majority of organizations lapped up without batting an eyelid just a decade ago.

Why not, agile solves most of the problems of Waterfall method. It gives more flexibility, visibility, and control over change that every business seeks today.

With that kind of mass adoption Agile schedule planning takes the center stage when it comes to managing projects.

Scrum master takes an incremental, top-down approach – along with the team – to develop schedule on agile projects.

Here’s how it is typically done –

  • The Release Schedule typically covers 6-8 months, spanning high-level chunks of user stories (or Epics, for larger chunks of work).
  • A Release contains Iterations (or Sprints) – typically of 3-4 weeks duration.
  • The above arrangement gives product owner, scrum master, and the team to decide which features need to be developed in which order. This is based on the business needs, dependencies, and limitations (nascent technology, availability of high-skill resources and so on).
  • A Release Plan allows prioritization and allocation of user stories across multiple Iterations. The priority, size, and even iteration duration can be changed based on how things shape up as you go along, and what lessons are learned along the way.
  • A the beginning of each Iteration, the team does Iteration planning. It prioritizes user stories and breaks them down Tasks, assigns to members, and estimates them in terms of story points.
  • And they work as a cohesive, collaborative, single unit to get the work done.

With one or more of the above you have..

Schedule baseline,

A schedule baseline is an approved version of the schedule model with start and end dates. You use change control process to make changes to schedule baseline. Also, the team will be clear as to which schedule it should look at and follow at any point in time.

Project schedule,

This can be done in a simpler form or detailed form. It can be descriptive or graphical/chart based.

Some of the components of a schedule are –

  • Milestone charts – a time-scale chart showing important milestones, their expected dates and any external interfaces.
  • Bar charts – indicating start and end dates of major activities or modules on the project.
  • Schedule network diagrams – can be activity-on-node or precedence-diagramming-method we saw in Sequence Activities process. This can be represented as a Gantt chart.

Whichever way you create the schedule you need to ensure that team understands it. And all stakeholders can read and follow it quite easily. This will free up a lot of time for you as project manager in explaining people. And may even help people identify brewing issues on their own!

Schedule data,

This refers to are all the data generated during schedule creation approach. This can include activities, activity attributes, milestones, information about external interfaces and dependencies, assumptions (from what-if analysis) and constraints, schedule network diagrams, resource requirements and alternative schedules. These will be required when you control changes to schedule as well.

Project calendars,

This is a list of working days available for scheduled activities on the project.

..and updates to Project management plan

Lot of data is churned when you develop schedule. A good amount of additional, missing, or even redundant data in previously created project documents can be discovered. All these documents may need to be updated now. Changes may be required to documents such resource requirements, activities and their attributes, assumption log, as calendars, risk register.

I know, it’s been a lot in this post. Develop schedule process can feel daunting. But by following the steps given in this series of posts, you would have gained all the required ammunition to confidently create your project schedule.

You may need to take a break now and scan back this lesson to get a better hang of how scheduling is approached.

This post should help you answer about 10-15 questions on the exam, so every minute you spend on this is worth it’s marks in gold. 🙂

With the major part behind us, let us move on and see how a changes to your schedule is controlled in the project.

[SneakyAffiliate sneakyaffiliateurl=”https%3A//” sneakyaffiliatecookiexpdays=”1″ sneakyaffiliatesplash=”Are%20you%20sure%20you%20want%20to%20leave%20before%20you%20checkout%20special%20PM%20PrepCast%20sale%20by%20Cornelius%3F”] [/SneakyAffiliate]

like the post

<-- Liked this post? Help your friends by sharing this using social network buttons. Thanks for being awesome!

OSP sidebar

PMP Study Books

Help Run This Blog At No Cost To You.. Use this box to search and purchase your stuff on Amazon. Thanks!

{ 2 comments… add one }
  • Kenan May 26, 2013, 8:41 pm

    Shiv, i think there is a duplication in What if scenario paragraph. You used the term project charter twice.

    This is about finding out what impact will an adverse event have on project schedule. This is a step further from the assumptions we consider (from project charter, scope statement, and project charter)…

    • Shiv May 28, 2013, 8:42 pm

      Thanks Kenan for pointing this out. Now corrected.