LEARN. PRACTICE. GROW.Concept and mechanism
A shared goal lets a team adapt tasks without losing purpose. The Product Goal guides product work; the Sprint Goal gives coherence to what the Sprint seeks to achieve. A task list with assignees does not replace that direction. When several teams work on the same product, they need a shared Product Goal, Product Backlog, and Product Owner. Do not generalize this rule to independent products merely because they belong to one company. The Definition of Done makes increment quality understandable. Where an organizational standard exists, it is a minimum for the team; self-management does not mean declaring that minimum optional.
Guided application
Consider two teams changing versions of a payments interface. Each pipeline may pass while the integrated journey still fails. Local status then does not demonstrate a usable increment. Expose the failure instead of weakening criteria to preserve a green report. Work failing Done is not part of the increment and returns to the Product Backlog for future consideration; it does not gain automatic priority in the next Sprint. Also distinguish Done from release: the Sprint Review is not a mandatory release gate. An increment may be delivered before it, while external operational conditions still apply. Done does not itself waive authorization required in context.
“Green pipeline” needs interpretation: which version, which journey, and which criteria were actually tested?
Common pitfalls
Done by team majority; review as mandatory approval; unfinished items automatically committed; autonomy as exemption from standards.
Related topics: Facilitate participation and difficult decisions · Coaching, mentoring, teaching, and leadership
Retain shared direction and observable quality criteria in the integrated product.
Reference: The Scrum Guide · PSM II; Scrum Guide November 2020; no public numbered exam revision