How to Prepare for a Scrum Master Exam: A Study Plan

Passing a Scrum Master exam is less about memorising facts and more about understanding how Scrum works and why. Exams from different providers vary in length, format and passing score, but almost all of them are based on the Scrum Guide, and almost all of them test whether you can apply it to realistic situations. This guide gives you a step-by-step study plan, the topics that most often catch people out, techniques for scenario questions, and practical advice for exam day.

Key takeaways

• Start by checking the exact format of your own exam with your provider.
• The Scrum Guide, current edition November 2020, is the foundation for most Scrum Master exams.
• Understanding why each rule exists matters more than memorising the rule.
• Practice questions are most useful when you review every wrong answer against the Scrum Guide.
• Two to three weeks of steady study is a reasonable plan for someone new to Scrum.

Step 1: Know your exam

Before you start studying, find out exactly what your exam looks like. Details differ between providers and can change over time, so always check the current information from the organisation you are certifying with. Useful things to confirm:

• How many questions there are and how long you have
• The passing score
• Whether the exam is open book or closed book
• The question types, such as multiple choice, multiple answer or true/false
• How many attempts are included, and the policy for retakes
• The language of the exam
• How and where it is delivered, for example online with a webcam or at a test centre
• How long the certification is valid and whether it needs renewing

Knowing these details early shapes how you prepare. A closed-book exam needs more memorisation; a short, timed exam needs practice at answering quickly.

What Scrum Master exams usually test

Most Scrum Master exams cover the same core areas, all drawn from the Scrum Guide:

• Scrum theory: empiricism, lean thinking, and the three pillars of transparency, inspection and adaptation
• Scrum values: commitment, focus, openness, respect and courage
• The Scrum Team: the accountabilities of the Scrum Master, Product Owner and Developers, and what self-management means
• The events: the Sprint, Sprint Planning, Daily Scrum, Sprint Review and Sprint Retrospective, including their purpose and timeboxes
• The artifacts and commitments: Product Backlog and Product Goal, Sprint Backlog and Sprint Goal, Increment and Definition of Done
• Applying Scrum: scenario questions about what should happen in a particular situation

Our articles on Scrum events and Scrum artifacts cover two of the biggest areas in detail, and the complete Scrum Master guide gives an overview of the whole framework.

Step 2: Read the Scrum Guide, properly

The Scrum Guide is short, free and written by the creators of Scrum, Ken Schwaber and Jeff Sutherland. It is the source most exams are based on. Reading it once is not enough. A three-pass approach works well:

1. First read: read it straight through for the overall picture. Do not take notes yet.
2. Second read: go slowly, section by section. Write down every accountability, event, artifact, commitment and timebox in your own words.
3. Third read: for each rule, ask yourself why it exists and what would go wrong without it. This is the understanding that scenario questions test.

Make sure you study the 2020 edition

Many older study materials are based on earlier editions of the Scrum Guide. The November 2020 edition made several important changes that exams now reflect:

• Developers replaced the earlier term "Development Team", emphasising one Scrum Team rather than a team within a team.
• Accountabilities is used to describe the Scrum Master, Product Owner and Developers.
• Product Goal was introduced as the commitment for the Product Backlog.
• Commitments were added for each artifact: Product Goal, Sprint Goal and Definition of Done.
• Self-managing replaced "self-organising".
• Sprint Planning gained a third topic: why the Sprint is valuable.
• The three Daily Scrum questions from earlier editions were removed; the Developers choose their own structure.
• Lean thinking was added alongside empiricism as a foundation of Scrum.
• The guide became shorter and less prescriptive overall.

If a practice question uses terms like "Development Team" or asks about the "three questions", it was probably written for an older edition.

Step 3: Understand the why, not just the what

Many exam questions describe a situation and ask what should happen next, or who is accountable for something. Memorised facts help, but they are not enough. You need to understand the reasoning behind the framework. For example:

• The Sprint Goal stays stable during the Sprint because it gives the team focus and coherence, while the plan to reach it can change.
• The Daily Scrum belongs to the Developers because they are self-managing and responsible for their own plan.
• Work that does not meet the Definition of Done returns to the Product Backlog because presenting unfinished work would destroy transparency.
• Sprints are short because shorter cycles create more learning and limit the risk of cost and effort.

