PSD

Scrum.org describes it as knowledge of practices and techniques that support building software with Scrum. Expect questions on applying Scrum theory, technical practices such as test automation and continuous integration, collaboration inside a self-managing team, and delivering a releasable Increment every Sprint.

Developers: programmers, testers, designers, and anyone doing the building work on a Scrum Team. Scrum Masters and Product Owners can take it, but the content assumes you write, test, and integrate software daily. Hands-on delivery experience matters more than memorizing definitions.

Yes. Scrum.org lists a Software Developer Open assessment described as preparation for PSD. Use it to find weak areas before booking. It is a readiness check, not a guarantee, so review every question you miss and understand why the correct answer fits Scrum.

Start with the Scrum Guide, then map each Developers accountability to real practices you use. Spend most time on the four published focus areas, and finish with the open assessment. Study in short repeated sessions with your team rather than one long read, and discuss disagreements out loud.

Answering from habit rather than from Scrum. Candidates pick answers that describe their current organization, or that sound technically sensible but contradict the framework - for example, treating a Sprint review as a demo, or letting quality work slip to a later Sprint. Read each option against the Scrum Guide.

Enough to reason about practices, not to write code in the exam. You should understand why automated tests, refactoring, continuous integration, and a shared definition of done support empiricism. Questions test judgment about how practices serve transparency and adaptability, not syntax.

Those details are not stated in the material available here, so treat any figure you see elsewhere with suspicion. Check the current assessment page on Scrum.org for duration, question count, price, and pass score before you register, since these change over time.

Retake terms are set by Scrum.org and are not confirmed in the material available here. Look up the current policy on your Scrum.org account or the assessment page. In practice, most candidates who fail do so narrowly, so review missed topics before scheduling a second attempt.

Validity periods are not confirmed in the available material, so verify on Scrum.org rather than assuming. Regardless of formal expiry, the practices behind the certificate keep changing; re-reading the Scrum Guide and retaking the open assessment periodically keeps your knowledge current.