LEARN. PRACTICE. GROW.Concept and mechanism
Shared quality requires concrete collaboration. A developer can help expose internal states; a tester can identify overlooked data combinations; an operator can explain what happens when an overnight batch fails. Sharing responsibility does not mean everyone has identical skills or authority. Define who prepares data, who investigates failures, and who can accept a business risk. In Scrum, an increment that does not satisfy the Definition of Done is not complete because a demonstration looks convincing. Outside Scrum, use the criteria agreed within the team’s method. Avoid turning a rule from one framework into a universal obligation for every Agile organization.
Guided application
In a middleware migration, the security specialist has only two available hours. Use that time to review risks and design checks the team can repeat, while retaining specialist decisions that still require that expertise. Invite someone unfamiliar with the new screen to observe first use without explaining in advance where to click. This first-use feedback loses value once the person knows the journey. Record the difficulty, confirm the user’s objective, and combine the observation with functional testing. To involve business colleagues, present short examples of process exceptions using fictional data and ask for specific decisions about expected outcomes.
Shared knowledge reduces dependency; authority remains explicit.
Common pitfalls
Everyone treated as an expert; demonstration treated as Done; coaching first use.
Related topics: Strategy, risk, and regression · Planning, metrics, and improvement · Examples, criteria, and small deliveries
Collaborate early and retain clear responsibilities.
Reference: The Scrum Guide · CTAL-AT v2.0 (2026)