Iteration Planning: Features, Story Points, and Release Timelines

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 determines the number of iterations or sprints in the release, empowering the product owner and team to determine the development scope, timelines, and a releasable product, factoring in business goals, dependencies, impediments, and resource availability.

Iteration planning schedules feature development, where prioritized features are delivered by user stories (estimated in story points), and tasks (estimated in hours) are created to deliver those user stories.

Why It Matters for the Exam

This concept appears frequently in PMI exam questions about agile planning hierarchy, estimation techniques, and stakeholder communication. You will encounter it in scenario-based questions testing your understanding of how product vision cascades through roadmap, release, and iteration plans, as well as questions about when to use story points versus hours.

Key Points to Remember (for the exam)

• Planning Hierarchy: Product Vision → Product Roadmap → Release Plan → Iteration Plan
• Release Plan: High-level timeline (3–6 months); determines number of iterations; factors in business goals, dependencies, impediments, and resource availability
• Iteration Plan: Schedules feature development; features delivered by user stories
• Estimation Methods: Many agile teams use story points instead of hours; story points reflect relative effort or complexity rather than absolute time
• Story Point Rationale: Teams are typically better at comparing work items than predicting precise durations
• Feature Value: Features represent expected value to the customer; the timeline defines which features will be available at the end of each iteration
• Task Breakdown: User stories are broken into tasks estimated in hours for daily work management

Typical PMI Exam Example

A project team is planning their next release. The product owner presents the product roadmap showing features planned for the next 4 months. During release planning, the team identifies dependencies between Feature A and Feature B, and notes that a key resource will be unavailable during Iteration 3. The team adjusts the iteration plan to deliver Feature A in Iteration 1 and Feature B in Iteration 2, ensuring the release remains on schedule while accommodating resource constraints.

PMI Exam Traps

• Trap: Confusing story points with hours

• Reality: Story points measure relative effort/complexity; hours measure absolute time. Many agile teams use story points because teams compare work items better than predicting durations.

• Trap: Thinking release planning determines exact task-level details

• Reality: Release planning provides a high-level summary timeline; iteration planning breaks features into user stories and tasks

• Trap: Assuming product roadmap and release plan are the same

• Reality: Product roadmap drives release plans; roadmap is the longer-term vision, release plan is the specific 3–6 month schedule

• Trap: Ignoring dependencies and impediments during release planning

• Reality: Release planning must factor in business goals, dependencies, impediments, and resource availability

Important PMI Connections

Quick Review Questions

1. What is the typical duration range for agile release planning?
2. Why do many agile teams use story points instead of hours for estimation?
3. What factors must be considered during release planning besides development scope?
4. What is the relationship between product vision, product roadmap, and release plan?
5. How are features, user stories, and tasks related in iteration planning?

PMBOK v8 Reference

Section 5.2 - Agile Release Planning and Iteration Planning

Note: This content is derived from the PMBOK v8 RAG context provided. The exact section numbering may vary in the official PMBOK v8 Guide.