
A sprint can finish on schedule while the release is still blocked. The work you completed might cover development, while an unresolved test, approval or deployment dependency is what determines whether the release is ready. Keep a short readiness table that survives the sprint boundary.
| Release criterion | Owner | Evidence required | Check date | Current state |
|---|---|---|---|---|
| Export handles the supported inputs | QA lead | Recorded results from the agreed cases | Sprint 2 Friday | In progress |
| Support knows what changes | Support lead | Reviewed help text and response notes | Sprint 3 Tuesday | Waiting on screenshots |
| Rollback procedure is usable | Release lead | Documented staging rehearsal | Sprint 3 Thursday | Scheduled |
| Release approved | Release lead | Required checks confirmed and decision recorded | Release morning | Pending |
Use one row per criterion. Link to the underlying sprint issues where details belong. Pick status terms that help someone act: waiting for evidence, blocked, verified, or explicitly accepted with a named owner. Decide who can accept an exception and capture their reason. A green sprint board alone does not satisfy a verification criterion.
At the end of Sprint 2, suppose the feature is merged but one supported input remains untested. Carry the test criterion forward with the exact missing case and the next check date. Write down which release decision it could delay. Keeping the old and new sprint link makes the history easy to follow.
In the first check of Sprint 3, ask what changed since the previous review and whether evidence is still current. If a late change affects a result you verified earlier, identify the check that must be repeated. Leave completed criteria visible so the final decision can distinguish verified work from a newly accepted exception.
In SelfManager.ai Team, pin a shared table with one task per criterion, then assign an owner and keep evidence links in notes or comments. Keep sprint work in its own dated tables. Move the next verification task to the date when someone can do it, while keeping the release deadline visible. Use Team AI Review to summarize what moved across the relevant shared work, then confirm release gates against the underlying results. Team review and dated tables.
End each sprint by naming the next three decisions, who will make them, and when you will check. At release time, the decision should be explainable from the table without recreating the last three sprint meetings.

Plan smarter, execute faster, achieve more
Create tasks in seconds, generate AI-powered plans, and review progress with intelligent summaries. Perfect for individuals and teams who want to stay organized without complexity.
Get started with your preferred account