Skip to main content

Formal: Why Scrum needs "official" spaces to Inspect and Adapt

December 11, 2025

A while ago, someone told me: “Our team stopped using the Scrum Events. We can’t wait that long to get the benefits!”

 

I loved it!

 

A team too eager to inspect and adapt to wait for a calendar invite? That’s a great problem to have.

 

But here’s the thing: Scrum says these are *formal* opportunities to inspect and adapt.

Why formal? Why not just “meet when it feels right”?

 

Let’s unpack that.

From the Cambridge Dictionary:

- Formal = “Public or official.”

- Public = “Relating to or involving people in general, rather than being limited to a particular group.”

- Official = “Relating to a position of responsibility.”

 

Put simply: formal events ensure the right people are included and the right accountabilities are fulfilled.

 

When Scrum Teams skip the formal events - or turn them into hallway chats or ad hoc calls - things might start to slip:

- Not everyone gets the same information.

- Decisions get made in the shadows.

- Feedback loops shrink.

- Accountability blurs.

 

Formal doesn’t mean bureaucratic - it means visible and shared.

Scrum’s events are “public” in the sense that everyone who needs to inspect and adapt can be there. They’re “official” because they anchor the team’s responsibility to improve.

 

And yes, informal interactions are vital too!

Grab a coffee, whiteboard something, debate, laugh, argue.

But bring the insights back to the formal events so that everyone - who needs to - learns from them. That’s how informal creativity feeds formal improvement.

 

Because if inspection and adaptation happen only in private corners, Scrum’s transparency collapses.

 

So, next time someone says “we don’t need all these events,” ask:

- Who’s missing out on the conversation?

- What decisions are being made off the radar?

- Are we adapting as a team—or just a few individuals?

 

Formal doesn’t mean boring. It means shared.

What you do with that space—that’s up to your facilitation skills.

 

 

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 (0)

Be the first to comment!