Career upgrade: Learn practical AI skills for better jobs and higher pay.
Level up
PracticeVideosBlogFlashcardsEspañol
All Practice Exams

100+ Free PSD Practice Questions

Pass your Professional Scrum Developer exam on the first try — instant access, no signup required.

✓ No registration✓ No credit card✓ No hidden fees✓ Start practicing immediately
100+ Questions
100% Free
1 / 100
Question 1
Score: 0/0

From the Developer's perspective, what is the most important characteristic of a well-refined Product Backlog item?

A
B
C
D
to track
Same family resources

Explore More Scrum.org Certifications

Continue into nearby exams from the same family. Each card keeps practice questions, study guides, flashcards, videos, and articles in one place.

PSM I

Practice QuestionsStudy GuideCheat SheetFlashcards1 blog

Professional Scrum Master I (PSM I)

Practice Questions1 blog

Scrum.org PAL Evidence-Based Management (PAL EBM)

Practice Questions

Scrum.org Professional Agile Leadership I (PAL I)

Practice Questions

Scrum.org Professional Scrum Facilitation Skills (PSF)

Practice Questions

Scrum.org Professional Scrum Master II (PSM II)

Practice Questions

More From This Family

Videos and articles for deeper review.

ArticleFREE Professional Scrum Master I (PSM I) Exam Guide 2026: Pass scrum.org First Try14 min readArticleFREE PSM I Exam Guide 2026: Pass Professional Scrum Master I on First Try (85% Score, Scrum Guide 2020, Practice Tests)26 min read
2026 Statistics

Key Facts: PSD Exam

85%

Passing Score

Scrum.org

80 Qs

Exam Questions

60 minutes

$200

Exam Fee

Per attempt

Lifetime

Validity

No renewal needed

100

FREE Practice Qs

OpenExamPrep

PSD is a 60-minute, 80-question online assessment from Scrum.org requiring 85% to pass ($200 per attempt). No prerequisites or mandatory training. Covers the 2020 Scrum Guide from the Developer's perspective (Developer accountability, Sprint Backlog ownership, Definition of Done) plus engineering practices: Test-Driven Development (TDD, Red-Green-Refactor), Acceptance TDD, Behavior-Driven Development (BDD, Given-When-Then), Continuous Integration, Continuous Delivery, deployment pipelines, automated test pyramid (unit/integration/system/exploratory), refactoring, code quality, emergent and intentional architecture, technical debt, pair and mob programming, trunk-based development, and collective code ownership. Lifetime certification with no renewal.

Sample PSD Practice Questions

Try these sample questions to test your PSD exam readiness. Each question includes a detailed explanation. Start the interactive quiz above for the full 100+ question experience with AI tutoring.

