Release Planning Schedule
A Release Planning Schedule is a primary output of the Conduct Release Planning process. It identifies which deliverables will be provided to customers and specifies the planned cadence and target dates for each release. Not every Sprint must end with a customer release.
Key Points
- Produced during Conduct Release Planning to map deliverables to customer releases.
- Defines the release cadence and target dates or windows for each drop.
- Provides guidance for teams and stakeholders and is updated as priorities or capacity change.
- Allows for Sprints without a customer-facing release when appropriate.
Example
On a mobile app program, the team plans customer releases after Sprints 3, 6, and 9. The Release Planning Schedule lists features for Release 1 on Mar 15 (login and password reset), Release 2 on Apr 26 (biometric authentication and session timeout), and Release 3 on Jun 7 (in-app notifications). Sprints 4 and 8 focus on internal refactoring and performance work without a public release.
PMP Example Question
Which artifact shows which deliverables will be shipped to customers and when, while acknowledging that not every Sprint ends with a release?
- Release Planning Schedule
- Sprint Backlog
- Definition of Done
- Sprint Burndown Chart
Correct Answer: A — Release Planning Schedule
Explanation: The Release Planning Schedule outlines which deliverables go to customers and the planned cadence and dates for releases. Other artifacts do not define release timing to customers.
