PSM I Cheat Sheet
Quick-reference summary of the key facts for the PSM I exam.
The Scrum Guide at a glance
Scrum is a lightweight framework for developing, delivering, and sustaining complex products. It is founded on empiricism — knowledge comes from experience, decisions are based on what is observed — and lean thinking, which reduces waste and focuses on the essentials. Scrum employs an iterative, incremental approach to optimize predictability and control risk. The whole framework fits in the Scrum Guide 2020, a short document by Ken Schwaber and Jeff Sutherland. This cheat sheet summarizes the facts the PSM I exam tests most: the pillars, the values, the accountabilities, the events and their timeboxes, the artifacts and their commitments.
The three pillars of empiricism
| Pillar | What it means |
|---|---|
| Transparency | The emerging process and work must be visible to those doing the work and those receiving it. Decisions rest on the perceived state of the artifacts; low transparency leads to decisions that diminish value and increase risk. |
| Inspection | Artifacts and progress toward agreed goals are inspected frequently and diligently to detect unwanted variation. Scrum provides cadence through its five events. Inspection without adaptation is pointless. |
| Adaptation | If a process deviates outside acceptable limits or the product is unacceptable, adjust as soon as possible to minimize further deviation. Harder when people are not empowered or self-managing. Adapt the moment you learn something new through inspection. |
The five Scrum Values
Commitment — the team commits to achieving its goals and supporting each other. Focus — the primary focus is the work of the Sprint, to make the best possible progress toward the goals. Openness — the team and its stakeholders are open about the work and the challenges. Respect — team members respect each other as capable, independent people, and are respected as such by the people they work with. Courage — team members have the courage to do the right thing and to work on tough problems. The values give direction to the team's work, actions, and behavior; when embodied, the empirical pillars come to life and build trust.
The Scrum Team
One Scrum Master, one Product Owner, and Developers. No sub-teams or hierarchies. Typically 10 or fewer people; if larger, consider reorganizing into multiple cohesive teams sharing one Product Goal, one Product Backlog, and one Product Owner. Cross-functional (all skills needed to create value each Sprint) and self-managing (internally decides who does what, when, and how). The entire team is accountable for a valuable, useful Increment every Sprint, and responsible for all product-related activities.
| Accountability | Accountable for |
|---|---|
| Product Owner | Maximizing the value of the product. Effective Product Backlog management: developing and communicating the Product Goal, creating and communicating items, ordering items, ensuring the backlog is transparent, visible, and understood. One person, not a committee. May delegate work but never accountability. Only person who can cancel a Sprint. |
| Scrum Master | Establishing Scrum as defined in the Scrum Guide, and the Scrum Team's effectiveness. A true leader who serves. Coaches the team in self-management, helps focus on high-value Increments, causes impediment removal, ensures events happen and stay in timebox. Serves the Product Owner, the team, and the organization. No authority over team members. |
| Developers | Creating any aspect of a usable Increment each Sprint. Always accountable for: creating the Sprint Backlog, instilling quality by adhering to the Definition of Done, adapting the plan daily toward the Sprint Goal, holding each other accountable as professionals. Responsible for sizing the work they will do. |
The five events and their timeboxes
| Event | Timebox (one-month Sprint) | Purpose |
|---|---|---|
| Sprint | One month or less, fixed length | Container for all other events. New Sprint starts immediately after the previous one. No changes endangering the Sprint Goal; quality does not decrease; backlog refined as needed; scope may be renegotiated with the Product Owner. |
| Sprint Planning | Max 8 hours | Initiates the Sprint. Three topics: why (Sprint Goal), what (items selected), how (plan). Whole Scrum Team collaborates; Sprint Goal finalized before the event ends. |
| Daily Scrum | 15 minutes | For the Developers, every working day, same time and place. Inspect progress toward the Sprint Goal, adapt the Sprint Backlog, produce an actionable plan for the next day. |
| Sprint Review | Max 4 hours | Inspect the outcome of the Sprint and determine future adaptations. Scrum Team presents results to key stakeholders; progress toward the Product Goal discussed; backlog may be adjusted. A working session, not a presentation or a gate. |
| Sprint Retrospective | Max 3 hours | Plan ways to increase quality and effectiveness. Inspect individuals, interactions, processes, tools, and the Definition of Done. Most impactful improvements addressed as soon as possible; may be added to the next Sprint Backlog. |
The three artifacts and their commitments
| Artifact | Commitment | Key facts |
|---|---|---|
| Product Backlog | Product Goal | Emergent, ordered list of what is needed to improve the product; the single source of work. Refinement is ongoing: breaking items into smaller, more precise items. Developers size the work. One backlog per product. |
| Sprint Backlog | Sprint Goal | Sprint Goal (why) + selected items (what) + plan (how). A plan by and for the Developers. Updated throughout the Sprint as more is learned. Enough detail to inspect progress in the Daily Scrum. |
| Increment | Definition of Done | Concrete stepping stone toward the Product Goal. Additive, verified, usable. Multiple Increments per Sprint possible. Work counts only if it meets the Definition of Done. May be delivered before the Sprint ends. |
Numbers to memorize
Exam: 80 questions, 60 minutes, 85% to pass, $200 per attempt. Sprint: max 1 month. Sprint Planning: max 8 hours. Daily Scrum: 15 minutes. Sprint Review: max 4 hours. Sprint Retrospective: max 3 hours. Scrum Team: typically 10 or fewer. Accountabilities: 3. Events: 5. Artifacts: 3. Pillars: 3. Values: 5.