Skip to main content

Due to the Russian invasion of Ukraine, we have paused all purchases and training in and from Russia.

How can the Scrum Master support Inspection? Back to the foundations of the Scrum framework (22)

October 14, 2021

Remember that Scrum is founded on empirical process control, and that inspection is one of the three pillars.

Each of the Scrum accountabilities participates in one or more inspections. If you feel that there are undesired variances for any aspect of your initiative, think about who could best initiate an inspection.


Inspection is about detecting undesirable variances in progressing towards agreed goals.


So how about the Scrum Master in the Scrum Team.

As part of the Scrum Team, the Scrum Master is collaborating with the team in all aspects of inspection. Yet his/her focus is not the same. The Scrum Master is looking for opportunities to improve the professional use of the Scrum framework in order to raise the effectiveness of the Scrum Team. And this can come from within the team or outside the team.

The Scrum Master can ask a lot of questions for this. Some examples include

  • Is the Scrum Team delivering a Done Increment each Sprint providing value to the market?

  • Does the Scrum Team have all skills needed?

  • Does it have enough mandate to decide how to do their work?

  • Does the Scrum Team live the Scrum Values?

  • Does the team apply feedback cycles as short as needed? On the product, tools, process, collaborations, etc. And do they involve the right stakeholders for this?

  • Do they act on potential improvements?

Every Scrum Event can be used for this. Every day brings opportunities to watch out for possible undesired variances in the professional use of Scrum.


Does the Scrum Master actively take part in detecting undesired variances in the professional use of the Scrum framework? In detecting undesired variances in the effectiveness of the Scrum Team?


Together with the Scrum Team

  1. Clarify the different goals: Product, Sprint, Definition of Done, effectiveness.
  2. Inspect the current status for undesired variances.
  3. Evaluate what improvements can be made to close these gaps.

We hope you will find value in these short messages and if you are looking for more clarifications, feel free to take contact.


Here we are, 11 short reads further about how each of the Scrum elements supports Inspection, the second pillar of empiricism.
Remember, only bringing transparency is not enough. Adding only Inspection is still not enough.
At this point we have a shared understanding about the situation and about deviations we don't want.
Without Adaptation, the third pillar of empiricism, all is waste.
So next week we'll start looking at how the 11 elements support Adaptation, the third pillar of empiricism.

💡After this second part in the series - Transparency was the first, Inspection the second - I am curious to hear from you what your most important insight is so far, what you did or plan to do with it, and how we can help you further in your agile adventures.

⏩Feel free to forward these messages to anyone whom you feel might also benefit from. 

So: let me know what you did with it, and according to you who would also benefit from these.


If you want to take a deeper dive into the core concepts we are covering in this blog series, then surely check out our Professional Scrum Mastery workshop.
Don't want to miss any of these blog posts? Have the professional Scrum foundations series weekly in your mailbox.

How does the Scrum Master support Inspection?

What did you think about this post?