Study Timeline

How Long to Study for Scrum.org PSM I

A complete week-by-week study plan for the Scrum.org PSM I (Medium difficulty, ~85% pass rate).

8

Weeks

5

Hrs/Week

40

Total Hours

~85%

Pass Rate

Read the source document end to end and take a baseline
Week 1

4-6 hours this week

  • Download the November 2020 Scrum Guide from scrumguides.org and read it once without stopping to take notes.
  • Take the free Scrum Open assessment at scrum.org, 30 questions drawn at random from a larger pool, and record your score. Scrum.org gives feedback during this test, unlike the paid one.
  • Bookmark Scrum.org's Suggested Reading for Professional Scrum Master I page, which lists the exact focus areas PSM I draws on.
  • Write down every term in the Scrum Guide you could not define from memory. Expect Product Goal, Definition of Done, Sprint Goal, refinement and self-management to be on that list.
  • Read Scrum.org's Accountabilities in Scrum article to fix the 2020 change from roles to accountabilities in your head.
Empiricism, the pillars and the five values
Week 2

4-5 hours this week

  • Reread the Scrum Theory and Scrum Values sections of the Scrum Guide and write out transparency, inspection and adaptation with one example of each from your own workplace.
  • Work through Scrum.org's five-part Maximize Scrum blog series on Focus, Openness, Courage, Commitment and Respect.
  • Download the Scrum Values poster from Scrum.org and pin the five values where you can see them.
  • Build a one-page table listing practices you have used that Scrum does not prescribe, such as story points, burndown charts, planning poker and the three questions in the Daily Scrum. Scrum.org's own prep page tells you to know what is and is not part of the framework.
  • Retake the Scrum Open and note which questions you now get right for the right reason rather than by elimination.
The Scrum Team and the three accountabilities
Week 3

5-6 hours this week

  • Memorise the composition rule: one Scrum Master, one Product Owner, Developers, no sub-teams, no hierarchies, typically 10 or fewer people.
  • List the Scrum Guide's stated Scrum Master services to the Scrum Team, to the Product Owner and to the organisation, three lists, and be able to say which service belongs to which list.
  • Read Scrum.org's The 8 Stances of a Scrum Master and Evolution of the Scrum Master.
  • Answer this in writing: who decides how many Product Backlog items enter the Sprint, and who decides how the work gets done. Both answers are in the Scrum Guide and both appear on the test.
  • Practise explaining the whole framework aloud to someone who has never used Scrum, in under five minutes. Scrum.org's prep page recommends this exercise by name.
Events and timeboxes
Week 4

5-6 hours this week

  • Write the five events and their maximum durations for a one-month Sprint from memory: Sprint one month or less, Sprint Planning 8 hours, Daily Scrum 15 minutes, Sprint Review 4 hours, Sprint Retrospective 3 hours.
  • Learn the ordering rule: the Sprint Review is the second to last event and the Sprint Retrospective concludes the Sprint.
  • Read Scrum.org's Sprint Review: Much More Than a Demo and the Scrum Myth article on whether the Scrum Master must attend the Daily Scrum.
  • Learn who can cancel a Sprint and on what grounds, because the Scrum Guide gives that authority to exactly one person.
  • Take the Scrum Open twice this week and target 100 percent both times.
Artifacts, commitments and Done
Week 5

5-6 hours this week

  • Map each artifact to its commitment three times from blank paper: Product Backlog to Product Goal, Sprint Backlog to Sprint Goal, Increment to Definition of Done.
  • Read the Increment and Definition of Done sections of the Scrum Guide twice and write out what happens to an item that does not meet the Definition of Done.
  • Read Getting to Done: Creating Good Sprint Goals on Scrum.org and draft three Sprint Goals for work you actually did last month.
  • Work out from the Scrum Guide whether an Increment can be released mid-Sprint, and find the sentence that settles it.
  • Take the Product Owner Open assessment. Scrum.org recommends it for PSM I candidates because artifact questions are often written from the Product Owner's side.
Developing people and teams
Week 6

4-5 hours this week

  • Read Scrum.org's Resources for Growing as a Scrum Master learning series, concentrating on the facilitation and coaching material.
  • Read chapters on self-management and impediments in Mastering Professional Scrum by Stephanie Ockerman and Simon Reindl, which Scrum.org lists in its suggested reading.
  • Write ten scenario questions of your own in the form what should the Scrum Master do, and answer each with a Scrum Guide sentence rather than an opinion.
  • Read the ScrumBut page on Scrum.org and identify at least two ScrumButs in the team you work with now.
  • Take the Scrum Developer Open assessment for a third perspective on the same framework.
Managing products with agility
Week 7

5-6 hours this week

  • Read the Product Backlog and Product Goal sections of the Scrum Guide alongside Scrum.org's How Do You Define a Product resource.
  • Learn what the Scrum Guide does and does not say about estimation, refinement time and velocity. It prescribes no technique and sets no refinement percentage.
  • Read Scrum: A Pocket Guide by Gunther Verheyen, another title on Scrum.org's suggested reading list, for the chapter on forecasting and release planning.
  • Practise ordering a real backlog of at least 20 items and defend the order in one sentence each.
  • Run a timed set of 80 mixed questions from open assessments and blog quizzes in 60 minutes to rehearse the pace.
Timed rehearsal and the attempt
Week 8

3-4 hours this week

  • Score 100 percent on the Scrum Open three times in a row, finishing each in under 15 minutes.
  • Read the Scrum Guide once more in a single sitting the day before your attempt.
  • Set up the test conditions in advance: a wired or stable connection, a browser with the Scrum Guide open in a second tab, and 75 uninterrupted minutes booked out even though the timebox is 60.
  • Buy the 200 dollar password only when your open assessment scores are consistently at 100 percent, since the password is valid for one attempt and does not expire.
  • Take the test. Aim to reach question 40 by minute 25 and to finish your first pass by minute 45, leaving 15 minutes for flagged items.
Working Full-Time Schedule

Duration: 12 weeks

Hours/week: 4 hours

Daily: ~1 hours on weeknights

Weekends: 3-4 hours Saturday + Sunday

Study during lunch breaks and commute time. Use weekends for deeper study sessions and practice tests.

Weekend-Only Schedule

Duration: 16 weeks

Hours/week: 3 hours

Saturday: 4-5 hours of focused study

Sunday: 3-4 hours of practice tests

Longer timeline but sustainable. Review flashcards on weeknights for 15-20 minutes to maintain retention.

Frequently Asked Questions

How long does it take to study for the Scrum.org PSM I?

Plan for 8 weeks of dedicated study at 5 hours per week (40 total hours). If studying while working full-time, extend to 12 weeks.

Can I pass the Scrum.org PSM I in 2 weeks?

It's unlikely for most candidates. The Scrum.org PSM I is rated "Medium" difficulty and typically requires 8 weeks of preparation. Rushing increases your risk of failing and paying the exam fee again.

How many hours a day should I study for Scrum.org PSM I?

Aim for 1-1 hours per day on weekdays. Quality matters more than quantity, use active recall and practice tests rather than passive reading.

Is Scrum.org PSM I hard to pass?

The Scrum.org PSM I is rated "Medium" difficulty with a pass rate of ~85%. With proper study, most candidates pass on their first attempt.

Ready to start your Scrum.org PSM I journey?

Get the complete exam guide with tips, resources, and practice questions.

View Scrum.org PSM I Guide