LEARN. PRACTICE. GROW.Concept and mechanism
In a financial integration, normal processing works but reconciliation required by the Definition of Done failed. Showing only the happy path may lead stakeholders to assume readiness. Item-specific criteria and common increment criteria address complementary needs. Acceptance of one feature does not automatically make the whole usable. When multiple Scrum Teams work on one product, they need a common Definition of Done appropriate to the integrated increment.
Guided application
In the exercise, the organization requires recovery evidence before production. The team can create a Done increment and deliver when ready and applicable conditions are met. Sprint Review does not replace that governance and is not by definition technical production authorization. Nor must delivery wait for Review merely because it is a Sprint-end event. Discuss delivering small increments without reducing quality, considering observability, compatibility, and real operational decisions.
A team retains required checks and reduces negotiated scope rather than removing the check preventing a Done claim.
Common pitfalls
Lowering criteria to improve reports; turning Review into a mandatory release sign-off.
Related topics: Review, retrospective, and usable learning · Empiricism and values in real decisions
Done requires demonstrated quality; release decisions have their own context.
Reference: The Scrum Guide, November 2020 · PSM I; Scrum Guide November 2020; no public numbered exam revision