Skip to main content

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

How the Sprint Retrospective supports Inspection - Back to the foundations of the Scrum framework (15)

August 26, 2021

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

During each of the Scrum Events, and throughout the Sprint itself, the Scrum Team and the stakeholders inspect based on a common understanding. Without this transparency, one cannot perform a valuable inspection.

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


Let’s take the Sprint Retrospective.

Inspect what?

The Sprint itself in its entirety.

  • Any specific goals for individuals showing deviations?
  • Any interactions that did not work out as expected?
  • Any process variations outside expected boundaries?
  • What about the Definition of Done? Did the team achieve it? What work remains undone?
  • How about the agreed improvements from the last Sprint Retrospective; were these implemented with the expected results?

Sure a team can use a qualitative feeling of how these items performed. If data is available though, make use of it. This again shows the importance of goal and target setting. If no clear targets are agreed, how can a team do a useful Sprint Retrospective?

Inspection by whom? 

  • By the entire Scrum Team: the Product Owner, the Developers, and the Scrum Master. They collaborated during the Sprint, now it is up to them to inspect themselves how effective they were.



"During the Sprint Retrospective, does your Scrum Team look for undesired variances with regards to individuals, interactions, processes, tools, and the Definition of Done? Do you?"


Prompt: With your entire team, have a conversation about the entire Sprint with regards to effectiveness of individuals, interactions, processes, tools and the Definition of Done.


I hope you find value in these short articles and if you are looking for some clarifications, or if this raises a number of questions, feel free to take contact at steven @ boostyourscrum . com

PS. Next week we'll look at Inspection during the Sprint.

Don't want to miss any of these? Have the professional Scrum foundations series weekly in your mailbox.

How the Sprint Retrospective supports Inspection

What did you think about this post?