What is the purpose of a shared 'Definition of Done'?
Tests your ability to ensure quality and transparency across multiple teams. A shared 'Definition of Done' is a formal description of quality for the integrated Increment. It ensures all work is combinable and shippable.
What's really being asked
This question assesses your understanding of how to maintain product quality and transparency when scaling Scrum beyond a single team. The interviewer wants to see if you can think at the product level, not just the team level. It specifically tests your knowledge of the 'Increment' as a core Scrum artifact and how a shared Definition of Done (DoD) is the key commitment that ensures a single, integrated, usable product is created each Sprint from the work of many teams.
The full answer
First, define it as a formal, shared agreement on the quality standards that work must meet to be considered part of the integrated product Increment. Second, explain its primary purpose: to ensure that the work from all teams combines into a single, usable, and potentially releasable product version at the end of every Sprint. This creates transparency for all stakeholders. Third, detail its impact on development practices, such as forcing the use of shared repositories, continuous integration (CI), and common standards. Fourth, explain its impact on testing, requiring integration, end-to-end, and non-functional tests (e.g., performance) to be part of every team's responsibility within the Sprint, not a later phase.
The mistakes people make
A major red flag is describing a scenario where each team has its own, independent DoD. While a team can add to the shared DoD, they must meet the baseline for the product. Saying "each team decides what 'done' means" shows a failure to understand integration. Another mistake is treating the DoD as a simple task checklist (code written, PR approved) instead of a commitment to the quality and state of the integrated Increment. Finally, suggesting that integration happens in a separate "integration sprint" is incorrect; a shared DoD implies integration is a continuous activity for all teams.
What usually comes next
Expect questions like, "How would you facilitate the creation of a shared DoD among several teams?" or "What happens if one team consistently fails to meet the shared DoD?" For the latter, a good answer explains this is a critical impediment for the Scrum Masters to address, as it threatens the value of the entire Sprint for all teams. It requires immediate inspection and adaptation.
A concrete example
For a mobile app built by four teams, our shared DoD required every code merge to the main branch to pass a full suite of integration tests and not increase the app's startup time by more than 5ms. This meant a feature wasn't 'done' when it worked in isolation. My team had to work with the platform team to run performance profiling in a shared staging environment before we could consider our user story complete. This prevented end-of-sprint surprises where the integrated app was too slow to ship.
Interview question
When multiple Scrum teams work on one product, what is the primary purpose of establishing a shared Definition of Done?
- a.To allow each team to define its own independent quality standards, promoting team autonomy and speed.
- b.To ensure the work from all teams integrates into a single, usable, and potentially releasable Increment each Sprint.Correct
- c.To provide a standardized checklist of development tasks, like code reviews and unit tests, for all teams.
- d.To prepare all individual team outputs for a separate 'integration sprint' that occurs after several development sprints.
Why? this is the answer
The correct answer is C because a shared DoD's main purpose is to ensure all work combines into a single, integrated, and usable Increment each Sprint. Option A is a common misconception; while teams have autonomy, a shared DoD is necessary to create a common quality baseline for the integrated product.
Just read this? Test yourself on what you have been reading.
Read the original → scrumguides.org
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on agile — each one lists the topics its interview covers.
See open roles