PSL N41

It tests applied Scrum knowledge across six domains: theory and principles, the Scrum Team, Scrum events, artifacts and commitments, facilitation and team effectiveness, and coaching, mentoring, and servant leadership. Questions tend to be scenario-based, so you are judged on the quality of your reasoning and chosen action, not on reciting definitions.

Candidates with hands-on Scrum experience usually find the mechanics familiar but the scenario questions demanding, because several answers can look defensible. The hard part is picking the response most consistent with Scrum's principles and the Scrum Master's accountabilities. Deep reading of the Scrum Guide plus practice explaining your reasoning is the most reliable way to raise your score.

The certifying body determines the current format, including question types, length, and delivery method. Check its official website for the authoritative details before scheduling. Prepare for a mix of multiple-choice and scenario-based items, and read each question for what is being asked of the Scrum Master or team rather than what is technically possible.

Those figures are published by the certifying organization and can change, so confirm them on its official site rather than relying on secondhand numbers. When you know the time limit, practice pacing yourself on scenario questions, which take longer than recall items. Leave time at the end to revisit flagged questions.

Retake rules, waiting periods, and any associated costs are set by the certifying body, so check its official policy page. Before retaking, review which domains your score report shows as weakest and rebuild those areas rather than rereading everything. Most candidates improve most by studying why their original answers were wrong.

Start with the current Scrum Guide and lock down roles, events, artifacts, and commitments. Then move to scenario practice on team dynamics and facilitation, and finish with coaching and servant leadership, which are hardest to learn from text alone. Apply concepts to a real team as you go, and revisit missed questions weekly.

Three patterns dominate: answering from personal preference instead of Scrum theory, over-focusing on memorized definitions while missing the situation described, and ignoring the coaching and facilitation domains because they feel soft. Another frequent error is choosing an answer that solves the immediate problem but violates a Scrum accountability or event boundary.

It is not strictly required, but it helps considerably. Scenario questions assume you have seen a team struggle with a sprint goal, a poorly refined backlog, or a retrospective that goes nowhere. If you lack experience, simulate it: study case examples, discuss them with practitioners, and practice writing out what you would do and why.

No. Each certifying organization maintains its own exams, domains, and standards, and this page is an independent study resource with no affiliation to any of them. Verify the exact exam name and code with the certifying body before you register, and use its published outline as the final word on scope.