Question bank
Professional Scrum Developer (PSD)
40 Professional Scrum Developer (PSD) questions with the correct answer and a written explanation, organised across 4 exam domains.
- 40 questions
- 4 domains
- Foundation level
certilumQuestion index
Jump straight to any question. Answers and explanations are inline.
Developing & Delivering Products Professionally
12 questions in this domain
- Question 1Single Choice
What does collective ownership require from Developers in a Scrum Team?
- AThey must be able to perform every task perfectly.
- BThey share responsibility for the quality and completion of the Increment.Correct answer
- CThey should focus only on their own specialized tasks.
- DThey should ask testers to handle all quality checks.
Why this is the answer
Collective ownership means the Developers share accountability for quality and completion, not that every person can do everything perfectly.
- Question 2Multiple Select
Which two statements reflect skill complementarity in Scrum?
- AThe team collectively covers all technical dimensions required by the Product Goal.Correct answer
- BEvery Developer must be a unicorn who knows every skill perfectly.
- CScrum focuses on combining specialized skills rather than hiring unicorns.Correct answer
- DThe team should rely on external specialists for security and performance.
Why this is the answer
Skill complementarity means the team's combined expertise covers all technical dimensions, so Scrum values complementary specialists over unicorns.
- Question 3Interactive
Observe the code block. Which Scrum concept does the data structure describe?
- AUnicorn developer
- BT-shaped professionalCorrect answer
- CCross-training
- DCollective ownership
Why this is the answer
The code shows one deep expertise plus several supporting skills, which represents a T-shaped professional.
- Question 4Single Choice
What is the main risk of relying on external specialists or silos?
- AWait time and external blockersCorrect answer
- BHigher test coverage
- CBetter Definition of Done
- DMore predictable velocity
Why this is the answer
External dependencies create wait time and blockers, which are primary drivers of Sprint failure and unpredictable velocity.
- Question 5Multiple Select
Which two statements about Definition of Done alignment are correct?
- AThe team's collective skills must allow them to satisfy every DoD criterion.Correct answer
- BOnly the most experienced Developer needs to understand the DoD.
- CMeeting the DoD means the Increment is potentially releasable.Correct answer
- DThe DoD should be changed after every Sprint to reduce quality.
Why this is the answer
The DoD operationalizes cross-functionality and ensures the Increment is truly releasable, requiring the whole team's collective skills.
- Question 6Interactive
What common misinterpretation of cross-functionality is represented by the code block?
- ACross-functionality is the same as cross-training.
- BEvery Developer must be able to perform every task perfectly.Correct answer
- CSpecialists are not welcome on a Scrum Team.
- DOnly the team, not the individual, needs capability.
Why this is the answer
The code models the trap of assuming cross-functionality means every developer must perform every task perfectly.
- Question 7Single Choice
What does a T-shaped professional look like?
- ADeep expertise in one area and broad enough skills to assist in other areas.Correct answer
- BEqual ability in every technical area.
- CNo specialization at all.
- DDeep expertise in exactly two unrelated areas.
Why this is the answer
A T-shaped professional has a deep vertical skill and a horizontal breadth of supporting skills to help the team reach the Sprint Goal.
- Question 8Multiple Select
Which two statements are traps according to PSD?
- AAssuming cross-functionality means every Developer can perform every task perfectly.Correct answer
- BMistaking cross-functionality for cross-training.Correct answer
- CSeeking skill complementarity in the team.
- DAccepting specialists on the Scrum Team.
Why this is the answer
The traps are assuming perfection from every Developer and mistaking cross-functionality for cross-training. Skill complementarity and specialists are expected.
- Question 9Interactive
One pillar of empirical process control is missing from the list. What is it?
- AAdaptationCorrect answer
- BAutomation
- CDocumentation
- DCertification
Why this is the answer
The three pillars of empirical process control are transparency, inspection, and adaptation.
- Question 10Single Choice
What is a primary vehicle for Kaizen in Scrum?
- AContinuously strengthening the Definition of DoneCorrect answer
- BIncreasing the number of features per Sprint
- CDeferring quality improvements
- DReplacing Retrospectives with design meetings
Why this is the answer
A primary vehicle for Kaizen is the continuous strengthening of the DoD by incrementally adding stricter quality criteria.
- Question 11Multiple Select
Which two actions do Developers take in the Sprint Retrospective to improve technical excellence?
- AIdentify technical bottlenecks such as slow automated tests.Correct answer
- BCommit to actionable improvements.Correct answer
- CAssign blame for build failures.
- DTurn the Retrospective into a technical design meeting.
Why this is the answer
Developers use the Retrospective to inspect technical bottlenecks and commit to actionable improvements, not to assign blame or hold design meetings.
- Question 12Interactive
Which technical debt practice does the code block recommend?
- ADeferring technical debt to a future sprint
- BAddressing technical debt incrementallyCorrect answer
- CWaiting for a dedicated refactoring sprint
- DAssigning debt to external specialists
Why this is the answer
Kaizen encourages addressing technical debt incrementally during every Sprint rather than waiting for a refactoring sprint.
Developing People and Teams
8 questions in this domain
- Question 13Single Choice
Which statement best describes collective ownership in a Scrum team?
- AAll Developers share responsibility for the Increment's quality and completionCorrect answer
- BEach Developer owns a separate code module exclusively
- CTesters alone are responsible for ensuring quality
- DA designated Technical Lead owns all technical outcomes
Why this is the answer
Collective ownership means the whole team shares accountability for the Increment's quality and completion, not a single role or individual.
- Question 14Multiple Select
Which statements about cross-functionality are true? Select all that apply.
- AThe team combines expertise to cover all required technical dimensionsCorrect answer
- BEvery team member must be able to perform every task perfectly
- CExternal specialists are needed to avoid any internal skill gaps
- DThe team can deliver an Increment without relying on outside silosCorrect answer
Why this is the answer
Cross-functionality means the team collectively has the required skills to deliver an Increment and reduce reliance on external specialists.
- Question 15Interactive
Read the embedded code block. Which Scrum practice does the code describe?
- ACollective code ownershipCorrect answer
- BTechnical lead ownership
- CTest-only ownership
- DIndividual module ownership
Why this is the answer
The code assigns shared codebase, quality accountability, and a uniform Done standard to every developer, which reflects collective ownership.
- Question 16Single Choice
In the T-shaped professional model, what does the vertical bar represent?
- ADeep expertise in one areaCorrect answer
- BBroad ability across many areas
- CKnowledge of all programming languages
- DManagement and leadership skill
Why this is the answer
The vertical bar represents deep expertise in a primary area, while the horizontal bar represents broad supporting skills.
- Question 17Multiple Select
Which practices help a Scrum Team eliminate dependencies? Select all that apply.
- ACombining skills inside the team to cover all product dimensionsCorrect answer
- BPostponing Sprint work until an outside expert is available
- CEnsuring the team has the collective capacity to meet the DoDCorrect answer
- DOutsourcing security analysis to a separate department
Why this is the answer
Dependencies are reduced by ensuring internal collective capacity and removing the need to wait for outside experts.
- Question 18Interactive
What does the embedded code block illustrate about delivering the goal?
- AThe team needs every member to master all these skills
- BThe combined skills cover the dimensions needed to achieve the goalCorrect answer
- COnly backend developers will be assigned to testing tasks
- DAn external security specialist is required before work starts
Why this is the answer
The code shows complementary skills that together cover the technical areas needed to achieve the team's goal.
- Question 19Single Choice
How does the Definition of Done operationalize cross-functionality?
- AIt verifies the team's combined skills can satisfy every completion criterionCorrect answer
- BIt lists which specialist should perform each task
- CIt replaces the need for collaboration
- DIt only applies to testing activities
Why this is the answer
The DoD ensures the team's collective capabilities can produce an Increment that meets every agreed quality criterion.
- Question 20Multiple Select
Which statements are common traps related to cross-functionality? Select all that apply.
- AThinking every developer must perform every task perfectlyCorrect answer
- BTreating cross-training as the final goal rather than delivery capabilityCorrect answer
- CBelieving specialized skills cannot exist on a Scrum TeamCorrect answer
- DCombining specialists so the team can deliver an Increment collectively
Why this is the answer
Common traps include unrealistic all-rounder expectations, mistaking cross-training for the objective, and treating specialization as forbidden.
Managing Products with Agility
8 questions in this domain
- Question 21Single Choice
What does Collective Ownership require from Developers on a Scrum Team?
- AShared responsibility for Increment qualityCorrect answer
- BTesters ensure quality alone
- CScrum Master fixes all defects
- DOnly lead developers own quality
Why this is the answer
Collective Ownership means the whole team shares responsibility for quality and completion of the Increment, not a single role or person.
- Question 22Multiple Select
Which of the following are common traps when applying cross-functionality? Select all that apply.
- ARequiring every developer to master every taskCorrect answer
- BMistaking cross-functionality for cross-trainingCorrect answer
- CViewing specialized skills as a Scrum violationCorrect answer
- DEliminating all specialized roles from the team
Why this is the answer
Cross-functionality traps include demanding perfect universal ability, confusing it with cross-training, and treating specialists as prohibited. Specialists are welcome if the team remains cross-functional.
- Question 23Interactive
The code block shows a Scrum Team's skill coverage. If the Product Goal requires security expertise, what does this represent?
- AA gap in the team's combined expertiseCorrect answer
- BA requirement for every developer to know security
- CA sign that specialists should not be used
- DAn acceptable delay until the next Sprint
Why this is the answer
Cross-functionality depends on the team's combined skills. If security is required, the missing capability is a gap the Developers need to fill collectively.
- Question 24Single Choice
How is cross-functionality operationalized within a Scrum Team?
- AThe team's skills satisfy every DoD criterionCorrect answer
- BEach Developer has a separate quality checklist
- CThe Product Owner approves all technical work
- DDoD applies only to externally visible work
Why this is the answer
Cross-functionality is operationalized through the DoD: the team's collective skills must satisfy every criterion so the Increment is potentially releasable.
- Question 25Multiple Select
Which of the following are common traps for Kaizen? Select all that apply.
- ABelieving Kaizen means doing more workCorrect answer
- BConfusing Retrospective with design meetingCorrect answer
- CThinking technical debt can be fixed laterCorrect answer
- DAddressing debt incrementally every Sprint
Why this is the answer
Kaizen is about increasing efficiency and quality, not doing more work. The Retrospective is for process and people, and technical debt should be handled continuously.
- Question 26Interactive
The code block shows team data shared with stakeholders. Which Scrum pillar makes this practice essential for adaptation?
- ATransparencyCorrect answer
- BInspection
- CAdaptation
- DTechnical Debt
Why this is the answer
Sharing build failures, test duration, and velocity openly creates transparency, the foundation for inspecting and adapting.
- Question 27Single Choice
What does Kaizen promote in professional Scrum development?
- AContinuously improve quality and efficiencyCorrect answer
- BDo more feature work each Sprint
- CFix technical debt in a separate sprint
- DAvoid changing the Definition of Done
Why this is the answer
Kaizen is continuous improvement focused on quality and efficiency. It includes strengthening the DoD and addressing debt incrementally.
- Question 28Multiple Select
Which options are traps related to shared ownership? Select all that apply.
- AShared ownership means no specialized skillCorrect answer
- BTechnical Lead is fully accountable for qualityCorrect answer
- CShared ownership means groupthinkCorrect answer
- DPeer review and shared documentation are needed
Why this is the answer
Shared ownership permits specialization, holds all Developers accountable, and requires rigorous standards. It does not mean groupthink or a lack of specialization.
Understanding and Applying the Scrum Framework
12 questions in this domain
- Question 29Single Choice
What does collective ownership require from every Developer on a Scrum Team?
- AOnly owning the code you wrote
- BBeing accountable for the quality and completion of the whole IncrementCorrect answer
- CTaking turns being the tester
- DAvoiding changes outside your specialty
Why this is the answer
Collective ownership means the whole team shares responsibility for the Increment's quality and completion, rather than individual silos.
- Question 30Multiple Select
Which practices help distribute technical knowledge and lower the 'bus factor' in a Scrum Team?
- APair programmingCorrect answer
- BCode reviewsCorrect answer
- CShared documentationCorrect answer
- DAssigning permanent single owners to modules
Why this is the answer
Pair programming, code reviews, and shared documentation reduce knowledge silos and make the team resilient to individual absences.
- Question 31Interactive
In the provided code, each team member is shown with one isolated skill. Which Scrum characteristic is most directly weakened?
- AT-shaped professionalsCorrect answer
- BCollective ownership
- CDefinition of Done evolution
- DEmpirical Process Control
Why this is the answer
The snippet shows narrow specialists, but T-shaped professionals also have broad enough skills to assist the team across areas.
- Question 32Single Choice
How does the PSD view T-shaped professionals?
- AA developer with deep expertise in one area and broad enough skills to help in other areasCorrect answer
- BA developer who knows every technology perfectly
- CA developer who only works on the horizontal part of the UI
- DA developer who avoids work outside their specialism
Why this is the answer
T-shaped professionals have deep expertise in one area, plus general skills that let them assist the team across other areas.
- Question 33Multiple Select
Which statements about cross-functional teams are true?
- AThey minimize or eliminate reliance on external specialistsCorrect answer
- BEvery developer must be able to perform every task perfectly
- CThey reduce wait time caused by external silosCorrect answer
- DAll technical dimensions required by the Product Goal must be covered by the teamCorrect answer
Why this is the answer
A cross-functional team collectively covers all required technical skills and reduces external dependencies and wait time.
- Question 34Interactive
Refer to the code snippet. Which Scrum goal is most at risk?
- AElimination of dependenciesCorrect answer
- BTechnical debt management
- CDefinition of Done evolution
- DAutomated feedback loops
Why this is the answer
External dependencies create wait time and are a primary driver of Sprint failure and unpredictable velocity.
- Question 35Single Choice
According to the Professional Scrum Developer guidance, what is a primary vehicle for Kaizen?
- AThe continuous strengthening of the Definition of DoneCorrect answer
- BWaiting for a separate refactoring sprint
- CReducing the number of Developers
- DAssigning a Technical Lead to make decisions
Why this is the answer
A primary vehicle for Kaizen is the continuous strengthening of the Definition of Done with stricter quality criteria.
- Question 36Multiple Select
Which traps should a Scrum Team avoid when applying cross-functionality?
- AAssuming every Developer must perform every task perfectlyCorrect answer
- BMistaking cross-functionality for cross-training as the goalCorrect answer
- CViewing specialized skills as a violation of ScrumCorrect answer
- DEnsuring all technical dimensions are covered collectively
Why this is the answer
Cross-functionality does not mean perfect individual generalists, cross-training is only a method, and specialists are welcome.
- Question 37Interactive
The code snippet schedules detailed technical design during the Sprint Retrospective. Which trap is represented?
- AConfusing the Sprint Retrospective with a technical design meetingCorrect answer
- BStrengthening the Definition of Done
- CPracticing Kaizen
- DImplementing automated feedback loops
Why this is the answer
The Retrospective is for process and people; technical design should happen through continuous collaboration and refinement.
- Question 38Single Choice
How should Developers address technical debt according to Kaizen?
- AProactively and incrementally during every SprintCorrect answer
- BOnly in a dedicated refactoring sprint
- CWait until the Product Owner requests it
- DDefer it until after the product is released
Why this is the answer
Kaizen encourages addressing technical debt incrementally during every Sprint to maintain a sustainable development pace.
- Question 39Multiple Select
Which three elements are pillars of empirical process control?
- ATransparencyCorrect answer
- BInspectionCorrect answer
- CAdaptationCorrect answer
- DAutomation
Why this is the answer
Empirical process control depends on transparency, inspection, and adaptation.
- Question 40Interactive
What does the code above reveal about the team's attitude to technical debt?
- ATechnical debt can be fixed laterCorrect answer
- BTechnical debt management is incremental
- CKaizen is continuous
- DThe Definition of Done is strengthened incrementally
Why this is the answer
Waiting for a refactoring sprint reflects the trap of thinking technical debt can be fixed later.
Frequently asked questions
Everything about the Professional Scrum Developer (PSD) question bank and how to use it.