How I came beware of the empirical process control model
At Procurios we are using Scrum over four years and I always participated in the Scrum Events, because it is just a part of Scrum. But since I followed the Professional Scrum Master Training I became aware of the empirical process control model, which Scrum is based on.
The three pillars
- Transparency
- Inspection
- Adaptation
Transparency
Be transparent about the things you want to talk about. Let's take the Retrospective as an example. Every member of the Scrum Team thinks of what went well and what could be improved. If everyone writes this on post-its, there is a wall filled with all post-its of the whole Scrum Team.
Inspection
Now it's time to see if there are big differences in the things you want to discuss. Maybe there are issues that concern each team member. If in a Retrospective all team members write a post-it with the same subject or issue, then that's a good sign to think about how to handle that issue.
Adaptation
This is the discussion of the most important issues and the process of thinking of solutions to solve these issues. In a Retrospective we define actions or experiments to try to solve issues.
Conclusion
I used the Retrospective as an example, because I think that's the most obvious Scrum Event which reflects this model. Now I'm aware of this model and I use this model consciously to determine what the purpose is of all the Scrum Events. And there are several other things you can apply this model to, such as the Daily Happiness (how happy is each team member), the absence board (when is a team member not in the office) and code reviews.