Scrum Certifications: PSM, PSPO and Current Scrum Skills

Scrum certification is not controlled by a single universal certification body. Scrum itself is defined by the Scrum Guide, while organizations such as Scrum.org, Scrum Alliance and other training providers issue their own credentials around Scrum roles and practices. That distinction is important because eligibility, training requirements, assessment style and renewal rules vary by provider even when the certifications cover similar Scrum concepts.

For candidates using a general Scrum certification page, the safest approach is to begin with the current Scrum Guide and then map the provider-specific credential to it. Scrum.org's Professional Scrum certifications provide a useful current example because they are assessment-based, do not require class attendance, and include progressive tracks for Scrum Masters and Product Owners. Other providers may require formal training or periodic renewal, so their rules should be checked separately rather than assumed to match Scrum.org.

The Scrum Guide is the common foundation

The official Scrum Guide remains the definitive description of the framework. The current official version is the November 2020 edition by Scrum co-creators Ken Schwaber and Jeff Sutherland. It defines Scrum through empiricism, Scrum Values, the Scrum Team, the accountabilities of Product Owner, Scrum Master and Developers, the events, the artifacts and their commitments.

Candidates should be able to explain how those elements reinforce one another. Sprint Planning creates a plan for the Sprint, the Daily Scrum supports inspection and adaptation toward the Sprint Goal, the Sprint Review examines the product and future direction, and the Sprint Retrospective focuses on improving quality and effectiveness. The Scrum roles, events and artifacts are easier to remember when studied as a system rather than as separate definitions.

A strong study method is to take a real product problem and run it through one Sprint on paper. Define a Product Goal, create Product Backlog items, select work around a Sprint Goal, decide what “Done” means, inspect progress and adapt. When a rule from the Scrum Guide feels abstract, place it into that scenario and ask what problem the rule is designed to expose or prevent.

PSM I validates foundational Scrum Master understanding

Scrum.org's Professional Scrum Master I certification is designed to validate fundamental understanding of Scrum and the Scrum Master accountabilities. The current assessment expects candidates to understand the framework as defined in the Scrum Guide and apply it to real situations. Scrum.org requires a score of 85 percent or higher for its professional-level assessments and does not require candidates to attend a class before attempting PSM I.

PSM I practice can supplement scenario work, but successful preparation requires scenario reasoning. Memorizing that a Scrum Master “removes impediments” is not enough; candidates must understand how the Scrum Master helps the team become more effective without taking over the Developers' self-management or acting as a traditional task manager.

Practice identifying anti-patterns. A manager assigns tasks during the Daily Scrum, the Sprint Goal changes casually midway through a Sprint, unfinished work is counted as Done, or a Product Owner delegates all ordering decisions to a committee. For each scenario, identify which Scrum principle is being weakened and what a Scrum Master should do to restore transparency, inspection and adaptation.

PSM II expects deeper judgment, coaching and organizational awareness

Professional Scrum Master II builds on the same framework but expects a more advanced understanding of the Scrum Master role. Candidates need to reason about coaching, facilitation, team effectiveness, product value and organizational impediments rather than only recalling framework rules. Experience matters because advanced questions often involve imperfect situations where several actions sound plausible.

The PSM II exam practice can support targeted practice after the fundamentals are strong. Build preparation around difficult conversations: a Product Owner is inaccessible, stakeholders pressure the team to bypass quality, managers demand individual utilization metrics, or several teams are optimizing locally while product outcomes decline. Ask what intervention helps the system learn rather than merely suppressing the symptom.

It also helps to distinguish the Scrum Master from a conventional project manager. The comparison in Scrum Master versus project manager highlights why Scrum places different accountabilities on the team. The Scrum Master enables effective use of Scrum; the role does not become a substitute project owner, line manager or dispatcher of tasks.

PSPO certifications focus on value and product accountability

