Inspection and the Increment - Back to the foundations of the Scrum framework (19)
Scrum is founded on empirical process control, and inspection is one of the three pillars.
Each of the Scrum Artifacts is inspected in one or more Scrum Events to detect undesired variances. If you feel something isn’t running as expected, have a good look with your team at your Artifacts what could be going on.
Inspection is about detecting undesirable variances in progressing towards agreed goals.
Let’s take the Increment.
The Increment is inspected at least during the Sprint Review in order to detect variances in the current state of the Product compared to customer and market expectations.
Do we have the expected capabilities? How does the market respond to the product? How are we progressing towards the Product Goal?
It is typically inspected by the entire Scrum Team in collaboration with stakeholders.
Other questions that can be asked are
- What is the current value the Increment provides? How happy are users? And is this improving or declining?
- What capabilities are available yet do not seem to be used, and why is this? What capabilities are no longer valuable to users?
- What additional value can be created? In our current markets, or in other markets?
Do you inspect your Increment to detect variances in the current state of the product compared to expectations of the market?
Prompt: With your entire team evaluate your Increment. What might be beneficial to your users, clients, and market? What might be too much in the Increment that hardly provides value?
We hope you will find value in these short messages and if you are looking for more clarifications, feel free to take contact.
PS. Next week we'll look at the Product Owner and Inspection.
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? Have the professional Scrum foundations series weekly in your mailbox.