1According to the 2020 Scrum Guide, who is responsible for creating a usable Increment every Sprint?
A.The Scrum Master
B.The Product Owner
C.The Developers
D.The entire Scrum Team
Explanation: The Developers are the people in the Scrum Team committed to creating any aspect of a usable Increment each Sprint. While the entire Scrum Team is accountable for delivering value, the Developers specifically hold the accountability for turning Product Backlog items into a usable Increment. The Scrum Master and Product Owner have their own distinct accountabilities.
2What is the Definition of Done in Scrum?
A.A checklist of tasks approved by the Product Owner before a Sprint begins
B.A formal description of the state of the Increment when it meets the quality measures required for the product
C.A list of acceptance criteria defined for each Product Backlog item
D.The set of conditions that must be met before the Scrum Master signs off on a Sprint
Explanation: The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. It creates transparency and shared understanding of what 'done' means for an Increment. Work that does not meet the Definition of Done cannot be released or presented at the Sprint Review.
3Which Scrum event is the primary opportunity for the Scrum Team to inspect the Increment and adapt the Product Backlog?
A.Sprint Planning
B.Daily Scrum
C.Sprint Review
D.Sprint Retrospective
Explanation: The Sprint Review is the event where the Scrum Team and stakeholders inspect the outcome of the Sprint (the Increment) and determine future adaptations. The Sprint Review results in a revised Product Backlog that defines the probable next steps. The Sprint Retrospective focuses on the team's processes and practices.
4In Test-Driven Development (TDD), what is the correct sequence of steps?
A.Write code, write tests, refactor
B.Write a failing test, write the minimum code to pass the test, refactor
C.Write all tests upfront, write all production code, deploy
D.Refactor existing code, then write tests to verify the refactoring
Explanation: TDD follows the Red-Green-Refactor cycle: first write a failing test (Red) that defines the desired behavior, then write the minimum production code needed to make that test pass (Green), and finally refactor the code to improve its design without changing its behavior. This tight feedback loop keeps code clean and verifiable.
5What is the primary purpose of Continuous Integration (CI) in a Scrum team context?
A.To allow each Developer to work in isolation and merge code at the end of the Sprint
B.To integrate code frequently so that integration problems are detected and resolved quickly
C.To replace the Sprint Review by automatically demonstrating features to stakeholders
D.To eliminate the need for a Definition of Done by automating all quality checks
Explanation: Continuous Integration involves integrating code changes frequently — often multiple times per day — so integration problems surface early when they are cheapest to fix. CI typically includes automated builds and tests that run on every integration, giving the team rapid feedback on the health of the codebase.
6Who creates the Definition of Done when no organizational standard exists?
A.The Scrum Master
B.The Product Owner
C.The Developers
D.External auditors or quality assurance managers
Explanation: If the Definition of Done is not an organizational standard, the Developers must create a Definition of Done appropriate for the product. The Developers are the practitioners who do the work and best understand what quality standards are achievable and necessary to produce a releasable Increment.
7Which of the following best describes Acceptance Test-Driven Development (ATDD)?
A.Writing unit tests before writing production code to drive the design
B.Collaborating with stakeholders to define acceptance tests before development begins, then building to satisfy those tests
C.Automating regression tests after a feature has been fully implemented
D.Having the Product Owner manually verify each feature before it is accepted into the Sprint
Explanation: ATDD extends TDD by involving stakeholders in defining acceptance criteria before development starts. The team collaborates with business stakeholders to write acceptance tests that specify the desired behavior from the user's perspective. These tests guide development and serve as living documentation of the system's behavior.
8What distinguishes Behavior-Driven Development (BDD) from TDD?
A.BDD uses the Red-Green-Refactor cycle while TDD does not
B.BDD focuses on describing system behavior in human-readable language that stakeholders can understand, while TDD focuses on developer unit tests
C.BDD is only used for UI testing; TDD is used for backend logic
D.BDD and TDD are identical practices with different names
Explanation: BDD extends TDD by expressing tests in human-readable language (often Given-When-Then format) so that product owners, developers, and testers share a common understanding of expected behavior. Tools like Cucumber or SpecFlow allow these natural-language specifications to drive executable tests. TDD operates primarily at the unit level in developer-centric syntax.
9A Scrum Team has accumulated significant technical debt over multiple Sprints. How should the Developers address this?
A.Schedule a dedicated 'technical debt Sprint' with no feature work
B.Raise technical debt as a risk at the Sprint Review and wait for the Product Owner to prioritize it
C.Incorporate technical debt reduction into the Definition of Done and address it continuously each Sprint alongside feature work
D.Ask the Scrum Master to create a separate backlog for technical debt items
Explanation: Technical debt should be addressed continuously rather than deferred to a dedicated sprint. Raising the quality bar through a stronger Definition of Done — ensuring code is clean, tested, and refactored as part of normal Sprint work — is the sustainable approach. A 'debt sprint' perpetuates the pattern of deferring quality work.
10Which branching strategy is most compatible with Continuous Integration practices?
A.Long-lived feature branches that merge to main only when the feature is complete
B.Trunk-based development with short-lived branches or direct commits to the main branch
C.A separate release branch for each Sprint that is maintained indefinitely
D.Branching by team member so each Developer has their own permanent branch
Explanation: Trunk-based development — integrating to the main branch frequently through short-lived branches or direct commits — is the branching strategy most aligned with CI. It keeps integration cycles short, surfaces conflicts early, and ensures the main branch is always releasable. Long-lived feature branches delay integration and increase merge risk.

About the PSD Exam

