Scrum Methodology Cheat Sheet

Updated 2026-07-17

🎯Take a practice test on this topic7 practice tests · 187 questions→

🧠Study flashcards on this topic126 cards · spaced repetition→

Scrum is a lightweight agile framework designed to help teams deliver value iteratively through fixed-duration sprints (typically 1-4 weeks). Founded on empiricism and lean thinking (decisions grounded in observation and experimentation, waste ruthlessly eliminated), Scrum relies on three foundational pillars: transparency, inspection, and adaptation. The framework defines three accountabilities (Product Owner, Scrum Master, Developers), five time-boxed events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective), and three artifacts (Product Backlog, Sprint Backlog, Increment), each paired with a commitment that enhances focus and transparency. Unlike traditional project management, Scrum enables self-managing, cross-functional teams to respond rapidly to change while maintaining a sustainable pace and delivering a usable Increment at the end of every sprint.

What This Cheat Sheet Covers

This topic spans 22 focused tables and 128 indexed concepts, 126 flashcards, 7 practice tests with 187 questions. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.

Table 1: Core Scrum Roles (Accountabilities)Table 2: Scrum Events (Ceremonies)Table 3: Scrum ArtifactsTable 4: Artifact Commitments (2020 Scrum Guide Addition)Table 5: Scrum ValuesTable 6: Empiricism and Lean Thinking FoundationsTable 7: Estimation TechniquesTable 8: User Story ComponentsTable 9: Backlog Prioritization TechniquesTable 10: Scrum MetricsTable 11: Scrum Best PracticesTable 12: Common Scrum Anti-PatternsTable 13: Definition of Done vs Acceptance CriteriaTable 14: Impediment ManagementTable 15: Scaling Scrum FrameworksTable 16: Scrum in Practice (Team Dynamics)Table 17: Product Roadmap and VisionTable 18: Work in Progress (WIP) ManagementTable 19: Scrum and Technical PracticesTable 20: Scrum 2020 Guide Key ChangesTable 21: Retrospective TechniquesTable 22: Evidence-Based Management (EBM)

Quick IndexSubscribe to unlock

A jump-to index of every table row in this cheat sheet.

Mind MapSubscribe to unlock

An interactive map of every table and concept in this topic.

Table 1: Core Scrum Roles (Accountabilities)

Scrum defines just three accountabilities, and the distinctions between them trip up most new teams. The Product Owner owns what and why, the Developers own how, and the Scrum Master keeps the team effective without managing anyone. Together they form one self-managing unit: no sub-teams, no hierarchies, and nobody handing out tasks.

Role	Example	Description
Product Owner	`product_owner.maximize_value()` `product_owner.manage_backlog()`	• Accountable for maximizing product value resulting from the Scrum Team's work • accountable for effective Product Backlog management: develops the Product Goal, creates and orders items, keeps the backlog transparent • one person, not a committee; may delegate the work but remains accountable, and the organization must respect their decisions.
Scrum Master	`scrum_master.improve_effectiveness()` `scrum_master.coach_team()`	• Accountable for the Scrum Team's effectiveness and for establishing Scrum as defined in the Guide • true leader who serves: coaches self-management, causes the removal of impediments, keeps events productive and within the timebox • serves the Product Owner and the organization too; not a project manager and assigns no work.
Developers	`developers.create_increment()` `developers.self_manage()`	• Anyone committed to creating any aspect of a usable Increment each Sprint, not just programmers ("developers" is used to simplify, not to exclude) • always accountable for the Sprint Backlog, instilling quality via the Definition of Done, and adapting the plan daily • self-manage who does what, and hold each other accountable as professionals.

Table 2: Scrum Events (Ceremonies)

Scrum defines five events: the Sprint, a fixed-length container, plus the four inspect-and-adapt events that run inside it. Each of the four carries a maximum duration stated for a one-month Sprint, and the Guide says only that shorter Sprints are usually shorter, not that the timebox scales by formula. Backlog Refinement is widely practiced but stays an ongoing activity rather than an official event.

Event	Example	Description
Sprint	`sprint(duration="2 weeks")` `sprint.timebox = "one month or less"`	• Fixed-length container for all other Scrum events (one month or less) • a new Sprint starts immediately after the previous one ends • only the Product Owner may cancel a Sprint, and only if the Sprint Goal becomes obsolete.

