Change Control and Schedule Updates

The primary purpose of creating multiple schedule baselines in project management is to capture progressive schedule changes and track project evolution over time. This is crucial because:

1. It provides a historical record of how the project schedule has evolved
2. It enables measurement of schedule variances and trends
3. It helps in performance measurement and tracking
4. It supports project documentation requirements
5. It aids in lessons learned and organizational process assets

The other options are incorrect because:

• Managing different stakeholder requirements is handled through stakeholder management and communication plans, not through multiple baselines

• Risk management and contingency planning use schedule risk analysis and contingency reserves, not multiple baselines

• While milestone variations are important, documenting them is a byproduct of baseline management, not its primary purpose

The Performance Measurement Baseline (PMB) combines three fundamental project elements - scope, schedule, and cost - into a single integrated baseline used for measuring project performance. This integration is essential for earned value management and effective project control.

This is the correct answer because the PMB serves as the key reference point against which all project performance is measured, enabling project managers to track variances and make informed decisions.

The other options are incorrect because:
- Having multiple reference points across milestones does not accurately describe the PMB's integrated nature
- The PMB is not primarily about defining acceptable schedule deviations or historical data
- The PMB is not limited to critical path activities; it encompasses the entire project scope, schedule, and cost baseline

In an agile-hybrid project environment, rolling wave planning with periodic baseline updates at the release level is the most appropriate approach because:

It balances agile flexibility with traditional project control needs by:
- Maintaining high-level schedule control at the release level
- Allowing for adaptive planning within sprints
- Providing appropriate timing for baseline updates
- Supporting progressive elaboration of project details

Why other approaches are less effective:

Establishing a complete baseline at project inception is too rigid for agile environments and limits the ability to adapt to changes.

Updating the baseline after every sprint creates unnecessary overhead and diminishes the baseline's value as a measuring tool for project performance.

Creating separate baselines for each sprint and consolidating at the end defeats the purpose of baseline control and makes it impossible to track progress effectively during the project.

The optimal solution provides the right balance between control and flexibility, allowing teams to maintain agile practices while ensuring proper schedule governance.