Free resource · Markdown

A release-readiness checklist that asks for evidence.

Separate completed implementation from verified behavior. Make coverage, stale evidence and unresolved decisions visible to the people responsible for shipping.

Take it into your next release review.

Download checklist Download worked sample

ScopeAre the intended requirements and boundaries clear? Have changes been recorded?ImplementationDoes each requirement have accountable work? Are blockers visible?VerificationWhich tests are untested, failed, blocked or stale? Do results identify the executed revision?ExceptionsDo unresolved defects and accepted risks have an owner and rationale?DecisionWho owns go/no-go? Have the required reviewers inspected the evidence?Operational handoffHave deployment, monitoring, rollback and communications been considered?

These checkboxes are temporary and are not saved or sent anywhere. The download is yours to keep. Operational-handoff prompts are general advice, not claims that Yetea deploys, monitors or rolls back software.

Worked example: hold for a coverage gap.

In our fictional release, CASE-001 revision 1 passed the single-use check. The expired-link requirement still lacks a case. The product owner holds the release review while the QA owner defines and executes that coverage.

A passing result for one requirement does not settle the decision for the entire release.

Follow the connected workflow