HKSM
Release Readiness Plan
A plan that lays out the actions for the involved Scrum Teams and other stakeholders to verify that the minimum release criteria are satisfied and that the product or product increment is ready to be deployed.
Key Points
- Defines the tasks, owners, and checkpoints to confirm minimum release criteria are met.
- Aligns multiple Scrum Teams and contributors on what evidence is needed for release.
- Captures required proofs such as test results, security/compliance signoffs, and updated documentation.
- Supports go/no-go decisions, including risk assessment, rollback steps, and environment readiness.
Example
A product group preparing a quarterly release creates a Release Readiness Plan that lists security testing, performance benchmarks, UAT approvals, updated release notes, training materials, and a rollback plan. Each item has an owner and due date. Once all items are completed and signed off by the Product Owner and compliance, the increment is cleared for production deployment.
PMP Example Question
Which artifact outlines the actions Scrum Teams and other stakeholders take to verify that minimum release criteria are met and a product increment can be deployed?
- Definition of Done
- Release Readiness Plan
- Sprint Backlog
- Product Roadmap
Correct Answer: B — Release Readiness Plan
Explanation: The Release Readiness Plan specifies the verification steps, owners, and evidence needed to confirm the increment is ready for release. The other options do not define these end-to-end release verification activities.
