.png&w=3840&q=75)
Question bank
Certified Scrum Developer (CSD)
44 Certified Scrum Developer (CSD) questions with the correct answer and a written explanation, organised across 7 exam domains.
- 44 questions
- 7 domains
- Foundation level
certilumQuestion index
Jump straight to any question. Answers and explanations are inline.
Agile Engineering Practices
8 questions in this domain
- Question 1Single Choice
During the Sprint Review, what is the central artifact the team presents for inspection?
- AThe Increment completed according to the Definition of DoneCorrect answer
- BA detailed status report of all team activities
- CIndividual developer performance metrics
- DA list of process improvement proposals
Why this is the answer
The Sprint Review inspects the Increment against the Definition of Done, verifying that it meets quality standards and is potentially releasable.
- Question 2Multiple Select
Which two statements describe the collaborative nature of the Sprint Review?
- AAdapt the Product Backlog based on current stakeholder feedbackCorrect answer
- BPerform a root-cause analysis of build failures
- CInspect the Increment against the Definition of DoneCorrect answer
- DAssign blame for technical debt accumulated in the Sprint
Why this is the answer
The Sprint Review adapts the Product Backlog and inspects the Increment using the Definition of Done. Root-cause analysis and blame are not Review activities.
- Question 3Interactive
Examine the code block. Which numbered step in the sprint_review function represents a common Sprint Review trap?
- A1Correct answer
- B2
- C3
- D4
Why this is the answer
Presenting the Increment as a passive demo is the 'Demo Fallacy'. The Sprint Review must be a two-way dialogue, not a silent presentation.
- Question 4Single Choice
In Scrum, which event is described as the practical application of Kaizen?
- ASprint RetrospectiveCorrect answer
- BSprint Review
- CSprint Planning
- DDaily Scrum
Why this is the answer
The Retrospective is the practical application of Kaizen; developers identify workflow friction and commit to small-scale improvements.
- Question 5Multiple Select
Which two technical topics are appropriate for a CSD-focused Sprint Retrospective?
- AThe effectiveness of Test-Driven DevelopmentCorrect answer
- BStakeholder satisfaction with the latest feature
- CSlow build times and flaky testsCorrect answer
- DThe quality of the team's status report
Why this is the answer
CSD retrospectives inspect technical practices such as TDD and workflow friction like slow builds. Stakeholder satisfaction and status reporting belong in the Review.
- Question 6Interactive
Review the code block. Which numbered step in run_retrospective violates the self-managing nature of the Scrum team?
- A1
- B2Correct answer
- C3
- D4
Why this is the answer
The Scrum Master should not dictate improvements. The Retrospective is owned by the self-managing team; the Scrum Master may facilitate but not impose changes.
- Question 7Single Choice
According to the playbook, what is the ultimate checkpoint for the Definition of Done?
- ASprint ReviewCorrect answer
- BSprint Retrospective
- CDaily Scrum
- DBacklog Refinement
Why this is the answer
The Sprint Review is the ultimate checkpoint for the Definition of Done; features that do not meet the DoD cannot be presented as part of the Increment.
- Question 8Multiple Select
Which two behaviors are examples of confusing the Sprint Review with the Retrospective?
- ADiscussing how the team worked instead of what was builtCorrect answer
- BAddressing team conflicts during the Sprint ReviewCorrect answer
- CInspecting the Increment against the Definition of Done
- DCommitting to concrete improvements in the Retrospective
Why this is the answer
The Sprint Review focuses on what was built and its value. Discussing how the team worked or resolving team conflicts are Retrospective matters.
Scrum Artifacts
4 questions in this domain
- Question 9Single Choice
According to the playbook, which Scrum event is the formal opportunity for the team to present the results of the Sprint and for stakeholders to collaborate on Product Backlog adaptation?
- ASprint ReviewCorrect answer
- BSprint Retrospective
- CDaily Scrum
- DSprint Planning
Why this is the answer
The Sprint Review is the event where the Increment is inspected and the Product Backlog is adapted based on stakeholder feedback. The Retrospective focuses on process improvement, not product review.
- Question 10Multiple Select
Which two activities are explicitly identified in the playbook as traps to avoid during the Sprint Review?
- ATreating the Sprint Review as a passive demonstration while stakeholders sit silentlyCorrect answer
- BDiscussing technical process failures or team conflicts during the ReviewCorrect answer
- CShowing actual working software instead of status slides
- DUsing metrics such as cycle time and defect density to make process adjustments
Why this is the answer
The playbook identifies the Demo Fallacy and Misplacing Process Improvement as traps. Showing working software is expected, and data-driven process metrics belong in the Retrospective.
- Question 11Interactive
Review the activities in the code block. Which set contains only activities that belong in the Sprint Review?
- AShowing a working feature and updating Product Backlog priorityCorrect answer
- BExplaining a plan to reduce flaky tests and reviewing pair programming
- CShowing a working feature and explaining a plan to reduce flaky tests
- DUpdating Product Backlog priority and reviewing pair programming
Why this is the answer
Showing working software and updating Product Backlog priorities are Sprint Review activities. Reducing flaky tests and reviewing pair programming are process improvements for the Retrospective.
- Question 12Single Choice
In a CSD-focused Sprint Retrospective, what should the team primarily inspect according to the playbook?
- AInspecting the Increment against the Definition of Done
- BEvaluating technical practices such as Pair Programming, TDD, and the robustness of the Definition of DoneCorrect answer
- CAssigning blame for technical bugs
- DReviewing stakeholder feedback on product features
Why this is the answer
CSD-focused retrospectives inspect technical practices such as Pair Programming, TDD, and DoD robustness. The Sprint Review handles Increment inspection and stakeholder feedback.
Scrum Events
7 questions in this domain
- Question 13Single Choice
During the Sprint Review, what is the team primarily presenting to stakeholders?
- AA formal status report of planned tasks
- BThe results of the Sprint, focusing on what was 'Done' according to the Definition of DoneCorrect answer
- CA detailed analysis of team conflicts
- DA financial budget update for the next Sprint
Why this is the answer
The Sprint Review presents the results of the Sprint, focusing on what was 'Done' according to the Definition of Done (DoD). This is a technical verification of value, ensuring the increment meets quality standards and is potentially releasable.
- Question 14Multiple Select
Which two common traps should a team avoid during the Sprint Review?
- ATreating the event as a passive demonstration where stakeholders sit silentlyCorrect answer
- BUsing the Review to discuss process failures or team conflictsCorrect answer
- CEngaging stakeholders in a two-way dialogue about the Increment
- DShowing actual working software to provide transparency
Why this is the answer
The Sprint Review is a collaborative, two-way dialogue, not a passive demonstration. Technical process failures and team conflicts belong in the Sprint Retrospective, not in the Review.
- Question 15Interactive
The code block describes a Sprint Review scenario. Which Sprint Review trap is represented?
- AThe 'Demo' Fallacy: assuming the event is a passive demonstrationCorrect answer
- BMisplacing process improvement in the Review
- CConfusing Review with Retrospective by discussing 'how' the team worked
- DInspecting the Increment against the Definition of Done
Why this is the answer
The scenario shows stakeholders being silent while developers present, with no two-way dialogue. This matches the 'Demo' Fallacy trap, where the Sprint Review is mistakenly treated as a passive demonstration.
- Question 16Single Choice
The Sprint Retrospective is the practical application of which continuous improvement concept?
- AKaizenCorrect answer
- BWaterfall
- CLean Startup
- DParkinson's Law
Why this is the answer
The Retrospective is the practical application of Kaizen, or continuous process improvement. Developers identify friction in their workflows and commit to small-scale improvements that enhance long-term sustainability.
- Question 17Multiple Select
Which two practices are appropriate focus areas for a CSD-focused Sprint Retrospective?
- AEvaluating the effectiveness of Pair ProgrammingCorrect answer
- BEvaluating the effectiveness of Test-Driven Development (TDD)Correct answer
- CAssigning individual blame for architectural mistakes
- DRefining the Product Backlog with stakeholders
Why this is the answer
CSD-focused retrospectives dive into the 'how' by evaluating technical practices such as Pair Programming, Test-Driven Development (TDD), and the robustness of the Definition of Done. They do not assign blame or refine the Product Backlog.
- Question 18Interactive
The code block contains metrics a team might review in a Retrospective. Which Retrospective practice does this represent?
- AData-Driven ReflectionCorrect answer
- BInspection of the Increment
- CStakeholder Collaboration
- DProduct Backlog Adaptation
Why this is the answer
Using metrics such as cycle time, defect density, and build success rates during the Retrospective enables data-driven reflection. This helps the team make objective, evidence-based process adjustments instead of relying on subjective feelings.
- Question 19Single Choice
Who should own the process improvements identified during the Sprint Retrospective?
- AThe Scrum Master
- BThe self-managing development teamCorrect answer
- CThe Product Owner
- DExternal stakeholders
Why this is the answer
The team is self-managing and must own its process changes. The Scrum Master should not dictate improvements, because the Retrospective is meant for the team to identify and commit to its own actionable outcomes.
Scrum Framework
7 questions in this domain
- Question 20Single Choice
In the Scrum Framework, what is the primary focus of the Sprint Review regarding the Increment?
- AInspecting the Increment against the Definition of DoneCorrect answer
- BDemonstrating the team's development workflow
- CAssigning blame for technical failures
- DSolving specific bugs found during the Sprint
Why this is the answer
The Sprint Review is a technical verification of value, ensuring the Increment meets the Definition of Done and is potentially releasable.
- Question 21Multiple Select
Which activities are appropriate for the team and stakeholders to perform during a Sprint Review? Select all that apply.
- AInspecting the Increment against the DoDCorrect answer
- BCollaborating with stakeholders to refine the Product BacklogCorrect answer
- CDiscussing internal team workflow conflicts
- DShowing working software to provide transparencyCorrect answer
Why this is the answer
The Sprint Review inspects the Done Increment, adapts the Product Backlog with stakeholders, and shows working software. Team workflow conflicts belong in the Retrospective.
- Question 22Interactive
According to the Scrum Framework, which item in the agenda above is inappropriate for a Sprint Review?
- APresent the Increment
- BCollect stakeholder feedback
- CUpdate Product Backlog priorities
- DDiscuss developer workflow conflictsCorrect answer
Why this is the answer
Discussing developer workflow conflicts is a Retrospective topic. The Sprint Review focuses on the Increment, stakeholder feedback, and Product Backlog adaptation.
- Question 23Single Choice
In the Scrum Framework, when should technical process failures such as slow build times be addressed?
- ASprint Review
- BSprint RetrospectiveCorrect answer
- CDaily Scrum
- DProduct Backlog refinement
Why this is the answer
The Retrospective is the practical application of Kaizen, where developers identify friction in technical workflows and commit to small-scale improvements.
- Question 24Multiple Select
Which statements about the Sprint Retrospective are true according to the Scrum Framework? Select all that apply.
- AIt applies Kaizen to technical workflowsCorrect answer
- BIt inspects TDD and Pair Programming practicesCorrect answer
- CIt produces actionable outcomes for the Sprint BacklogCorrect answer
- DIt fixes specific production bugs reported by stakeholders
Why this is the answer
The Retrospective applies Kaizen, inspects technical practices, and must produce actionable outcomes. Specific bugs are handled during the Sprint, not in the Retrospective.
- Question 25Interactive
Which item in the retrospective outcomes above is most likely misplaced according to the Scrum Framework?
- AReduce build time by adding caching
- BFix the login bug (#1234)Correct answer
- CAdd unit tests for the payment module
- DExtend the DoD to include integration tests
Why this is the answer
A specific bug is handled during the Sprint; the Retrospective addresses the process that allowed the bug to occur.
- Question 26Single Choice
In the Scrum Framework, who is responsible for owning the process improvements identified in a Sprint Retrospective?
- AThe Scrum Master
- BThe Product Owner
- CThe development teamCorrect answer
- DSenior management
Why this is the answer
The team is self-managing and must own its process changes; the Scrum Master does not dictate Retrospective improvements.
Scrum Roles & Responsibilities
4 questions in this domain
- Question 27Single Choice
What is the main purpose of the Sprint Review?
- AInspecting the Increment and confirming it meets the Definition of DoneCorrect answer
- BEvaluating team collaboration and communication patterns
- CAllocating blame for technical roadblocks encountered during the Sprint
- DBreaking down the next Sprint into detailed technical tasks
Why this is the answer
The Sprint Review focuses on inspecting the Increment and verifying it against the Definition of Done; team process discussions belong in the Retrospective.
- Question 28Multiple Select
Which actions are appropriate during a Sprint Review? Select all that apply.
- ADemonstrating working software and gathering stakeholder feedbackCorrect answer
- BCollaborating with stakeholders to refine Product Backlog prioritiesCorrect answer
- CDiscussing technical process breakdowns such as slow builds or flaky tests
- DVerifying the Increment against the Definition of DoneCorrect answer
Why this is the answer
Appropriate Sprint Review activities include demonstrating the Increment, adapting the Product Backlog, and verifying the DoD. Discussing process failures belongs in the Sprint Retrospective, not the Review.
- Question 29Interactive
Given the following code snippet, which Scrum event is being represented?
- ASprint ReviewCorrect answer
- BSprint Retrospective
- CDaily Scrum
- DSprint Planning
Why this is the answer
The code block models an event that inspects the Increment, checks the Definition of Done, and includes stakeholder interaction while excluding process improvement, which matches the Sprint Review.
- Question 30Single Choice
Which of the following is a common trap during the Sprint Review?
- ATreating the Sprint Review as a passive demonstrationCorrect answer
- BEncouraging two-way dialogue about shifting business needs
- CShowing working software instead of status slides
- DRefining the Product Backlog based on stakeholder input
Why this is the answer
The Sprint Review must be a two-way collaboration, not a passive demo. Showing real software and adapting the Product Backlog are expected behaviors.
Scrum Theory & Values
7 questions in this domain
- Question 31Single Choice
What is the primary focus of the Sprint Review in Scrum?
- AVerifying the Increment against the Definition of Done and confirming potentially releasable valueCorrect answer
- BAssessing individual developer performance and team morale
- CDiscussing how the team can improve its technical workflows
- DAssigning corrective actions for technical debt ownership
Why this is the answer
The Sprint Review focuses on inspecting the Increment against the Definition of Done, presenting what was Done, and determining whether the result is potentially releasable. Process improvement is handled in the Retrospective, not the Review.
- Question 32Multiple Select
Which statements about the Sprint Review are true? Select all that apply.
- AIt is a two-way dialogue among stakeholders, the Product Owner, and the Developers.Correct answer
- BFeedback received during the Review may cause the Product Backlog to be adapted.Correct answer
- CIt is primarily a status report meeting supported by slide decks.
- DIt provides transparency toward the Product Goal by showing working software.Correct answer
Why this is the answer
The Sprint Review is collaborative, supports Product Backlog adaptation, and creates empirical transparency by demonstrating working software. It is not a static status report, and slide presentations cannot replace the inspectable Increment.
- Question 33Interactive
The code_block contains a proposed Sprint Review agenda. Which combination of agenda items aligns with Scrum?
- A1, 2, and 4 onlyCorrect answer
- B1 and 3 only
- C2 and 3 only
- D1, 2, 3, and 4
Why this is the answer
A Sprint Review includes demonstrating the working Increment, collecting stakeholder feedback, and adapting the Product Backlog. Discussing individual productivity is not part of the Review; that belongs in the Retrospective.
- Question 34Single Choice
Which statement best describes the \"Demo Fallacy\" trap in the Sprint Review?
- ATreating the Sprint Review as a passive demonstration in which stakeholders only watchCorrect answer
- BReplacing the Increment demonstration with slides about team velocity
- CFocusing on technical process improvements during the Review
- DPrioritizing Product Backlog changes over stakeholder collaboration
Why this is the answer
The Demo Fallacy is assuming that the Sprint Review is only a demonstration. In reality, the Review is a two-way dialogue where stakeholders, Product Owner, and Developers collaborate to inspect the Increment and adapt the Product Backlog.
- Question 35Multiple Select
Which scenarios are recognized traps during the Sprint Review? Select all that apply.
- AStakeholders remain silent while developers present the Increment.Correct answer
- BThe team discusses technical process failures such as flaky tests and slow builds.Correct answer
- CThe team describes how it worked instead of what was built.Correct answer
- DThe Product Owner and stakeholders collaborate to reprioritize the Product Backlog based on feedback.
Why this is the answer
Silent stakeholders, process-focused discussions, and treating the Review as a \"how we worked\" conversation are traps. Sprint Review should focus on the Increment and enable Product Backlog adaptation, not on internal process improvement.
- Question 36Interactive
The code_block lists outcomes from a Sprint Retrospective. Which outcome violates Scrum's principle of self-management?
- AReduce build time by optimizing the CI pipeline
- BScrum Master selects new coding standards for the teamCorrect answer
- CAdd one improvement task to the next Sprint Backlog
- DStrengthen the Definition of Done with more test coverage
Why this is the answer
The Scrum Team is self-managing and must own its process improvements. The Scrum Master should not dictate improvements. Concrete outcomes such as backlog tasks and strengthened DoD are valid Retrospective results.
- Question 37Single Choice
Which Scrum event is the practical application of Kaizen?
- ASprint RetrospectiveCorrect answer
- BSprint Review
- CSprint Planning
- DDaily Scrum
Why this is the answer
The Retrospective is the practical application of Kaizen. During the Retrospective, the team inspects its technical practices and commits to small, concrete improvements for long-term development sustainability.
Technical Practices
7 questions in this domain
- Question 38Single Choice
What is the primary purpose of the Sprint Review?
- AInspect the Increment against the Definition of DoneCorrect answer
- BAllocate individual tasks for the next Sprint
- CEvaluate each developer's performance
- DDiscuss improvements to the build pipeline
Why this is the answer
The Sprint Review exists to inspect the Increment, verifying that what is 'Done' meets the Definition of Done and is potentially releasable.
- Question 39Multiple Select
Which activities are appropriate for a Sprint Review?
- AShowing Done, working softwareCorrect answer
- BAdapting Product Backlog prioritiesCorrect answer
- CConducting a team retrospective
- DAssigning praise based on individual effort
Why this is the answer
Sprint Review focuses on demonstrating the Done Increment and collaborating with stakeholders to adapt the Product Backlog based on feedback.
- Question 40Interactive
Refer to the interaction in the code block. Which Sprint Review principle is being illustrated?
- AStakeholder CollaborationCorrect answer
- BDefinition of Done Alignment
- CEmpirical Transparency
- DDemo Fallacy
Why this is the answer
The dialogue shows a two-way conversation where the developer and stakeholder react to business changes, reflecting collaborative Sprint Review behavior.
- Question 41Single Choice
What does Kaizen refer to in the Sprint Retrospective?
- AContinuous process improvementCorrect answer
- BShort iteration cycles
- CStakeholder feedback
- DDefinition of Done
Why this is the answer
Kaizen, or continuous process improvement, is implemented in the Retrospective when the team identifies small, sustainable improvements to its workflows.
- Question 42Multiple Select
Which of the following are common traps to avoid during a Sprint Retrospective?
- AFocusing on 'what' instead of 'how'Correct answer
- BExpecting the Scrum Master to dictate improvementsCorrect answer
- CUsing the event to fix specific bugsCorrect answer
- DCommitting to concrete improvement items
Why this is the answer
Traps include confusing 'what' with 'how', letting the Scrum Master dictate changes, and solving specific bugs rather than the process that allowed them.
- Question 43Interactive
Look at the outcomes in the code block. What should the team do with Retrospective improvements?
- AAdd them to the next Sprint BacklogCorrect answer
- BExecute them immediately during the Sprint Review
- CEscalate them to the Scrum Master for approval
- DDelete them if they are not customer features
Why this is the answer
Retrospective improvements should be turned into actionable tasks, often added to the next Sprint Backlog so the team implements them.
- Question 44Single Choice
What is the key difference between the Sprint Review and the Sprint Retrospective?
- AReview looks at 'what'; Retrospective looks at 'how'Correct answer
- BReview focuses on morale; Retrospective on customers
- CReview is developers only; Retrospective includes stakeholders
- DReview assigns tasks; Retrospective evaluates performance
Why this is the answer
Sprint Review focuses on the product and value ('what'), while the Retrospective focuses on the team's technical process and collaboration ('how').
Frequently asked questions
Everything about the Certified Scrum Developer (CSD) question bank and how to use it.