Difference Between 'Code Complete' and 'Done'?
Tests if you grasp value delivery vs. task completion. A great answer defines 'code complete' as a dev step and 'Done' as a team-agreed state of shippable value, governed by the Definition of Done. A red flag is equating 'Done' with just 'QA passed'.
What's really being asked
This question tests whether you think in terms of delivering business value versus simply completing technical tasks. Interviewers are looking for a senior mindset that understands ownership, quality, and team accountability. It separates candidates who see their job as 'writing code' from those who see it as 'shipping a valuable, working product'.
The full answer
A good answer covers four key points in order: first, define 'Code Complete' as a developer-centric milestone where code is written, passes unit tests, and is checked in. Second, define 'Done' as a team-agreed, product-centric state where a Product Backlog Item (PBI) provides demonstrable value and is potentially shippable. Third, identify the key artifact as the 'Definition of Done' (DoD), a formal, living document created by the entire Scrum Team that acts as a quality checklist. Fourth, explain that the gap between the two states represents all other value-add activities like integration testing, QA, documentation, and security scans.
The mistakes people make
A major red flag is a siloed, 'not my job' mentality. Saying 'Code Complete' is where the developer's responsibility ends is a classic example. Another common mistake is equating 'Done' with 'QA approved'. While QA is part of the process, 'Done' is a commitment from the entire team, not just one function. Finally, stating that the Product Owner or a manager dictates the Definition of Done is incorrect; the Scrum Guide is clear that the entire Scrum Team creates it.
What usually comes next
Expect follow-ups that probe your practical experience. For example: 'How do you handle sprints where the team consistently fails to get items to Done?', 'Who is responsible if a bug is found in a 'Done' item after the sprint?', or 'Describe a good Definition of Done for a service you've built.'
A concrete example
For a PBI like 'User can reset their password', 'Code Complete' means the backend endpoint is built and unit tested. 'Done', according to a team's DoD, might require that plus: the front-end form is integrated and works, automated E2E tests pass, the feature is reviewed and accepted by the Product Owner, performance tests show a response time under 300ms, and relevant technical documentation is updated.
Interview question
What is the fundamental difference between a feature being 'Code Complete' and being 'Done' in an agile development context?
- a.'Code Complete' means the feature is ready for integration testing, and 'Done' means it has been successfully deployed to the production environment.
- b.'Code Complete' means the developer has finished their tasks, while 'Done' means the Product Owner has accepted the feature.
- c.'Code Complete' refers to the code being written and unit tested, whereas 'Done' signifies that the feature has passed all quality assurance checks.
- d.'Code Complete' is a developer-centric milestone where code is written and unit tested, while 'Done' is a team-agreed, product-centric state where the item is potentially shippable and delivers demonstrable value according to the Definition of Done.Correct
Why? this is the answer
The correct answer (D) accurately distinguishes 'Code Complete' as a developer's technical milestone from 'Done' as a broader, team-agreed state of shippable value defined by the Definition of Done. Option C is a common misconception because while QA is part of getting to 'Done', 'Done' encompasses much more, including integration, documentation, and demonstrable value, not just QA approval.
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