Explain the difference between code complete and Done. What artifact defines this?
Tests whether you know Done means a usable Increment, not just written code. Strong answer: code complete is a dev milestone; Done means the Increment meets quality standards. Red flag: saying testing happens after Done or that Done is optional.
What's really being asked
This question tests whether you understand the Scrum distinction between developer activity and a transparent, usable Increment. Interviewers want to see that you know Done is a formal state that creates transparency about actual progress, not an informal milestone that hides remaining work.
The full answer
First, define code complete as a local developer milestone where implementation is written but not necessarily integrated, tested, or documented. Second, define Done as the state where the Product Backlog Item meets the teams shared quality standard and the resulting Increment is usable. Third, name the Definition of Done as the artifact that formalizes this standard and makes the state of the Increment transparent to the Scrum Team and stakeholders. Fourth, connect this to empiricism: without a clear Definition of Done, inspection of progress is misleading because the perceived state of the Increment does not match reality.
The mistakes people make
Saying that Done means the code is merged or passed code review but testing or documentation will happen later. Treating Done as optional or variable per item rather than a shared team standard. Confusing the Sprint Backlog or Product Backlog with the artifact that defines quality. Claiming the Product Owner alone decides what Done means without team input.
What usually comes next
How does your team handle work that does not meet the Definition of Done by the end of a Sprint? What happens if the Definition of Done is too strict and the team cannot finish items? How does the Definition of Done relate to the Increment and transparency?
A concrete example
A developer finishes writing a feature and opens a pull request. The item is code complete. However, it is not Done until the code is reviewed, merged, deployed to a staging environment, passing automated and manual tests, and documented in the release notes. Only when those criteria in the Definition of Done are met does the Product Backlog Item become a transparent part of the Increment.
Interview question
In Scrum, a developer finishes coding and opens a pull request. Which statement best distinguishes this state from Done?
- a.The item is code complete; Done is whatever the Product Owner alone decides it to be for this item
- b.The item is an Increment that meets the team's shared quality standard
- c.The item is code complete; it becomes Done only when it meets the Definition of DoneCorrect
- d.The item is Done because the code is written and ready for review
Why? this is the answer
The correct answer distinguishes code complete as a local developer milestone from Done, which requires meeting the shared Definition of Done so the Increment is usable. Option D is tempting because it equates written code with Done, but the card shows that Done requires integration, testing, and documentation against the Definition of Done.
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 scrum — each one lists the topics its interview covers.
See open roles