Change Control in Adaptive and Predictive Environments

PMBOK v8 Definition

The scope baseline is the approved version of formal scope documents that can be changed using formal change control procedures and is used as the basis for comparison to actual results. For adaptive approaches, the baseline is defined at the beginning of each iteration and aligned with the prioritized requirements, based on the value expected from the delivery. In adaptive environments, it is usually a product owner who dynamically approves changes and generates them in a more flexible environment, without a formal change control procedure.

Why It Matters for the Exam

This concept appears frequently in PMI exam questions that test your understanding of how change control differs between predictive and adaptive life cycles. Expect scenario-based questions where you must identify the correct change control approach based on the project's development methodology, particularly when distinguishing between formal change control boards (predictive) and product owner approval (adaptive).

Key Points to Remember (for the exam)

• Predictive Change Control: Formal change control procedures are required; changes go through a Change Control Board (CCB) for approval
• Adaptive Change Control: No formal change control procedure; the product owner dynamically approves changes based on value
• Baseline Definition in Adaptive: The baseline is defined at the beginning of each iteration, not once for the entire project
• Performance Measurement Baseline (PMB): Includes scope baseline, schedule baseline, and cost baseline
• Scope Baseline Components: Approved scope statement, Work Breakdown Structure (WBS), and WBS dictionary
• Common Confusion: Thinking adaptive projects have no baselines → Reality: baselines exist but are redefined each iteration
• Key Distinction: Formal change control = predictive; dynamic approval = adaptive

Typical PMI Exam Example

A software development project using Scrum has a product owner who receives a change request from a stakeholder during an iteration. The product owner evaluates the request against prioritized requirements and expected value, then approves the change without a formal CCB meeting. This is correct because in adaptive environments, the product owner dynamically approves changes.

PMI Exam Traps

• Trap: Confusing "no formal change control" with "no change control at all"

  • Reality: Adaptive environments still control changes, but through the product owner's dynamic approval based on value

• Trap: Applying predictive baseline concepts to adaptive projects

  • Reality: In adaptive approaches, baselines are set per iteration, not once for the entire project

• Trap: Thinking the product owner needs CCB approval for all changes

  • Reality: In adaptive environments, the product owner has authority to approve changes without formal CCB procedures

• Trap: Assuming the scope baseline is static in adaptive projects

  • Reality: The scope baseline evolves each iteration as requirements are reprioritized

Important PMI Connections

Quick Review Questions

1. In an adaptive project, who typically approves changes to the scope baseline during an iteration?

2. What are the three components of the scope baseline according to PMBOK v8?

3. How does the definition of baseline differ between predictive and adaptive approaches?

4. What is the relationship between the scope baseline and the Performance Measurement Baseline (PMB)?

5. In which type of project environment would a formal Change Control Board (CCB) be required for scope changes?

PMBOK v8 Reference

Section 5.5 - Scope Baseline (part of Scope Management Knowledge Area) Section 4.2 - Performance Measurement Baseline (part of Integration Management) Section 6.5 - Schedule Baseline Section 7.3 - Cost Baseline