Scrum.org's Professional Scrum Product Owner track validates understanding of Product Ownership and maximizing value. PSPO I is the foundational assessment, while PSPO II expects more advanced judgment about product vision, backlog management, release planning, business strategy and stakeholder collaboration. The Product Owner is accountable for maximizing product value and effective Product Backlog management, not simply for writing user stories.

PSPO I practice is most useful when paired with practice that connects Product Goal, ordering and stakeholder evidence. Take a backlog with more work than the team can deliver and decide how to order it when value, risk, learning and dependencies conflict. Then explain the rationale without relying on a mechanical prioritization formula.

For PSPO II, go beyond backlog mechanics. Practice product strategy, outcome measurement, experimentation and stakeholder trade-offs. A strong Product Owner should be able to explain why the team is building something, what evidence would show that the investment is working, and how new information would change the next decision.

Training and certification are separate in the Scrum.org model

Scrum.org explicitly separates training from certification. Classes are recommended and can provide structured learning, but attendance is not required to purchase and attempt a Professional Scrum assessment. Certification is awarded by passing the assessment rather than by completing the class alone. This is different from provider models in which course attendance is an eligibility requirement.

That difference affects preparation. Self-study candidates need to create their own feedback loops. Start with the Scrum Guide, use Scrum.org's Open Assessments, review areas of weakness and apply the concepts to real situations. A class can accelerate learning by exposing candidates to facilitation exercises and expert discussion, but simply attending does not replace the need to demonstrate knowledge on the assessment.

Do not mix provider rules. Scrum Alliance certifications operate under their own training and renewal structure, while Scaled Agile certifications apply Scrum within the larger SAFe operating model. A person can learn from all three ecosystems, but a requirement from one should not be presented as though it automatically applies to another.

Scrum.org certifications do not require renewal

One current-status difference is especially important: Scrum.org states that Professional Scrum certifications are lifetime credentials with no annual renewal cost or continuing-education requirement. Once a candidate passes the applicable assessment, the certification remains on the holder's profile. That policy applies to credentials such as PSM and PSPO under the Scrum.org model.

Lifetime certification does not mean lifetime competence. Scrum practice develops through experience, product context and continued learning. Teams encounter new technology, organizational structures and market conditions even when the framework itself has not changed. Certified practitioners should continue improving facilitation, product thinking, technical quality and evidence-based decision-making because the credential does not force a renewal cycle to create that discipline.

Maintain a practice journal after certification. Record one difficult Scrum situation each week, what happened, which Scrum principle was relevant, how the team responded and what evidence showed whether the intervention helped. Over time this becomes more valuable than a collection of memorized exam answers because it connects the framework to observed consequences.

Prepare to apply Scrum, not merely recite it

The best final preparation is scenario-based. Take common misconceptions and test them against the Scrum Guide. The Daily Scrum is not a status meeting for the Scrum Master. The Product Owner is one person, not a committee. Developers are self-managing. A Sprint can produce learning even when forecasts change, but work only counts toward the Increment when it meets the Definition of Done. The Sprint Goal provides coherence without freezing every detail of the plan.

Then connect each rule to value. Scrum is intentionally lightweight because it creates frequent opportunities to inspect reality and adapt. If a team performs every event but avoids difficult evidence, it can still be doing poor Scrum. Candidates should understand why transparency matters, what makes inspection meaningful and how adaptation happens before problems compound.

Before buying any exam, verify the current provider page, assessment name, passing score, languages, attempt policy and renewal status. If the goal is PSM or PSPO, use Scrum.org's live assessment pages and the current Scrum Guide as primary references. If the goal is a Scrum Alliance, Scaled Agile or another provider credential, use that provider's current rules. The framework can be shared while the certification mechanics remain different. Keeping those layers separate is the simplest way to build an accurate, durable Scrum certification plan.

For teams studying together, rotate the perspective in each scenario. Ask one person to answer as Product Owner, one as Scrum Master and another as a Developer. Differences in accountability become much clearer when the same situation is viewed from all three positions. This also exposes answers that sound collaborative but quietly move decision rights to the wrong role.