Scrum is not for loners. It’s for groups of people.
From the Scrum Guide: “Scrum engages groups of people…”
From Cambridge Dictionary:
- People: “men, women, and children,” and “used to refer to everyone, or informally to the group that you are speaking to.”
- Group of: “a number of people or things that are together or considered as a unit”.
So why “groups of people”? Not one group, but groups.
Because Scrum is never about one hero Developer, one visionary Product Owner, or one charismatic Scrum Master. Scrum’s strength lies in what happens when groups of people come together—bringing different skills, perspectives, and experiences—to tackle complex problems.
Which groups of people are we talking about?
- The Scrum Team itself: Developers, Product Owner, Scrum Master.
- Stakeholders: users, customers, sponsors.
- Leaders and managers: shaping the environment where Scrum teams can thrive.
- Sometimes even groups outside the organization: regulators, partners, suppliers.
Why groups matter:
- Collective intelligence beats individual brilliance.
- Inspecting and adapting is richer when diverse perspectives are included.
- Goals are achieved through collaboration, not isolated efforts stitched together.
But beware…
A group of people ≠ teamwork.
I’ve seen plenty of so-called “groups” stuck in dysfunction:
- Silos inside a Scrum Team (“backend vs frontend”).
- Stakeholders kept at arm’s length instead of engaged.
- Leadership treating Scrum as “the team’s thing” instead of changing how they themselves work.
How Scrum engages groups of people:
- Events create recurring opportunities for collaboration.
- Artifacts provide transparency so everyone sees the same truth.
- Values shape how people behave in groups—respect, openness, courage, focus, commitment.
- Shared goals (Product Goal, Sprint Goal, Definition of Done) align groups around purpose.
Scrum works not because it optimizes individuals, but because it engages groups of people to think, decide, and act together.
Reflection:
- Which groups of people are truly engaged in your Scrum implementation?
- Which groups are left on the sidelines?
I’d love to hear your thoughts in the comments below!
I hope you find value in these short articles and if you are looking for more clarifications, feel free to make contact.
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!
