Agile Release Planning and Roadmaps: PMP Exam Guide

Planning at Multiple Levels in Agile

A common misconception is that agile teams don't plan. In reality, agile involves planning at multiple levels — it's just done differently than in predictive project management. The PMP exam tests your understanding of how agile planning works and when different planning activities occur.

The Agile Planning Onion

Agile planning operates at several nested levels:

Vision — The long-term product direction (months to years)
Roadmap — High-level plan of themes and features across releases (quarters)
Release plan — Which features will be delivered in the next release (weeks to months)
Iteration/Sprint plan — What the team will complete this sprint (1-4 weeks)
Daily plan — What each team member will focus on today

Detail increases as you move inward. The vision is broad and stable. The daily plan is specific and may change tomorrow. This is progressive elaboration — a concept PMI values across both predictive and agile approaches.

Release Planning in Agile

Release planning determines what the team will deliver in an upcoming release and approximately when. Unlike predictive planning, which fixes scope and estimates the schedule, agile release planning can work in two modes:

Date-driven — The release date is fixed. The team forecasts how many features can be completed by that date based on velocity. Scope is variable.
Feature-driven — The required features are fixed. The team forecasts how many sprints are needed to complete them. The date is variable.

Both approaches use velocity-based forecasting: divide the total estimated work (in story points) by the team's average velocity to get the number of sprints needed.

Release Planning Inputs

Prioritized Product Backlog
Team velocity (historical average)
Sprint length
Known constraints (hard deadlines, dependencies, team availability)

Release Planning Outputs

Target release date (or target feature set)
Features included in the release
Key risks and assumptions
Updated roadmap

Building Agile Roadmaps

An agile roadmap communicates the strategic direction of the product without committing to specific features on specific dates. It organizes work into themes or goals rather than detailed feature lists.

Characteristics of a Good Agile Roadmap

Outcome-oriented — Focuses on goals ("improve checkout conversion") rather than outputs ("build one-click purchase")
Time-horizon appropriate — Near-term items are more detailed; future items are intentionally vague
Regularly updated — Reviewed and adjusted at least quarterly based on new information
Stakeholder-friendly — Provides enough visibility for business planning without over-committing the team

Common Roadmap Formats

Theme-based roadmap: Organizes work by strategic themes (e.g., "Q1: Security and compliance," "Q2: Mobile experience") without specifying individual features.

Now/Next/Later: A simple three-column format. "Now" shows current work, "Next" shows upcoming priorities, and "Later" shows future possibilities. No dates — just relative priority.

Timeline roadmap: Maps themes or epics to time periods. More familiar to stakeholders used to Gantt charts but carries the risk of being treated as a commitment.

PMP Exam Considerations

On the exam, remember:

Agile teams do plan — they just plan adaptively
Release plans are forecasts, not commitments — they're updated as velocity data and priorities change
Roadmaps should communicate direction without creating false precision about future delivery dates
The Product Owner drives release planning priorities; the team provides effort estimates

Practice release planning scenarios with PMPprep's exam simulator to build your judgment for these questions.