Skip to main content

Scrum Doesn’t Assign People—It Engages Them

October 23, 2025

How do you engage people to work together—not just to do tasks, but to care, contribute, and grow?

From the #Scrum Guide: “Scrum engages groups of people...”

Cambridge Dictionary defines *engage* as: “to interest someone in something and keep them thinking about it.”

That’s a far cry from just assigning tickets.

Scrum creates engagement by design:
- Purpose through Product & Sprint Goals.
- Mastery through continuous inspection, adaptation, and skill growth.
- Autonomy by empowering self-managing teams to decide how to work.

When these three are present, people don’t just show up—they bring energy, ideas, and ownership.

But without them? Teams disengage. Goals become checklists. Reviews become formalities. People start asking: “Why are we even doing this?”

I’ve felt both sides. What today is almost a minimum for organisations - to digitally exchange invoices and have them straight from the sellers in the buyers system - was a big challenge in the earlier days of my career. I believed in it. We learned fast, solved tough problems, and had the freedom to shape the product. That mix of purpose, mastery, and autonomy made me engaged.

Scrum at its best engages people the same way.

So, reflection time:
- When were you most engaged in your work?
- Do your teams have that same chance today?
- And if not—what’s blocking it?
 

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!

 


What did you think about this post?

Comments (2)


01:24 pm October 27, 2025

What about the idea, of spliting the Scrum Master into 2 Roles,  Backlog Scrum Master and Sprint Scrum Master? (I know it does not make sense, but would like to know an unbias  opinion :))

 

 


05:29 pm October 29, 2025

Hello Ruben,
I would not have the faintest idea what these two different roles would be accountable for. What would their purpose be?
The team together is accountable to deliver value each and every Sprint. Give this to a specific person and we reduce their ownership and their self-management.
The Sprint Backlog is in the hands of the Developers. Give this to a specific person and again we reduce their ownership.
The Product Backlog is owned by the Product Owner. Give this to another person and the Product Owner looses his preferred way to make his vision and decisions transparant.
So... I really don't see it...