Goal: Identify schedule problems

After your project begins and you are tracking the actual progress of tasks, you can review your schedule to identify problems or potential problems with task schedules. Identifying or anticipating problems enables you to take care of any issues that may affect the project's finish date.

Tip: This article is part of a series of articles within the Project Map that describe a broad set of project management activities. We call these activities "goals" because they are organized around the project management life cycle: Build a plan, track and manage a project, and close a project.

Analyze your schedule After you create a basic schedule, you should check it to discover problems or oversights that require adjustments.

Click all of the following that apply:

Analyze project and resource performanceby using Microsoft Office Project Server 2007. You can create a PivotChart or PivotTable report to help you analyze the schedule for resource or project problems.

Review the progress of your schedule to see how its tasks are affecting the finish date.

Assess why the project finish date is delayed Review the factors in the schedule that could extend the finish date of your project.

Click all of the following that apply:

Show the critical path to quickly find problem tasks. Tasks that fall on the critical path have a powerful effect on your schedule, because a delay of a critical task extends the finish date. Because the critical path may change as you modify your schedule, showing the critical path for your schedule helps you make decisions about what changes to make and how those changes affect the critical path.

Examine task constraints to see if they are necessary. Unnecessary task constraints can limit the flexibility of your schedule by forcing tasks to start on certain dates or to use all available slack. If you eliminate unnecessary constraints, Microsoft Office Project 2007 schedules tasks based on their durations and relationships to one another.