1.2 Scoring & Time-Management Strategy

The 85% Math And Your Error Budget

What 85% Actually Allows

The passing score is 85% of 80 questions. That equals 68 correct answers. Your error budget is therefore only 12 wrong answers for the entire assessment. Treat that number like a bank balance you cannot overdraw.

Because the margin is thin, a few careless misreads can fail you even when your knowledge is solid. Every question is worth the same single point — there is no weighting and no negative marking. The implication is strategic: a hard scenario question is worth exactly as much as an easy true/false, so never burn three minutes fighting one question while five easy points slip past on the clock. Protect the budget by banking the easy points first.

Never Leave A Blank

There is no scoring penalty for a wrong answer. An unanswered question is automatically scored wrong, so an educated guess can only help. Always select something — even on a question you flag for review — before you submit. The mathematics are simple: a blind 4-option guess is roughly 25% likely to be right, and on a multiple-choice question where you can eliminate two distractors, your odds rise to about 50%. Across a dozen guesses that is several free points.

Pacing And The Flag Feature

The assessment interface lets you flag (bookmark) a question and move on. Use it as a three-pass system:

1. First pass: answer everything you know in under 30 seconds each. Flag anything that needs more than ~45 seconds and pick a provisional answer before moving on — never leave it blank.
2. Second pass: with remaining time, revisit only flagged questions and refine your provisional answers.
3. Final check: confirm no question is unanswered and that multiple-selects have every box you intend ticked.

Guessing tactics when unsure

• Eliminate options that contradict the 2020 Scrum Guide — for example, anything calling the Scrum Master a "manager of the team," anything assigning the Product Owner authority over how work is done, or anything that adds a role the Guide does not define.
• Be suspicious of absolutes like always, never, must, or only unless the Scrum Guide actually states them. Scrum is a framework of boundaries, not rigid rules, so over-prescriptive options are frequently wrong.
• For multiple-select, count the required answers. Some questions tell you how many to pick; if so, selecting more or fewer guarantees zero. Remember there is no partial credit — selecting four of five correct options still scores zero for that whole question.
• Watch for "best" vs "correct" phrasing. When a question asks for the best action, more than one option may be defensible; choose the one most aligned with empiricism and self-management.

Why Precision On Wording Matters

Many PSM I questions hinge on a single word, and the distractors are deliberately built from outdated or near-miss phrasing. The exam is, in large part, a vocabulary test against the 2020 Scrum Guide. Internalize these high-frequency distinctions:

The Scrum Guide says the Scrum Master is accountable — not "responsible" — for the Scrum Team's effectiveness, and that the team is self-managing, deciding who does what, when, and how. Options that quietly swap an empowering verb for a controlling one are the classic trap. Read every option in full, because the test writers routinely place the most precise wording in option C or D after a plausible-but-imprecise option A. Slow, deliberate reading of the options — not deeper Scrum knowledge — is what recovers most borderline points.

A Worked Pacing Example

Suppose you finish your first pass through all 80 questions in 40 minutes, having confidently answered 60 and flagged 20 with provisional guesses. You now have 20 minutes for 20 flagged questions — a full minute each, double your average pace. That is exactly the situation the three-pass system engineers: front-load certainty, then spend your reserve where it matters. If instead you had stalled on hard questions during the first pass, you might reach minute 55 with ten questions never even read — a self-inflicted loss of easy points that alone could blow the 12-question budget.

The lesson: the clock, not the difficulty, is your real adversary. Bank every easy point first; spend deliberation time only after the floor is secured.

Common Reasons Strong Candidates Still Fail

Notice that none of these failures is a knowledge failure — they are process failures. A candidate who has read the Scrum Guide three times and scores 95%+ on Scrum Open already has the knowledge to pass; the exam day is won or lost on disciplined pacing, full reading of options, and never gifting away a blank. Rehearse the three-pass routine during timed practice so it runs on autopilot when the real clock starts.