When you understand the purpose, you can answer questions about situations the Scrum Guide does not describe word for word.

Step 4: Know the rules that catch people out

These points appear often in Scrum Master exams and are easy to get wrong:

• The Scrum Master does not assign tasks. The Developers are self-managing.
• The Daily Scrum is for the Developers and is timeboxed to 15 minutes.
• Only the Product Owner can cancel a Sprint, and only if the Sprint Goal becomes obsolete.
• Sprints are a fixed length of one month or less, and a new Sprint starts immediately after the previous one ends.
• Timeboxes for a one-month Sprint: Sprint Planning 8 hours, Sprint Review 4 hours, Sprint Retrospective 3 hours. Shorter Sprints usually have shorter events.
• A timebox is a maximum, not a required length.
• Work that does not meet the Definition of Done is not part of the Increment and returns to the Product Backlog.
• Product Backlog refinement is an ongoing activity, not a Scrum event.
• The Product Owner is one person, not a committee, although they may represent the needs of many stakeholders.
• The Product Owner is accountable for the Product Backlog, even if they delegate some of the work.
• The Developers are responsible for sizing Product Backlog items.
• The Sprint Backlog belongs to the Developers.
• A Scrum Team is typically ten or fewer people, with no sub-teams or hierarchies.
• Several teams on one product share one Product Backlog, one Product Owner, one Product Goal and one Definition of Done.
• An Increment can be released before the Sprint Review. The Review is not a gate for releasing value.

Step 5: Learn the key terms

Exams often test precise meanings. Make sure you can explain each of these in one sentence:

• Empiricism: knowledge comes from experience, and decisions are based on what is observed.
• Timebox: the maximum length of an event.
• Self-managing: the team decides internally who does what, when and how.
• Cross-functional: the team has all the skills needed to create value each Sprint.
• Product Goal: the long-term objective for the Scrum Team, held in the Product Backlog.
• Sprint Goal: the single objective for the Sprint.
• Definition of Done: the formal description of the state the Increment must reach to meet quality measures.
• Increment: a usable, verified step toward the Product Goal.
• Refinement: breaking down and adding detail to Product Backlog items.
• Impediment: anything that slows the team down or blocks progress toward the Sprint Goal.

Step 6: Practise with questions, the right way

Practice questions show you how exams phrase things and where your gaps are. But taking dozens of practice tests without reviewing them teaches very little. A more effective approach:

1. Take a practice test under timed conditions.
2. For every question you got wrong, or guessed, find the part of the Scrum Guide that explains the right answer.
3. Write it down in an "error log": the question topic, why you got it wrong, and the correct reasoning.
4. Review your error log before the next practice test.

Be careful with practice questions from unknown sources. Some are outdated or simply wrong. If a practice answer contradicts the Scrum Guide, trust the Scrum Guide.

Techniques for scenario questions

• Read the whole question first. A single word, such as "first" or "best", can change the answer.
• Identify who is accountable. Many questions come down to whether something belongs to the Scrum Master, the Product Owner or the Developers.
• Eliminate answers that break the Scrum Guide. An option where the Scrum Master assigns tasks, for example, is almost certainly wrong.
• Prefer answers that support self-management and empiricism. Scrum favours letting the team decide and learning from what actually happens.
• Watch out for absolutes. Words like "always" and "never" deserve a second look.
• Choose the best answer, not just a correct one. Several options may sound reasonable; pick the one that fits the Scrum Guide most closely.

Step 7: Make a study schedule

A three-week plan for people new to Scrum

• Week 1: read the Scrum Guide three times using the approach above. Learn the accountabilities, events, artifacts and commitments. Read our articles on what a Scrum Master does and the Scrum events.
• Week 2: focus on the why behind each rule. Study the key terms. Start practice questions and keep an error log.
• Week 3: take timed practice tests, review your error log daily, and focus on your weakest areas. Re-read the Scrum Guide one final time before the exam.

A one-week plan for experienced practitioners

If you already work with Scrum, your challenge is often unlearning habits that differ from the Scrum Guide. Spend the first days reading the 2020 edition carefully, noting where your team's practice differs from the guide. Then move straight to timed practice questions and your error log.

