Skip to main content

Scrum Guide Explored: What we’ve learned so far (and what’s next)

July 31, 2025

What a journey it’s been so far…

48 posts in (see below), and we’ve only just completed the first two sections of the Scrum Guide: Purpose of the Scrum Guide and Scrum Definition. There’s so much more ahead—and so much richness already uncovered.

The Scrum Guide is often underestimated. Don’t. 
Every word is deliberate. 
Every sentence has weight. 

Read it. 
Re-read it. 

Learn. Reflect. Repeat.

@Dave Smith shared three powerful questions with me to explore any sentence in the Guide with your team. 
Use them often. Use them well:

- “What does this mean to you?”
- “What do you think this does NOT mean?”
- “What would happen if that had been omitted from the Scrum Guide?”

Next up: Scrum Theory—because there’s no practice without theory, and no theory worth much without practice.

Stay tuned, keep questioning, and if you’ve got a Scrum puzzle—send it my way. Always happy to help.

 

Don't want to miss any of these blog posts? Have the “The Scrum Guide Explored” series weekly in your mailbox.

Wishing you an inspiring read and a wonderful journey.

Scrum on!

 



Scrum on!

  1. The Scrum Guide Explored - Scrum is a Game!


Purpose of the Scrum Guide 

  1. The Definition of Scrum
  2. Scrum's Essential Elements
  3. It's a Guide!
  4. Covering Up Problems...
  5. Breaking the Myth: Developers Aren’t Just Software Engineers
  6. How Is Scrum Simplifying or Adding Complexity to Your Life?
  7. Why Scrum Doesn’t Provide Specific Solutions—And Why That’s a Good Thing!


Scrum Definition

  1. What Does It Mean That Scrum Is a Framework? Is it Even Important...?
  2. Scrum: The Power of Doing Less
  3. Is Scrum Helping You? Discover How to Uncover Its Real Value
  4. Who Can Really Use Scrum? Hint: It’s Not Just Teams
  5. Defining Value in Scrum: What Does It Mean for You?
  6. Adaptive Solutions: The Heart of Scrum’s Power
  7. Scrum and Complex Problems: Why Planning Isn’t Enough
  8. The Scrum Master’s Role: Fostering Growth and Adaptation
  9. Fostering the Right Environment: The Scrum Master’s True Role
  10. Ordering Work in Scrum: it's about Clarity, Alignment and Collaboration
  11. Ordering vs. Prioritizing: What a Product Owner Really Does in Scrum
  12. The "Backlog" in Scrum: Beyond Features and Long Lists
  13. How Scrum Teams Select Work: Collaboration Toward Value
  14. Scrum Increments: Building Value, One Step at a Time
  15. Valuable Increments: Delivering What Truly Matters to Users
  16. Useful vs. Usable: What Makes an Increment Truly Valuable?
  17. Is Your Increment Truly Inspectable? Why it Matters More Than You Think...
  18. Scrum Adjustments: The Difference Between Learning and Stagnation.
  19. Are You Inspecting to Adapt or Just Showcasing?
  20. Stakeholders in Scrum: Who They Really Are (And Who You Might Be Missing)
  21. Why ‘Repeat’ is the Most Powerful Word in Scrum
  22. Scrum Is Simple… So Why Is It So Hard?
  23. Scrum Not Working? Try It As Is Before You Modify It
  24. Scrum Not Helping? Here’s How to Find Out Why.
  25. Scrum Still Not Working? Start with the Philosophy
  26. Scrum Feels Broken? Maybe You Missed the Theory...
  27. Scrum Not Delivering? Check the Structure. Minimal by Design, Powerful by Purpose.
  28. Scrum isn’t the Goal—Your Goals are
  29. Why the Scrum Guide is Purposefully Incomplete, and why that’s a good thing!
  30. Scrum Only Defines What’s Really Required. Aren’t You Adding Too Much?
  31. Scrum Isn’t Complete Without This One Ingredient: Collective Intelligence
  32. Scrum works—If you let people think (Collective Intelligence part II)
  33. Scrum’s Game Rules: Few, Clear, and Powerful
  34. To Guide, Not to Control: Scrum’s Take on the Hard Stuff
  35. The Secret to Better Scrum? Look at the Relationships
  36. Which techniques belong in your Scrum team? Here's the real answer.
  37. Scrum Wraps Around What You Already Do—But Not to Keep It Warm
  38. Rethinking legacy: when Scrum makes old practices obsolete
  39. Busy ≠ Effective: What Scrum should actually makes visible
  40. Scrum isn’t (just) for Delivering—it’s for Improving

 

To be continued...


What did you think about this post?