Release Readiness Sprint
A timeboxed sprint used, when necessary, to complete release preparation work and verify that the minimum release criteria are satisfied. It is conducted only once per release and serves as the final sprint immediately before the release.
Key Points
- Used to perform specific activities needed to prepare for a release and confirm minimum release requirements.
- Only created when preparation or verification work remains; not required for every release.
- Occurs once per release and is the last sprint before the release event.
- Common tasks include integration, testing, documentation, compliance checks, deployment checklists, and sign-offs.
Example
A product team plans a quarterly release. Development work is done, but they still need to run end-to-end tests, finalize user documentation, complete security scans, and confirm rollback and support plans. They schedule a Release Readiness Sprint to complete these items and verify release criteria before deploying.
PMP Example Question
A Scrum team has finished feature development for a major release, but several activities remain: system integration testing, regulatory documentation, and final go/no-go checks. What should the Scrum Master recommend?
- Extend the current development sprint until all readiness work is complete.
- Schedule a Release Readiness Sprint as the single final sprint before the release.
- Perform a hardening phase after the release to finish remaining tasks.
- Skip additional work and rely on automated pipelines to validate readiness.
Correct Answer: B — Schedule a Release Readiness Sprint
Explanation: A Release Readiness Sprint, used only when needed, is run once per release to complete preparation tasks and confirm that minimum release criteria are met before deployment.
