The three pillars for empirical processes, particularly emphasized in frameworks like Scrum, are:
- Transparency: All significant aspects of the process must be visible to those responsible for the outcome. This means providing a common understanding of the current state of the product, the work being done, and the process itself. Without transparency, it’s impossible to accurately inspect and adapt. Examples include shared backlogs, burn-down charts, and open communication.
- Inspection: Scrum artifacts and the progress towards a Sprint Goal must be frequently inspected to detect undesirable variances or problems. This doesn’t mean constant, micromanaging inspection, but rather timely and regular checks to identify issues or deviations from desired outcomes. This happens through events like daily scrums, sprint reviews, and sprint retrospectives.
- Adaptation: When inspection reveals that one or more aspects of the process deviate outside acceptable limits, adjustments must be made as soon as possible to minimize further deviation. This is about being able to respond to changes and learn from experience. If something isn’t working, the team should be empowered to change it. This happens through continuous improvement, process adjustments, and adapting plans based on new information.
These three pillars work together to create a continuous feedback loop, allowing teams to learn from their experiences and continuously improve their processes and products.