Release Planning
Release Planning is an agile practice where the team and Product Owner determine the scope, timing, and goals for the next product release by mapping backlog items across future iterations based on team velocity.
Know it well enough for the exam? Questions on Release Planning are scenario-based, not definitional.
Practice it freeExplanation
Release planning bridges the gap between individual sprints and product roadmap milestones. It answers the question: given our velocity and the remaining backlog, when can we deliver a meaningful set of features to users? Release planning is typically done at a higher level than Sprint Planning, looking ahead multiple sprints.
The Product Owner identifies the items that constitute a release (a Minimum Viable Product, a feature set, or a contractual deliverable). Using the team's average velocity, the team forecasts how many sprints are needed to complete those items. This forecast is a range, not a commitment, and is updated as the team completes each sprint.
Release planning supports both date-driven and feature-driven approaches. In a date-driven release, the team determines how many features can be completed by a fixed date. In a feature-driven release, the team estimates when a specific set of features will be done. Both approaches use velocity as the key forecasting metric.
Key Points
- •Maps backlog items across future iterations to forecast a release
- •Uses team velocity as the primary forecasting metric
- •Supports both date-driven and feature-driven release strategies
- •Updated regularly as the team completes sprints and new information emerges
Exam Tip
Release planning uses velocity to forecast when features will be ready. It produces a range estimate, not a fixed commitment, and is updated regularly.
Frequently Asked Questions
Related Topics
Velocity
Velocity is the amount of work a Scrum team completes in a Sprint, typically measured in story points, used to forecast how much work the team can handle in future sprints.
Burn-Up Chart
A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.
Minimum Viable Product (MVP)
A Minimum Viable Product (MVP) is the smallest version of a product that can be released to customers to validate a business hypothesis and gather maximum learning with the least effort.
Product Backlog
The product backlog is an ordered list of everything that is known to be needed in the product, serving as the single source of requirements and the primary artifact for managing scope in agile projects.
Most-studied PMP concepts
High-yield topics our learners drill most before exam day.
Burndown Chart
A burndown chart plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.
Burn-Up Chart
A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.
Weighted Shortest Job First (WSJF)
Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.
Relative Estimation
Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.
Sprint Review
The Sprint Review is a Scrum event held at the end of the Sprint where the Scrum Team presents the Increment to stakeholders, gathers feedback, and collaborates on what to do next.
Sprint Backlog
The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus the Sprint Goal and the plan for delivering the Increment.
Timeboxing
Timeboxing is the practice of allocating a fixed, maximum amount of time for an activity, after which the activity stops regardless of whether it is complete.
Resource Leveling
Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.
Deliverables
A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.
Part of
Agile & Hybrid
Practice Release Planning
Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.