Home > Sample chapters

Fine-Tuning Task Details in Microsoft Office Project 2007

Viewing the Project’s Critical Path

A critical path is the series of tasks that will push out the project’s end date if the tasks are delayed. The word critical has nothing to do with how important these tasks are to the overall project. It refers only to how their scheduling will affect the project’s finish date; however, the project finish date is of great importance in most projects. If you want to shorten the duration of a project to bring in the finish date, you must begin by shortening (also referred to as “crashing”) the critical path.

Over the life of a project, the project’s critical path is likely to change from time to time as tasks are completed ahead of or behind schedule. Schedule changes, such as assigning resources to tasks, can also alter the critical path. After a task on the critical path is completed, it is no longer critical because it cannot affect the project finish date. In Chapter 15, “Getting Your Project Back on Track,” you will work with a variety of techniques to shorten a project’s overall duration.


A task is on the critical path if its total slack is less than a certain amount—by default, if it is zero. In contrast, noncritical tasks have slack, meaning they can start or finish earlier or later within their slack time without affecting the completion date of a project.

In this exercise, you view the project’s critical path. One way to see the critical path is to switch to the Detail Gantt view.

  1. On the View menu, click More Views.

  2. In the More Views dialog box, select Detail Gantt, and then click the Apply button.

    The project appears in the Detail Gantt view.

  3. On the Edit menu, click Go To.

  4. In the ID box, type 12, and then click OK.

    Project displays task 12, the Production summary task.


    The Scene 3 tasks and later tasks are critical tasks. In the Detail Gantt view, Project distinguishes between critical and noncritical tasks. Critical task bars are red, but noncritical task bars are blue. In this view, you can also see tasks with free slack.

    Notice the Gantt bar of task 18, Scene 7–process dailies. The blue bar represents the duration of the task. The thin teal line and the number next to it represent free slack for this task. As you can see, this particular task has some slack and is therefore a noncritical task. (Remember that the term critical in this sense has nothing to do with the task’s importance, but only with how much or little total slack is associated with the task—and, ultimately, what effect the task has on the project’s finish date.) The slack on task 18 was caused by the Start No Earlier Than constraint applied to task 20. Without that constraint being applied, all tasks in the project would have been critical.

  5. On the View menu, click Gantt Chart.



  • By default, Project defines a task as critical if it has zero slack. However, you can change the amount of slack required for a task to be considered critical. You might do this, for example, if you wanted to more easily identify tasks that were within one or two days of affecting the project’s finish date. On the Tools menu, click Options, and in the Options dialog box, click the Calculation tab. In the Tasks Are Critical If Slack Is Less Than Or Equal To box, enter the number of days you want.

