PECB Certified PSM Basic common mistakes
PECB Certified PSM Basic · Understand the traps and how to avoid them.
Answering that the Scrum Master assigns tasks, prioritizes the Product Backlog, or otherwise directs the team, instead of describing facilitation, coaching, and removal of impediments.
Candidates carry over habits from traditional project manager or team-lead roles and assume authority comes with the title; exam items deliberately test whether the candidate understands servant leadership and the boundary between accountabilities.
What to do instead
For every scenario, ask 'who owns this artifact or decision?' Backlog ordering belongs to the Product Owner, self-management and work selection belong to the Developers, and the Scrum Master enables the process. Practice restating each Scrum Master action as a question or an offer of help rather than an instruction.
Treating the Sprint Retrospective as optional, or as a status meeting where the team reports progress, rather than a working session to inspect how the team worked and adapt its process.
Retrospectives in many workplaces degrade into complaint sessions or are skipped when time is short, so candidates misremember the event's purpose and confuse it with the Daily Scrum or Sprint Review.
What to do instead
Memorize the distinct inspection focus of each event: Daily Scrum inspects progress toward the Sprint Goal, Sprint Review inspects the product increment with stakeholders, Retrospective inspects individuals, interactions, processes, tools, and the Definition of Done. When a question mentions 'how we work' or 'process improvement', the answer is Retrospective.
Describing the three accountabilities as fixed job titles with sub-roles, such as a separate 'Scrum Master/team lead', a 'proxy Product Owner', or a 'QA developer', and treating the Developers as a subset of the Scrum Team.
Organizations invent hybrid titles, and candidates map those titles onto the framework instead of mapping the framework's accountabilities onto the organization.
What to do instead
Anchor on the single Scrum Team with exactly three accountabilities: Product Owner, Scrum Master, and Developers. Note that the Developers include everyone creating the increment regardless of specialty, that the Product Owner may delegate work but not accountability, and that no fourth role or sub-team exists in the framework.
Confusing the three empirical pillars or the five Scrum values, for example listing 'transparency, inspection, adaptation' as values, or naming 'commitment, focus, openness, respect, courage' as pillars.
Both lists are short, abstract, and taught together, so they blur under exam pressure; candidates recall the words without the category they belong to.
What to do instead
Build a two-column recall drill. Pillars of empiricism: transparency, inspection, adaptation. Scrum values: commitment, focus, openness, respect, courage. Attach a one-line example to each term, such as 'openness means the team surfaces bad news early', so the label is retrieved with meaning rather than by rote.
Explaining the Sprint Goal as a fixed scope commitment or as a list of backlog items that must all be completed, rather than as the single objective that gives the Sprint coherence and flexibility.
The word 'goal' invites a target-list interpretation, and many teams historically treated the Sprint as a scope contract, so candidates import that assumption.
What to do instead
State the Sprint Goal as one sentence describing why the Sprint is valuable, and remember that scope may be renegotiated with the Product Owner as more is learned while the goal stays fixed. If an item asks what happens when work turns out larger than expected, the correct reasoning is to negotiate scope with the Product Owner, not to silently drop the goal.
Giving timebox answers that are off by design, such as a two-week Daily Scrum, a Sprint Review held after the Retrospective, or a Sprint that may run indefinitely until the goal is met.
Event durations are easy to memorize superficially and easy to mix up; candidates often remember that events are timeboxed but not the specific boxes or their order.
What to do instead
Learn the events as a sequence with durations: Sprint is the container of fixed length; Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint; Daily Scrum is 15 minutes; Sprint Review is at most four hours for a one-month Sprint; Retrospective is at most three hours for a one-month Sprint. Shorter Sprints scale these down. Rehearse the order: Planning, Daily Scrums, Review, Retrospective.
Treating the Definition of Done as a team preference or an optional checklist, or letting the Product Owner unilaterally lower it to ship faster.
Candidates confuse the Definition of Done with acceptance criteria on individual items, or assume any organizational standard can be waived by whoever is accountable for value.
What to do instead
Separate the two concepts: acceptance criteria are per-item conditions for the Product Backlog item, while the Definition of Done is the shared quality standard every increment must meet. If the organization has a standard, the team must meet it at minimum; if not, the team creates one. The Definition of Done is not weakened to release an increment that does not meet it.
Presenting Scrum as a rigid, fully prescriptive methodology and answering that any deviation invalidates Scrum, instead of describing it as a lightweight framework whose purpose is to generate transparency and enable empiricism.
Training materials emphasize rules, so candidates overgeneralize rules into dogma and miss items that test judgment about purpose over mechanics.
What to do instead
Frame every practice by the purpose it serves: transparency enables inspection, inspection enables adaptation. When two answers look plausible, prefer the one that increases transparency or supports self-management over the one that enforces a procedure for its own sake. Also remember the framework intentionally leaves practices such as estimation technique or tooling to the team.
Recommending that the Scrum Master escalate to management, reassign a struggling developer, or add process controls when a team is not self-managing, rather than coaching the team to solve the problem itself.
Escalation feels decisive and is rewarded in many workplaces; candidates answer as managers rather than as servant leaders, and exam items test the coaching stance.
What to do instead
Choose the answer that builds the team's capability: ask powerful questions, teach the team to inspect and adapt in the Retrospective, and remove only genuine organizational impediments the team cannot remove itself. Reserve escalation for impediments outside the team's authority, and say so explicitly in your reasoning.
Describing adoption as a one-off rollout, such as 'train everyone, install the ceremonies, and Scrum is implemented', instead of describing incremental adoption with explicit change hypotheses and measurement.
Candidates study the framework mechanics but not the practice of applying it, so they answer with a training plan rather than an empirical improvement approach.
What to do instead
Answer adoption questions with the same empiricism as product questions: state a goal, form a hypothesis about which practice to change, run a small experiment, measure the effect, and adapt. Emphasize that the Scrum Master works with the wider organization on the environment and culture, not only with the team, and that improvement is continuous rather than a completed project.