Change Backlog Management in Adaptive Approaches
PMBOK v8 Definition
In adaptive approaches, managing project changes typically involves backlog management rather than a formal change request process. Changes are continuously assessed and prioritized throughout the iterative development cycle. When a stakeholder proposes a change, it is recorded as a product backlog item and added to the backlog, with an impact analysis conducted to evaluate the change's effect and set its priority. This concept resides within the Assess and Implement Changes process, which occurs from project start through completion.
Why It Matters for the Exam
This concept appears frequently in PMI exam questions comparing predictive vs. adaptive change management approaches. It is tested in scenario-based questions where you must identify how changes are handled in agile/adaptive environments—specifically that backlog management replaces formal change requests, CCB approvals, and change logs. Questions often test your ability to distinguish between "rejected," "deferred," and "accepted" changes in the backlog context.
Key Points to Remember (for the exam)
- No Formal Change Requests: In adaptive approaches, changes are NOT submitted as formal change requests—they become product backlog items.
- Continuous Assessment: Changes are assessed and prioritized continuously throughout the iterative development cycle, not at scheduled change control board meetings.
- Impact Analysis Required: Despite no formal change request, an impact analysis is still conducted to evaluate the change's effect and set its priority.
- Deferred vs. Rejected: A change assigned lower priority means it is deferred; choosing not to add a change to the backlog or removing an existing one means it is rejected.
- No Formal Approval Process: There is typically not a formal "approval" process; any proposed change can be added to the backlog.
- Backlog Refinement: This technique involves progressive elaboration of backlog content and reprioritization to identify work for upcoming iterations.
- Business Value Ranking: Backlog items are ranked in order of business value or importance to the customer and sized by the development team.
Typical PMI Exam Example
A project using an adaptive (agile) approach receives a request from a key stakeholder to add a new feature. The product owner conducts an impact analysis, determines the feature has moderate value but high complexity, and adds it to the product backlog with a low priority. Question: How should the project manager document this change? Answer: As a product backlog item with deferred status.
PMI Exam Traps
- Trap: Thinking adaptive approaches still require formal change requests and CCB approval.
- Reality: Adaptive approaches use backlog management—changes become backlog items, not formal change requests.
- Trap: Confusing "deferred" with "rejected" in backlog management.
- Reality: Deferred = lower priority (still in backlog); Rejected = not added or removed from backlog.
- Trap: Assuming impact analysis is skipped in adaptive approaches.
- Reality: Impact analysis is still conducted even without formal change requests.
- Trap: Believing backlog refinement is optional or one-time activity.
- Reality: Backlog refinement is progressive elaboration and continuous reprioritization throughout the project.
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Change Log | Replaced by | In adaptive approaches, the change log is not used; the product backlog serves this function. |
| Change Management Plan | Adapted | The change management plan in adaptive projects focuses on backlog management procedures rather than CCB processes. |
| CCB (Change Control Board) | Not applicable | Adaptive approaches do not use a CCB; prioritization is done by the product owner and team. |
| Impact Analysis | Still required | Impact analysis is performed for both predictive (formal) and adaptive (backlog) change approaches. |
| Backlog Refinement | Key technique | This technique enables continuous reprioritization and is tested as the mechanism for managing changes in adaptive projects. |
Quick Review Questions
-
In an adaptive project, a stakeholder proposes a change that the product owner decides not to add to the backlog. What does this represent in terms of change disposition?
-
What is the key difference between a change being "deferred" versus "rejected" in backlog management?
-
When a change is proposed in an adaptive approach, what analysis is still conducted before adding it to the backlog?
-
A project manager on an agile project is asked to produce a change log. What should the project manager explain about how changes are tracked in adaptive approaches?
-
What technique involves the progressive elaboration of backlog content and reprioritization to identify work for upcoming iterations?
PMBOK v8 Reference
Section 2.1.6.8.2 – Adaptive Approaches (within Assess and Implement Changes)