Creating a Forward and Backward Pass Project Management Template

Written by:  • Edited by: Ronda Roberts
Updated May 8, 2010
• Related Guides: Microsoft

A forward and backward pass template is useful for estimating a project's schedule and determining if there is any float time for completing the project. To catch a glimpse of what a forward and backward pass template looks like in a project manager's playbook continue reading more of this article.

Calculating and Executing a Forward and Backward Pass

When constructing a project schedule, a project manager can draw upon a score of strategic lessons from the game of football. For example, in wearing the hat of team coach, the project manager has at his fingertips a dynamic playbook of offensive and defensive moves to keep the project on schedule. During the early stages of the game, the project manager's focus is on developing realistic estimates for the project's schedule. The estimation process is accomplished by pulling from one of the early chapters of the playbook two essential plays: the forward pass and the backward pass. Analogous to the two minute drill, the forward pass is the best strategy for quickly driving the ball to the goal line or in the case of a project to the completion date. Each task represents a first down marker and the forward pass pushes the ball along the schedule in the least amount of time. A forward pass is executed by calculating the early start and the early finish for each task of the project. The early start is the earliest point in time when a task can be started. The early finish is the earliest point in time that a task could be finished. However, sometimes the forward pass is not the best strategy, particularly when the defense rushes the quarterback. In this case, the project manager needs to execute a backward pass to see if there is enough slack time to allow for a different set of plays and still get the project to the goal line before time expires on the clock. In constructing a backward pass, the project manager reverses the process to determine the late start and the late finish for each task in the project and remain in regulation time. The late start date is the latest point in time when a task can be started. The late finish is the latest point in time that task could be finished.

Constructing the Forward and Backward Pass Project Management Template

You can easily constructing a forward and backward pass template in Microsoft Word by following these steps:

  1. To create the template which is illustrated below and in a downloadable version in the Project Management media gallery, open a Word document and insert an organizational chart.
  2. Choose the primary color style.
  3. Create levels to reflect predecessor and successor tasks.
  4. Fill-in values for each task's early start and early finish. Begin with Task 1 and label the early start (abbreviated ES on the template) as Day 0.
  5. Add the estimated duration of the task to the early start to calculate the early finish (abbreviated EF on the template).
  6. Label each successor task's ES as the EF of the predecessor's task.
  7. Where you have more than one predecessor for a task, use the later EF as the ES for the successor task.
  8. Fill-in values for each task's late start and late finish. Begin with the last task and label the late finish (LF) with the completion day determined by the forward pass.
  9. Subtract the duration from the LF to calculate the late start (LS).
  10. Where you have more than one predecessor for a task, use the later LS as the LF for the predecessor task.

Forward and Backward Pass Template
click to enlarge
Here is an illustration of the forward and backward pass template. Notice that the early start and late start begin at the same time (Day 0) and the late start and late finish end at the same time (Day 30), The difference between the early and late finish of any task is called the total slack or float. Remember that even if the project falls behind, the project manager's playbook still has a number of other options to get the schedule back on track. For more on executing what is known in football as a “no huddle play" continue reading this article to learn more on crashing or compressing the project schedule.


Comments

Showing all 4 comments
 
Banerjee Feb 10, 2012 2:50 PM
RE: Creating a Forward and Backward Pass Project Management Template
Start with 0 and not 1 as ES. Just add the duration and that is your EF. In the successor node, copy the EF from the predecessor as the ES of this node and continue.
Gravity Gardener Mar 28, 2010 7:03 PM
Chunking out a Project
Chunking out a project can help you focus on certain areas to be completed and organize the tasks and activities into workgroups. These workgroups or phases can be a more effective approach in managing the entire project.

Some of the standard project phases can include:

1. Kickoff
2. Discovery
3. Scope definition
4. Development
5. Unit Testing
6. QA Testing
7. User Testing
8. Migration to Production

The phases listed above represent standard project phases that can be used for different implementations.The list can be expanded or broken down even further, depending on the type of project and the type of project you are managing. Slicing up a project into phases is a sound approach that keeps the overall project running smoothly.

http://gravitygarden.com/project101/phases-of-project.html
Ginny Edwards Feb 9, 2010 6:57 PM
Starting Value at Zero Explained
For this template, the focus is on duration. When the first task is begun the duration is zero (labeled Day 0) and the duration of the first task is computed. The second and subsequent tasks are dependent upon any predecessors and cannot begin until all predecessors are completed. The template tracks total duration assuming that the next task starts on the same day that the previous task is completed. The duration for the ES/LS of the new task is essentially zero but retains the value of the EF/LF of the predecessor task to derive the total duration of the project. I hope this approach in thinking about time in terms of duration helps.
TL Feb 9, 2010 5:56 PM
Missing Something
Forward and backward pass calculations in other publications (i.e. HeadFirst PMP) make use of a starting activity value of 1, then use +/- 1 to arrive at their values for ES/EF and LS/LF.

I don't see that listed in your article. Is that because your starting activity has a value of 0 that you've forgone the +/- 1?

With a starting value of 0 for the first activity, and not using any +/-1, all the EF and LF stay the same as if you started with a value of 1.

However, all the ES and LS are different.

Can you explain why you opted for the Starting Value 0 approach?
 
blog comments powered by Disqus
Email to a friend