Scrum on One Page (Expansion of the SGEP)

Collected Resources for Scrum Guide Expansion Pack
This document is a collection of independent works. Each section retains its original license or copyright status, as indicated. Please refer to each section for specific usage rights and requirements.

License: Creative Commons Attribution-ShareAlike 4.0 International ( CC BY-SA 4.0 ).
© 2025 Ralph Jocham, John Coleman, and Jeff Sutherland.
Disclaimer: No warranties are given. Use at your own risk.
This section is offered under the Attribution-ShareAlike 4.0 International license of Creative Commons.
By using this Scrum Guide Expansion Pack, you agree to the terms of the CC BY-SA 4.0 license.

Scrum is described in the 2020 Scrum Guide (40). Scrum is a lightweight framework for addressing complex (30-35) work, particularly in Product discovery, development, delivery, and value realization. Scrum is based on empirical process control (decisions informed by evidence) and lean thinking (reducing waste and focusing on the flow of value) (63). Scrum is purposefully incomplete, guiding interactions rather than prescribing detailed recipes.

Why Use Scrum?
Scrum enables Scrum Teams to identify, represent, or measure emergence (71), embrace uncertainty, respond to change, deliver and validate value frequently, and continuously improve. Scrum fosters collaboration, accountability, and evidence-informed decision-making, fostering the best possible outcomes in a rapidly changing environment. Self-managing Scrum Teams, organized around value, are crucial for creative problem-solving and opportunity capture; non-self-managing Scrum Teams hinder the ability to deal with complexity (30-35). Self-managing Scrum Teams are not to be confused with individual self-management.

Elements of Scrum

1. Scrum Theory: Built on three pillars:

• Transparency – Making work and value visible for Inspection.
• Inspection – Regularly assessing progress and outcomes for Adaptation.
• Adaptation – Adjusting plans informed by insights and feedback.

2. Scrum Values:

• Focus, Openness, Courage, Commitment, and Respect enable effective teamwork; they support trust.

3. Roles / Accountabilities:

• Scrum Team – A small, self-managing, cross-functional, cognitively diverse team consisting of:
  • Product Owner – Maximizes long-term value, engages Stakeholders, and manages the Product Backlog.
  • Scrum Master – Guides the Scrum adoption, removes impediments, and fosters continuous improvement.
  • Product Developers – Deliver Increments every Sprint through their cross-functional capabilities.
• Stakeholder - an entity, individual, or group interested in, affected by, or impacting inputs, activities, and outcomes with a direct or indirect interest inside or outside the organization, its Products, or services.
  • Supporter, a Stakeholder type – Fosters the climate and environment and participates as requested.
  • AI – As a tool or also a possible Product Developer, but not to be entirely trusted yet.

4. Scrum Events & Activities

• Scrum operates in Sprints (iterations of determinate length up to four weeks) with four timeboxed events:
• Sprint Planning – Define the Sprint Goal and plan the work.
• Daily Scrum – Product Developers align daily on progress toward the Sprint Goal or Product Goal.
• Sprint Review – Inspect the Increment, value, and marketplace, and adapt the Product Backlog.
• Sprint Retrospective – Reflect and improve the Scrum Team.
• Refinement – Clarify upcoming or selected work, formally (as an optional event) or informally

5. Scrum Artifacts & Commitments

• Product & Definition of Outcome Done – Product and valuable outcomes that provide evidence of realized benefits.
• Increment & Definition of Output Done – A potentially valuable, releasable candidate update for the Product.
• Product Backlog & Product Goal – the ordered (sequenced) list of work to achieve a medium-term, more strategic objective.
• Sprint Backlog & Sprint Goal – Selected Product Backlog Items and a plan for the Sprint, short-term objective.

Attribution for the Scrum Guide Expansion Pack Collection

This collection was written and compiled by Ralph Jocham, John Coleman, and Jeff Sutherland. Each section is individually attributed above and retains its original license. The collection as a whole is for informational purposes; please respect the license terms of each section.