The PSD (Professional Scrum Developer) from Scrum.org validates that Developers can apply Scrum and modern engineering practices to deliver high-quality Increments. The 80-question, 60-minute assessment requires 85% to pass and is grounded in the 2020 Scrum Guide plus professional engineering disciplines: TDD, BDD, ATDD, CI/CD, automated testing, refactoring, emergent architecture, and technical debt management. Unlike PSM I which focuses on Scrum process knowledge, PSD tests how Developers apply Scrum in a technical context — building software that is truly done every Sprint.

Questions

80 scored questions

Time Limit

60 minutes

Passing Score

85% or higher

Exam Fee

$200 (Scrum.org)

PSD Exam Content Outline

~40%

Scrum Framework Applied by Developers

Developer accountability, Sprint Backlog ownership, Definition of Done as a quality commitment, Sprint Goal from Developer perspective, empiricism, increment characteristics, and self-management

~35%

Agile/Lean Engineering Practices

TDD (Red-Green-Refactor), ATDD, BDD (Given-When-Then), CI/CD pipelines, deployment pipelines, automated test pyramid, exploratory testing, refactoring, code quality, and built-in quality

~25%

Architecture, Collaboration, and Excellence

Emergent and intentional architecture, technical debt management, pair/mob programming, trunk-based development, collective code ownership, SOLID principles, and sustainable pace

How to Pass the PSD Exam

What You Need to Know

  • Passing score: 85% or higher
  • Exam length: 80 questions
  • Time limit: 60 minutes
  • Exam fee: $200

Keys to Passing

  • Complete 500+ practice questions
  • Score 80%+ consistently before scheduling
  • Focus on highest-weighted sections
  • Use our AI tutor for tough concepts

PSD Study Tips from Top Performers

1Know the 2020 Scrum Guide's Developer accountabilities cold — Developers own the Sprint Backlog, create the Increment, and define the Definition of Done when no organizational standard exists
2Master TDD's Red-Green-Refactor cycle: failing test → minimal passing code → clean code. Know how TDD differs from ATDD (stakeholder-level) and BDD (Given-When-Then, human-readable)
3Understand the CI principle: integrate frequently (at least daily), keep the build green, and resolve failures immediately — long-lived feature branches violate CI
4Know the test automation pyramid: many unit tests, fewer integration tests, fewest end-to-end tests. Understand why flaky tests erode CI effectiveness
5For scenario questions, choose answers that build quality in continuously, use empirical data, support self-management, and maintain a sustainable pace

Frequently Asked Questions

What is the PSD passing score?

The PSD assessment requires 85% or higher to pass — at least 68 correct answers out of 80 questions in 60 minutes. This is the same 85% threshold as PSM I and PSPO I, but the subject matter is broader, covering both Scrum framework knowledge and modern engineering practices like TDD, CI/CD, and automated testing.

What engineering practices does PSD cover?

PSD covers Test-Driven Development (TDD) and the Red-Green-Refactor cycle, Acceptance Test-Driven Development (ATDD), Behavior-Driven Development (BDD) with Given-When-Then format, Continuous Integration and Continuous Delivery, automated testing (unit, integration, system, and exploratory), refactoring and code quality, emergent and intentional architecture, technical debt management, pair and mob programming, trunk-based development and version control strategies, and collective code ownership.

How is PSD different from PSM I?

PSM I (Professional Scrum Master I) focuses on the Scrum framework from a Scrum Master's perspective — facilitation, team development, and product agility. PSD (Professional Scrum Developer) focuses on how Developers apply Scrum and modern engineering practices to build high-quality Increments — TDD, CI/CD, automated testing, refactoring, and architecture. Both require 85% on 80 questions in 60 minutes and cost $200.

Do I need the PSD training class to take the assessment?

No. There is no mandatory training for PSD. You can purchase the $200 assessment password directly on Scrum.org and take it when ready. However, the Professional Scrum Developer class (if available) provides hands-on practice with the engineering techniques tested. Most successful self-study candidates read the 2020 Scrum Guide, study TDD and CI/CD in depth, and practice with the Scrum Developer Open Assessment on Scrum.org.

Is PSD certification worth it?

PSD validates technical Scrum competence at an industry-recognized standard from Scrum.org. It is most valuable for Developers who want to demonstrate both Scrum process knowledge and engineering discipline (TDD, CI/CD, clean code) — making it complementary to PSM I or PSM II. Like all Scrum.org certifications, it is lifetime with no renewal fees.