PST common mistakes
PST · Understand the traps and how to avoid them.
Treating the three empirical pillars as 'transparency, inspection, adaptation' but then answering scenario questions as if inspection alone produces adaptation, without naming the required adjustment or the transparency precondition.
Candidates memorize the three words as a list and never practice applying them to a scenario, so they pick an answer that names a pillar without showing the causal link the question is testing.
What to do instead
For each practice scenario, write one sentence per pillar stating what is transparent, who inspects, what was adapted, and what breaks if any pillar is missing. Drill until the causal chain is automatic.
Confusing Scrum's 'rules' with 'processes, techniques, and tactics' and asserting that the Scrum Guide prescribes estimation, story points, or a specific board.
Real workplaces mix framework rules with local practice, and candidates import their team's habits as if they were normative.
What to do instead
Re-read the Scrum Guide's definition of Scrum and mark every sentence that is a rule versus a suggestion. Build a two-column list: 'required by the framework' versus 'chosen by the team', and check each answer choice against it.
Assigning accountability for the Daily Scrum, Sprint Retrospective, or artifact ordering to the wrong role (for example, saying the Scrum Master runs the Daily Scrum or that the Product Owner facilitates the Retrospective).
Job titles in the candidate's organization map poorly onto Scrum accountabilities, and 'facilitator' language in training gets over-applied to every event.
What to do instead
Memorize the event-to-accountable-party table: Daily Scrum is for Developers; Sprint Planning, Refinement activity, and Product Backlog ordering belong to the Product Owner; Sprint Retrospective is scoped by the Scrum Master's coaching of the team. Test yourself by writing who is accountable for each event's purpose and each artifact's commitment.
Describing the Product Owner as a committee, a 'proxy', or a role shared across several people without noting that accountability must remain with one person even if work is delegated.
Organizations commonly split the PO role, and candidates describe their reality rather than the accountability model.
What to do instead
Practice explaining delegation versus accountability in one paragraph: the PO may delegate work but cannot delegate accountability. Then answer scenario questions by asking 'who can be held accountable?' rather than 'who does the work?'.
Treating the Sprint as a fixed container whose scope cannot change, and rejecting scope clarification or renegotiation between Product Owner and Developers during the Sprint.
Candidates conflate 'no changes that endanger the Sprint Goal' with 'no changes at all', a common misunderstanding reinforced by change-averse workplaces.
What to do instead
Write the exact condition: scope may be clarified and renegotiated with the Product Owner as more is learned, as long as it does not endanger the Sprint Goal. Practice classifying sample mid-Sprint changes as allowed or not allowed against that test.
Running Sprint Planning as a task-assignment meeting and answering that the Scrum Master or Product Owner decides who does what, rather than the Developers self-managing the selection of work.
Traditional project-management habits and hierarchy-driven workplaces make assignment feel like the natural answer.
What to do instead
Rehearse the Sprint Planning flow: why is this Sprint valuable, what can be done, how will the work get done. For each, state who owns the decision. Then practice answering 'who decides?' questions with 'the Developers' whenever the decision is about how the work is done.
Teaching by walking through the Scrum Guide section by section, then being unable to answer questions about applying Scrum in messy real situations.
It is the easiest preparation path and feels authoritative, but it transfers definitions rather than the ability to reason about trade-offs, which is what a Professional Scrum course is meant to build.
What to do instead
Restructure each session around a decision or tension (for example, a Sprint Goal that becomes obsolete mid-Sprint) and let the guide text surface as the resolution. Prepare at least one facilitated exercise per learning objective.
Facilitating with a lecture-and-slide default and using discussion only as a break, so learners leave with vocabulary but no changed behaviour.
Lecture is comfortable and time-efficient for the trainer, and candidates underestimate how much of Professional Scrum training is designed as practice with feedback.
What to do instead
Apply a concrete ratio in your lesson plans: for every concept, plan an activity where learners produce something (a Sprint Goal, a refinement question, a Retrospective format) and receive feedback. Time-box the lecture portion explicitly.
Treating the Professional Scrum Master, Product Owner, and Developer credentials as interchangeable, or assuming one assessment covers all accountabilities.
The names sound like seniority levels and candidates assume a single ladder rather than distinct accountability-focused credentials.
What to do instead
Build a comparison table of the Professional Scrum assessments you are targeting: which accountability each focuses on, what evidence of competence it implies, and what the recommended preparation path is. Verify current details on the certifying body's own site rather than secondary sources.
Preparing for scenario-based assessment items by memorizing definitions and single correct phrases, then choosing the answer that sounds most Scrum-pure instead of the one that best fits the described situation.
Definition recall is easier to practice than judgment, and 'most Scrum-pure' heuristics fail on items where several answers are technically consistent with the guide but only one addresses the stated problem.
What to do instead
Practice with scenario stems only: read the situation, name the constraint and the accountable party, eliminate answers that violate a rule, then choose among the remainder by asking which action best serves the stated purpose. Justify each elimination in writing before checking the answer.