More study resources

About this exam

The Professional Scrum Master I (PSM I) is an entry-level credential that assesses whether you understand Scrum as defined in the Scrum Guide and can apply it to real team situations. It is aimed at Scrum Masters, but product people, developers, managers and coaches often take it to establish a shared vocabulary before working in or alongside Scrum teams. The assessment is knowledge-based rather than experience-certified: it tests your grasp of Scrum theory and empiricism, the accountabilities of the Scrum Team, the events and their timeboxes, the artifacts and their commitments, and how the framework holds up against common organizational pressure to compromise it. Expect questions that reward precise reading of the Scrum Guide rather than pattern-matched buzzwords - several items hinge on distinguishing what Scrum requires from what is merely common practice. To prepare, read the current Scrum Guide closely and more than once, then work through the official and open assessments until you can explain, in your own words, why each rule exists. Wherever a candidate wants scheduling, pricing or scoring details, the certifying body publishes the current figure on its own site - always confirm there, since these logistics change.

What you'll study

Common questions

About PSM I preparation

What is the exam format?

It is a timed, online, multiple-choice assessment taken in a browser, typically with a mix of single-answer and multiple-answer items. Some questions ask you to pick all that apply, and partial credit rules vary by item, so read each prompt carefully. The certifying body publishes the current format and item types on its assessment page.

How long is the exam, and how many questions?

Those numbers are set by the certifying organization and change from time to time, so this page does not state them. Check the official assessment page before you schedule so you can plan your pacing. As a habit, skim the whole set first and answer the unambiguous items before returning to the tricky ones.

What score do I need to pass, and what does it cost?

Passing thresholds and fees are published by the certifying body and are not fixed forever. Confirm both on the official site at the time you book rather than relying on secondhand figures. If you purchase an assessment attempt alongside a course, check whether the attempt has an expiry.

How hard is it, really?

The content is not technical, but the questions are precise. People fail because they answer from team habit or from how their organization does Scrum, not from what the Scrum Guide actually says. If you can justify each rule and each timebox from first principles, the difficulty drops sharply.

Can I retake it if I fail?

Retake options depend on the certifying body's current policy and on how you purchased your attempt. Some purchases include a second attempt, others do not. Confirm the retake terms on the official site before booking, and treat a first attempt as diagnostic rather than as the plan.

What should I study first?

Start with the Scrum Guide itself - read it end to end, then again section by section. Next, focus on the definitions: accountabilities, events, artifacts and their commitments. Only after that should you take open practice assessments, and use each wrong answer as a prompt to reread the relevant paragraph.

Are there practice questions I can trust?

Use the open assessments published by the certifying body, and treat any third-party question set as a study aid rather than a source of truth. Practice questions are useful for exposing gaps; they are not authoritative. When a practice answer contradicts the Scrum Guide, the Guide wins.

Does the credential expire?

Validity terms are set by the certifying organization and should be confirmed on its site rather than assumed. Even where a credential does not formally expire, Scrum guidance evolves, so rereading the current Scrum Guide periodically matters more than the certificate itself.

What are the most common failure modes?

Answering what your team does instead of what Scrum requires; confusing the Scrum Master with a project manager or team lead; treating the Daily Scrum as a status report; and mixing up artifacts with their commitments. Also common: assuming a rule is optional because it feels impractical in your organization's context.

Do I need experience to pass?

No experience is formally required, and the assessment is knowledge-based. That said, a few months on a real Scrum team makes the questions far easier to parse, because you will recognize the situations being described. Candidates without experience should compensate by working through scenarios rather than memorizing definitions.