Sample scenario questions with explanations

These practice questions are written in the style of many Scrum Master exams. They are not taken from any real exam. Each answer is explained using the Scrum Guide.

Question 1

During the Sprint, a senior stakeholder asks one of the Developers to add an urgent new feature. What should happen?

Best answer: the Developer should direct the stakeholder to the Product Owner.

Why: the Product Owner is accountable for the Product Backlog and decides what the team works on next. During the Sprint, no changes should be made that endanger the Sprint Goal. The Product Owner can decide whether the request goes into the Product Backlog for a future Sprint. Adding it directly to the Sprint Backlog without the Product Owner would bypass that accountability.

Question 2

Halfway through the Sprint, the Developers realise they cannot finish all the items they selected. What should they do?

Best answer: work with the Product Owner to renegotiate the scope of the Sprint Backlog, without affecting the Sprint Goal.

Why: the Scrum Guide says scope may be clarified and renegotiated with the Product Owner as more is learned. The Sprint Goal gives the Developers flexibility in the exact work needed to achieve it. Extending the Sprint or lowering quality would both break the Scrum Guide.

Question 3

Who is required to attend the Daily Scrum?

Best answer: the Developers.

Why: the Daily Scrum is an event for the Developers. The Scrum Master makes sure it takes place and is kept within 15 minutes. If the Product Owner or Scrum Master are actively working on items in the Sprint Backlog, they take part as Developers.

Question 4

At the end of the Sprint, one item is almost finished but does not yet meet the Definition of Done. Can the team show it at the Sprint Review?

Best answer: no. It is not part of the Increment and returns to the Product Backlog.

Why: the Scrum Guide states that if a Product Backlog item does not meet the Definition of Done, it cannot be released or even presented at the Sprint Review. It returns to the Product Backlog for future consideration.

Common mistakes when preparing

• Studying from outdated material. Resources based on older editions of the Scrum Guide use terms and rules that have changed.
• Relying on workplace habits. Many teams use Scrum in their own way. The exam tests the Scrum Guide, not how your company does it.
• Memorising without understanding. Scenario questions quickly expose gaps in reasoning.
• Taking practice tests without reviewing them. The learning comes from understanding your mistakes.
• Trusting every practice question. Some online questions are simply wrong. When in doubt, go back to the Scrum Guide.
• Leaving everything to the last few days. Short, regular study sessions work better than one long cram.

How to study while working full time

Most people preparing for a Scrum Master exam are also working. A few habits make it manageable:

• Study little and often. Thirty to forty-five minutes a day is more effective than one long weekend session.
• Use your work as a case study. After each Scrum event at work, compare what happened with what the Scrum Guide describes.
• Keep the Scrum Guide on your phone. Re-reading a section during a commute adds up quickly.
• Book your exam date. A fixed date turns "someday" into a plan.
• Tell your team. Colleagues who use Scrum can be a useful source of discussion and questions.

On exam day

• Check your setup early. For online exams, test your internet connection, camera and computer in advance, and make sure you know how the exam platform works.
• Choose a quiet space where you will not be interrupted.
• Manage your time. Work out roughly how long you have per question, and do not spend too long on any single one.
• Flag and move on. If you are unsure, mark the question and come back to it at the end.
• Read every option before choosing, even if the first one looks right.
• Stay calm. A difficult question early on does not mean the whole exam will be hard.

After the exam

If you pass, share your credential. Digital badges, like the ones issued through LiveCertification, can be added to your professional profiles, and anyone can verify them. Then keep learning: certification is the start of the Scrum Master journey, not the end. Running a good Retrospective is a practical next skill to build.

If you do not pass, review your results, update your error log, and focus on the weakest areas before your next attempt. Most people who fail the first time pass after targeted revision.

The Scrum Master Plus exam

If you are preparing for Scrum Master Plus (Associate), here is what is included:

• 16 hours of training
• An online exam on ExamVault by CertExpert
• Three exam attempts included in the fee
• A certificate and a digital badge verifiable on LiveCertification
• A credential valid for two years

There are no formal prerequisites; experience in a project environment is helpful but not required. Experienced Scrum Masters can continue with Scrum Master Plus (Professional).