The rest of this section is part of the full cheat sheet

Table 3: Scrum Artifacts

Scrum has exactly three artifacts, and each one belongs to someone different. The Product Owner orders the Product Backlog, the Developers own the Sprint Backlog as their own working plan, and the Increment is the usable result that stacks on top of every Increment before it. Get those ownership lines right and most arguments about who may change what answer themselves.

Artifact	Example	Description
Product Backlog	`backlog = [user_story_1, epic_2]` `product_owner.order(backlog)`	• Emergent, ordered list of what is needed to improve the product • the single source of work undertaken by the Scrum Team • ordered by the Product Owner, who stays accountable even when the work is delegated • sized by the Developers who will do the work, and refined continuously as understanding grows.

The rest of this section is part of the full cheat sheet

Table 4: Artifact Commitments (2020 Scrum Guide Addition)

Every Scrum artifact carries exactly one commitment that gives it focus and something to measure progress against: the Product Backlog has the Product Goal, the Sprint Backlog has the Sprint Goal, and the Increment has the Definition of Done. Each answers a different question, namely where the product is heading, why this Sprint is worth doing, and what counts as finished. Mixing up which commitment belongs to which artifact is the most common slip here, and it costs the artifact the focus its commitment exists to give it.

Commitment	Example	Description
Product Goal	`product_goal = "Self-service refunds for every customer"` `backlog.emerges_to_fulfill(product_goal)`	• Describes a future state of the product the team can plan against; commitment for the Product Backlog • the long-term objective for the Scrum Team, spanning many Sprints; the rest of the Product Backlog emerges to define what will fulfill it • the team must fulfill or abandon one Product Goal before taking on the next.

The rest of this section is part of the full cheat sheet

Table 1: Core Scrum Roles (Accountabilities)

Role	Example	Description
Product Owner	`product_owner.maximize_value()` `product_owner.manage_backlog()`	• Accountable for maximizing product value resulting from the Scrum Team's work • accountable for effective Product Backlog management: develops the Product Goal, creates and orders items, keeps the backlog transparent • one person, not a committee; may delegate the work but remains accountable, and the organization must respect their decisions.
Scrum Master	`scrum_master.improve_effectiveness()` `scrum_master.coach_team()`	• Accountable for the Scrum Team's effectiveness and for establishing Scrum as defined in the Guide • true leader who serves: coaches self-management, causes the removal of impediments, keeps events productive and within the timebox • serves the Product Owner and the organization too; not a project manager and assigns no work.
Developers	`developers.create_increment()` `developers.self_manage()`	• Anyone committed to creating any aspect of a usable Increment each Sprint, not just programmers ("developers" is used to simplify, not to exclude) • always accountable for the Sprint Backlog, instilling quality via the Definition of Done, and adapting the plan daily • self-manage who does what, and hold each other accountable as professionals.

Table 2: Scrum Events (Ceremonies)

Event	Example	Description
Sprint	`sprint(duration="2 weeks")` `sprint.timebox = "one month or less"`	• Fixed-length container for all other Scrum events (one month or less) • a new Sprint starts immediately after the previous one ends • only the Product Owner may cancel a Sprint, and only if the Sprint Goal becomes obsolete.

Table 3: Scrum Artifacts

Artifact	Example	Description
Product Backlog	`backlog = [user_story_1, epic_2]` `product_owner.order(backlog)`	• Emergent, ordered list of what is needed to improve the product • the single source of work undertaken by the Scrum Team • ordered by the Product Owner, who stays accountable even when the work is delegated • sized by the Developers who will do the work, and refined continuously as understanding grows.

Table 4: Artifact Commitments (2020 Scrum Guide Addition)

Commitment	Example	Description
Product Goal	`product_goal = "Self-service refunds for every customer"` `backlog.emerges_to_fulfill(product_goal)`	• Describes a future state of the product the team can plan against; commitment for the Product Backlog • the long-term objective for the Scrum Team, spanning many Sprints; the rest of the Product Backlog emerges to define what will fulfill it • the team must fulfill or abandon one Product Goal before taking on the next.