- Production: scrumexpansion.org - Start reading now!
- Preview: agreeable-island-0c966e810-preview.centralus.6.azurestaticapps.net - Test latest changes before production
The Scrum Guide Expansion Pack was created because the world in which we build products has changed—and continues to change rapidly.
Scrum, as defined in the 2020 Scrum Guide, is still solid and useful. But many practitioners, leaders, and teams found themselves asking deeper questions: – How do we stay focused on real outcomes, not just shipping features? – How do we work when AI becomes part of the team? – How do we apply Scrum in fast-moving environments without losing its simplicity?
The Expansion Pack is a response to those questions. It’s not a replacement of the Scrum Guide. It’s an optional companion—a way to support people who already use Scrum but feel they need more guidance to navigate today’s realities.
The motivation wasn’t to add more rules or make Scrum heavier. Quite the opposite: it was to clarify the spirit of Scrum, especially around product thinking, emergence, and strategic focus. Scrum has always been about enabling teams to learn fast, adapt, and deliver value. The Expansion Pack helps modern teams keep that spirit alive—especially in environments shaped by uncertainty, acceleration, and new technology.
Changes to content can often be contentious, culturally sensitive, and difficult to manage effectively. To navigate these complexities, we encourage the following collaborative workflow for contributors to the Scrum Guide Expansion Pack:
- Create a Discussion – Engage peers in a conversation about the proposed change, aiming for consensus. Include all perspectives that could provide valuable insights.
- Create an Issue – Once consensus is reached, [create an issue] clearly documenting the change and attributing all participants.
- Submit a Pull Request – Follow standard GitHub procedures: fork the repository, implement the change, and submit a Pull Request.
- Review the Pull Request – The original creators (Jeff, John, Ralph) or their delegates will review your submission, and may approve, comment, or reject the proposed change.
The Scrum community thrives on shared knowledge and collaborative improvement.
- Share practical insights - Start a new discussion.
- Address implementation challenges - Help others overcome obstacles.
- Propose refinements - Suggest improvements.
- Document lessons learned - Share your discoveries.
Making Scrum knowledge accessible globally is essential.
- Expand language support
- Refine translations
- Review content
Open a discussion to connect with the community.
- Production: scrumexpansion.org
- Preview: agreeable-island-0c966e810-preview.centralus.6.azurestaticapps.net
- Download PDF: Available languages
- Default English:
site/content/guide/_index.md - Language versions:
site/content/guide/_index.{lang}.md
Contributions include:
- Enhance content
- Clarify concepts
- Suggest new sections
- Review and edit
- Improve platform functionality
- Optimize performance
- Maintain infrastructure
Guidance:
Developed by Scrum and agile product development experts:
- Ralph Jocham
- John Coleman
- Jeff Sutherland
Built upon the official 2020 Scrum Guide by Ken Schwaber and Jeff Sutherland.
Freely available under an open license:
- Read and distribute
- Use for training and education
- Translate
- Adapt and build upon
Attribution is requested.
See LICENSE for complete terms.
- Read the expansion - Production site
- Test latest changes - Preview site
- Engage with the community
- Support translations
- Review contribution guidelines
Together, we're advancing Scrum practice for modern product development challenges.