Iteration Adaptive All: Closing Adaptive Projects and Phases
PMBOK v8 Definition
The Close Project or Phase process involves finalizing all activities related to both successful and unsuccessful projects, phases, releases, iterations, or contracts. In adaptive approaches, this process centers on wrapping up all activities related to the release or iteration, ensuring the prioritized items are completed and the value is delivered. This process belongs to the Closing Process Group.
Why It Matters for the Exam
The PMI exam frequently tests the distinction between predictive and adaptive closing activities, particularly the iterative nature of closing in adaptive projects. Questions often present scenarios where a project manager must determine which closing activities are appropriate for an adaptive environment versus a predictive one.
Key Points to Remember (for the exam)
- Main Focus: Closing centers on the release or iteration, not the entire project (unless final closure)
- Key Activity: Confirm that prioritized backlog items are finished and all acceptance criteria are met
- Critical Step: Ensure all deliverables have been reviewed and accepted by stakeholders
- Common Confusion: Adaptive closing is NOT a one-time event at project end—it occurs repeatedly at the end of each iteration or release
- Essential Output: Value delivery is confirmed for the completed iteration
- Important Distinction: Stakeholder engagement remains crucial even if the project was terminated before completion
- Key Difference from Predictive: Adaptive closing does not require a final project management plan review—it focuses on backlog completion
Typical PMI Exam Example
A software development team using Scrum completes their third two-week sprint. The project manager needs to close the sprint. According to PMBOK v8, what is the PRIMARY activity the project manager should perform? The correct answer: Confirm that prioritized backlog items are finished and that all acceptance criteria are met.
PMI Exam Traps
-
Trap: Confusing adaptive closing with predictive closing activities
- Reality: Adaptive closing focuses on iteration/release completion, NOT reviewing the entire project management plan
-
Trap: Thinking closing only happens at the end of a project
- Reality: In adaptive approaches, closing occurs at the end of each iteration or release
-
Trap: Assuming adaptive closing ignores stakeholder acceptance
- Reality: Stakeholder review and acceptance of deliverables is a required activity in adaptive closing
-
Trap: Believing terminated projects don't need closing
- Reality: The Close Project or Phase process applies to both successful and unsuccessful projects, including terminated ones
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Initiate Project or Phase | Opposite process | Closing officially ends what initiating authorized |
| Predictive Approaches | Contrasting approach | Predictive closing reviews project management plan; adaptive closing reviews backlog |
| Stakeholder Engagement | Critical input | Engaging relevant stakeholders is crucial for comprehensive closure |
| Focus Areas | Process interaction | In adaptive approaches, all Focus Areas interact within short iterations, not sequentially |
Quick Review Questions
-
In an adaptive project, when does the Close Project or Phase process occur?
-
What are the two key activities that must be performed when completing a release or iteration in an adaptive project?
-
Does the Close Project or Phase process apply to projects that were terminated before completion?
-
How does the closing approach differ between predictive and adaptive projects regarding what is reviewed?
-
What is the primary focus of closing in adaptive approaches: the entire project or the iteration/release?
PMBOK v8 Reference
Section 2.1.6.9 - Close Project or Phase Section 2.1.6.9.2 - Adaptive Approaches
This article is optimized for PMI exam preparation using PMBOK v8 content exclusively.