The project’s baseline is used to measure how performance deviates from the plan. Your performance measurement would only be meaningful if you had an accurate baseline. A project’s baseline is defined as the original scope, cost, and schedule. The project’s baseline must be completely defined and documented before project execution and the control activities begin.
Once the project execution begins, the project’s baseline is put under change control to help in evaluating any further changes and their impact on the project. No meaningful measurements can be made if the scope, cost, and schedule are not under strict change control. If any change is approved, then the new baseline is redefined (with the change incorporated into it) as the original plan. It is a good idea to keep records that show how the plan has progressed and changed over time.
Frequent requests for changes to the project requirements may indicate that the initial requirement analysis was incomplete or there was a lack of meaningful communication with users and customers early in the project initiation phase.
Sciforma supports the capture of fourteen independent baselines in the project so that a history of significant project changes can be captured.
In order for Sciforma to compare current data with data saved within a specific baseline, users will have to select a Current Baseline.