PST study materials
PST study resources

PST: Scrum Theory and Professional Scrum

PST · Work through your exam, one topic at a time.

All guide sections

Scrum Theory and Professional Scrum

This domain tests whether you can explain why Scrum works - empiricism, lean thinking, and the five values - and defend Professional Scrum as a coherent whole rather than a set of ceremonies. Expect situational questions that ask you to diagnose a described team against theory, not to recite definitions.

The theoretical core

  • Scrum is founded on empiricism: knowledge comes from experience, and decisions are made on what is observed. The three pillars are transparency, inspection, and adaptation, and each depends on the others.
  • Transparency requires a shared Definition of Done and a visible, ordered Product Backlog. Without it, inspection misleads and adaptation misfires.
  • Lean thinking - reducing waste and focusing on essentials - explains why Scrum prescribes so little: it deliberately leaves the how to the team.
  • The five values (commitment, focus, openness, respect, courage) are not decoration; they are the behaviors that make the pillars function. Commitment means pursuing goals, not promising a fixed scope.

What "Professional" adds

Professional Scrum is Scrum applied with discipline: accountabilities, events, and artifacts used as designed, by a self-managing team, with the values intact. It is not a lighter or heavier variant. Because Scrum is intentionally incomplete, teams add practices without rewriting the framework's rules.

Worked example

A team reports green status and rising velocity while its Increment fails the Definition of Done. Diagnosis: the artifact is not transparent, so the reported state is misleading; stakeholders cannot inspect usefully, so adaptation is guesswork; openness and courage are missing. The remedy is to make the DoD explicit and enforce it - not to add a reporting dashboard, which hides the problem further.

Traps that cost marks

  • Treating the values as soft skills unrelated to the pillars.
  • Reading "commitment" as a fixed-scope promise.
  • Assuming Scrum answers every "how" question, or that a missing practice proves Scrum is broken.
  • Choosing a tooling fix where the theory points to a transparency problem.