PSM I: Independent Scrum framework study guide
Browse certifications
Exam Resources
Official learning paths, exam details, skills measured, and community resources to supplement your study.
About this study guide
This is an independently written study guide for learning and applying the Scrum framework. The practice questions are original. They are not official assessment items, are not a full exam simulation and do not guarantee a result.
The November 2020 Scrum Guide is the primary framework reference. The Guide is licensed under CC BY-SA 4.0, as stated in its official PDF. This study guide does not reproduce its wording. Scrum.org and Professional Scrum Master are trademarks of Advanced Development Methods, Inc.; this resource is not affiliated with, endorsed by, or sponsored by the provider.
Assessment facts
| Detail | Current published information |
|---|---|
| Assessment | Professional Scrum Master I (PSM I) |
| Official exam code | No separate exam code listed |
| Questions and time | 80 questions; 60 minutes |
| Formats | Multiple choice, multiple answer and True/False |
| Passing score | 85% |
| Price | US$200; verify current pricing before booking |
| Validity | Lifetime; no renewal |
| Course or prior certification | Not required |
| Status | Available in official indexed information checked on 30 October 2026; no retirement notice found |
| Official provider information | PSM I assessment |
Provider details can change. Confirm current format, price and registration requirements with the provider before booking.
Scope and study allocation
The provider’s PSM I preparation material names three competencies and does not publish numeric domain weights or question-type proportions. The bank therefore uses an editorial allocation to organize practice. It is not a claim about the real assessment’s question mix.
| Study area | Editorial share | Questions |
|---|---|---|
| Understanding and Applying the Scrum Framework | 38% | 95 |
| Developing People and Teams | 31% | 77 |
| Managing Products with Agility | 31% | 78 |
| Total | 100% | 250 |
Understanding and Applying the Scrum Framework
- Empiricism: make work visible, inspect it and adapt based on what is learned.
- Values: use commitment, focus, openness, respect and courage to guide behavior.
- Team: distinguish the Scrum Master, Product Owner and Developers accountabilities; understand cross-functionality and self-management.
- Events: recognize each event’s purpose and the Sprint’s role as the container.
- Artifacts: connect the Product Backlog, Sprint Backlog and Increment to their commitments.
- Done: use the Definition of Done to determine whether work is part of a usable Increment.
Developing People and Teams
- Self-management: the team decides how to organize its work within the framework.
- Facilitation: help people inspect and make progress without taking their decisions away.
- Coaching: support learning, team effectiveness and the organization’s understanding of Scrum.
- Professional accountability: Developers adapt their plan and hold one another accountable.
Managing Products with Agility
- Product value: the Product Owner is accountable for maximizing product value.
- Backlog management: keep the Product Goal explicit, items understandable and the backlog ordered and transparent.
- Stakeholders: use the Sprint Review to inspect outcomes and collaborate on what to do next.
- Forecasting: discuss likely outcomes from observed progress and uncertainty; a forecast is not a guarantee.
- Incremental delivery: a Done Increment can be released when it makes sense; the Sprint Review is not a release approval gate.
Framework reminders
The accountabilities are distinct
The Product Owner is accountable for product value and effective Product Backlog management. The Developers create the Sprint plan, build quality into the work, adapt their plan and hold one another accountable. The Scrum Master helps establish Scrum and improve the team’s and organization’s effectiveness. A person may delegate work, but delegation does not automatically transfer accountability.
Events have different purposes
Sprint Planning establishes the Sprint Goal, the work selected and an initial plan. The Daily Scrum is for Developers to inspect progress toward the Sprint Goal and adapt their plan. The Sprint Review is a working session for the Scrum Team and stakeholders to inspect outcomes and adapt future work. The Sprint Retrospective focuses on improving quality and effectiveness. They are not interchangeable status meetings.
Commitments make artifacts useful
The Product Goal is the long-term objective for the product and commitment associated with the Product Backlog. The Sprint Goal gives the Sprint Backlog a coherent objective. The Definition of Done describes the quality state required for an Increment. If an item does not meet the Definition of Done, it is not part of the Increment and returns to the Product Backlog for future consideration.
Treat forecasts as forecasts
Past progress can inform a forecast, but it does not make future scope, dates or outcomes certain. Use newly learned information to adjust expectations. Do not present a forecast as a promise or use an optional chart or estimation technique as if Scrum requires it.
Independent practice
The PSM I study practice and original questions are available in Guided. Twenty questions are free; full access is US$9 for one year. This independent bank has no timed exam-simulation mode. Its question allocation and selected-response mix are editorial.
Sources and relationship
- Scrum Guide, November 2020 - framework facts and terminology.
- PSM I assessment information - confirm current registration, price and assessment details.
- PSM I suggested reading - current preparation guidance and assessment scope.
The public links above avoid embedding or framing provider content. This page uses the provider’s marks only to identify the assessment it discusses.