Release Product Planning: Agile Release Planning for Exam
PMBOK v8 Definition
Agile release planning provides a high-level summary timeline of the release schedule (typically 3–6 months) based on the product roadmap and the product vision for the product’s evolution. This planning empowers the product owner and team to determine the development scope, timelines, and a releasable product, factoring in business goals, dependencies, impediments, and resource availability.
Why It Matters for the Exam
This concept appears frequently in questions about adaptive life cycle planning, particularly in scenarios where you must distinguish between release-level and iteration-level planning. PMI exam questions test your understanding of how release planning connects product vision to iteration execution, and how timeboxing prevents scope creep.
Key Points to Remember (for the exam)
- Main Input: Product roadmap and product vision
- Main Output: Release plan establishing the number of iterations or sprints
- Key Tool: Timeboxed periods (releases, waves, iterations)
- Typical Timeline: 3–6 months for a release schedule
- Common Confusion: Release planning vs. iteration planning – Release planning provides high-level summary; iteration planning schedules specific feature development
- Critical Factor: Timeboxing helps minimize scope creep by forcing the team to process essential features first
- Measurement: Features represent expected value to the customer; timeline shows which features are available at end of each iteration
Typical PMI Exam Example
A project manager is working on a software product with an adaptive life cycle. The product owner wants to communicate to stakeholders when specific features will be delivered. What planning approach should the project manager use to provide a high-level timeline showing feature availability across the next 4 months?
Answer: Agile release planning, which provides a summary timeline based on the product roadmap and determines the number of iterations needed.
PMI Exam Traps
-
Trap: Confusing release planning with iteration planning Reality: Release planning covers 3–6 months and multiple iterations; iteration planning covers a single timeboxed period
-
Trap: Thinking story points represent absolute time Reality: Story points reflect relative effort or complexity, not precise durations; teams are better at comparing work items than predicting exact hours
-
Trap: Assuming release planning is optional in adaptive life cycles Reality: Release planning is a defined practice in schedule management planning, with specified release and iteration length
-
Trap: Confusing product vision with product roadmap Reality: Product vision drives product roadmap, which then drives release plans (hierarchical relationship)
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Product Vision | Input to | Product vision drives the product roadmap, which drives release plans |
| Product Roadmap | Input to | Roadmap provides the basis for release schedule and feature prioritization |
| Iteration Planning | Output to | Release plan establishes iterations; iteration plans schedule feature development |
| Schedule Management Plan | Contains | Specifies release and iteration length when using adaptive life cycle |
| Timeboxing | Key Technique | Forces team to process essential features first; minimizes scope creep |
Quick Review Questions
-
What is the typical timeframe covered by agile release planning?
-
How does timeboxing help control scope in adaptive life cycles?
-
What is the relationship between product vision, product roadmap, and release planning?
-
When using story points instead of hours, what do story points reflect?
-
What factors must be considered when the product owner and team determine development scope and timelines in release planning?
PMBOK v8 Reference
Section 5.1.1.1 – Schedule Management Plan (Release and iteration length) Section 5.2.3.1 – Agile Release Planning (Figure 5-1 and related content)