SAFe-Agilist Establishing Team and Technical Agility Practice Question
Which THREE items should be included in a team's Definition of Done (DoD)? (Select THREE)
⚠ Common exam trap
Test-takers frequently select vague or output-focused options like 'stories estimated' or 'features approved by management' instead of concrete quality criteria like code reviews and passing tests.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Code reviewed by another team member.
The Definition of Done is a vital agreement that defines the quality and completeness of a product increment. It prevents 'done-ish' work from accumulating as hidden technical debt. Including these specific criteria ensures that the team consistently delivers high-quality increments, which is essential for integration on the Agile Release Train and for maintaining the trust of stakeholders throughout the Program Increment.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Code reviewed by another team member.
Why this is correct
Peer review is a fundamental practice for improving code quality and spreading knowledge across the team. It catches bugs early, ensures consistent coding standards, and promotes collaboration. Including this in the DoD ensures that every piece of work is subjected to this quality check before being considered truly finished.
- ✓
Automated tests passed.
Why this is correct
Automated testing is essential for maintaining built-in quality. By requiring that all tests pass, the team ensures that new code does not break existing functionality. This provides the confidence necessary for continuous integration and rapid delivery, as the team can verify the state of the software at any given time.
- ✓
Documentation updated for the end user.
Why this is correct
Documentation is often overlooked, leading to knowledge silos and user confusion. Including it in the DoD ensures that the work is not only technically complete but also usable and maintainable. This contributes to the overall quality of the product, preventing support issues and helping users understand the value being delivered.
- ✗
Approved by the customer representative.
Why it's wrong here
Customer approval should happen during reviews or as feedback, but it shouldn't be a gate for the DoD. The team should be empowered to define 'done' based on technical and quality criteria they can control. Making customer approval a requirement slows the team down and introduces unnecessary external dependencies.
- ✗
Budget approved for the next sprint.
Why it's wrong here
Budgeting is a high-level program or portfolio concern, not an individual team's responsibility. Including it in the DoD is irrelevant to the team's execution process. Focusing on such items distracts the team from their primary goal of creating high-quality, valuable software increments within their current iteration and program context.
About these practice questions
Courseiva writes every SAFe-Agilist question from scratch — 315 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Scaled Agile exam blueprint
This SAFe-Agilist practice question is part of Courseiva's free Scaled Agile certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAFe-Agilist exam.