# Before You Set a Baseline

Because the baseline will provide the reference points against which you compare actual project progress, it should include your best estimates for task duration, scheduling, resource allocation, costs, and the other project variables you want to monitor.

Baseline information that consistently differs from actual data shows that your original plan is inaccurate. If this is the case, don’t worry. At any time during the project you can modify or rework the baseline.

To help ensure that your baseline information is as accurate as possible, it’s a good idea to double-check your project file, even if you’ve already spent a week fine-tuning it. Checking the following items will help ensure that your baseline information is accurate:

- The project start and end dates have been approved.
- Working times calendars have been adjusted for the project, all groups, and each individual.
- The task list is complete.
- The resource list is complete.
- At least one resource is assigned to each task (except milestones).
- The workload is evenly distributed by resolving any resource overallocations.
- The critical path has been shortened as much as possible.
- Each task link reflects the true task sequence. For example, if two tasks can start at the same time, they are linked with a start-to-start dependency.
- No unnecessary contraints have been applied to any tasks.
- All unnecessary slack time has been cut from tasks, and slack remains only in those parts of the schedule where it’s needed.
- Estimated project costs are within budget.

For information about how to accomplish the tasks on this list, as well as other schedule refinements, read chapters 10 through 13 in Part 3, "Making Your Schedule Lean and Mean."

©1996-1997 Microsoft Corporation. All rights reserved.