The three core pillars of Scrum, an empirical process framework, are transparency, inspection, and adaptation.
Understanding the Three Pillars of Scrum
Scrum is built on empiricism, meaning that knowledge comes from experience and making decisions based on what is observed. To support this empirical approach, Scrum is founded on three essential pillars, as highlighted in the reference: transparency, inspection, and adaptation. These pillars work together to provide the structure and control needed for complex product development.
Let's explore each pillar in more detail:
Transparency
Transparency ensures that the process and the work are visible to both those performing the work and those receiving the work. In Scrum, this means:
- Visibility: Significant aspects of the process must be visible to those responsible for the outcome.
- Common Language: A common language should be shared so everyone understands what is being communicated.
- Shared Understanding: Everyone involved should have a clear understanding of the definition of "Done" for increment and artifacts.
Practical examples in Scrum:
- Product Backlog: Transparent list of ordered items (user stories, features, bugs) representing work to be done.
- Sprint Backlog: Visible plan for the Sprint, detailing the work the Development Team plans to accomplish to achieve the Sprint Goal.
- Task Boards: Visual representation of the work in progress during a Sprint (e.g., using tools like Jira, Trello, or physical boards).
- Definition of Done: A clear, shared understanding of what it means for a Product Backlog Item to be completed and integrated into the Increment.
Inspection
Inspection involves checking Scrum artifacts and progress towards a Sprint Goal to detect undesirable variances.
- Regular Checks: Key Scrum artifacts and the progress towards agreed-upon goals must be inspected frequently.
- Timely Inspection: Inspection should not be so frequent that it gets in the way of the work, but regular enough to detect problems promptly.
- Skilled Inspectors: Inspectors must be skilled at their work to avoid misinterpretations.
Examples of inspection activities:
- Daily Scrum: The Development Team inspects progress towards the Sprint Goal and adapts the Sprint Backlog as needed.
- Sprint Review: The Scrum Team and stakeholders inspect the outcome of the Sprint (the Increment) and adapt the Product Backlog.
- Sprint Retrospective: The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, and tools, and identifies improvements.
Adaptation
Adaptation is about adjusting the process or the materials being processed as soon as an inspection reveals that one or more aspects are deviating outside acceptable limits or if the resulting product will be unacceptable.
- Timely Adjustment: When a deviation is detected through inspection, the relevant aspects of the process or product should be adjusted as soon as possible.
- Empirical Control: This ability to adapt is the foundation of empirical process control in Scrum.
- Self-Managing Teams: Scrum Teams are empowered to adapt their processes and work as needed.
Adaptation opportunities in Scrum:
- Daily Scrum: The Development Team adapts the Sprint Backlog and daily plan based on the inspection of progress.
- Sprint Planning: The Scrum Team adapts the plan for the upcoming Sprint based on the Product Backlog and feedback.
- Sprint Review: The Product Backlog is adapted based on feedback on the Increment and discussions with stakeholders.
- Sprint Retrospective: The Scrum Team adapts its processes to implement improvements identified during the inspection.
Summary Table
| Pillar | Description | Importance in Scrum |
|---|---|---|
| Transparency | Making the process and work visible and understandable. | Ensures a shared reality and common understanding. |
| Inspection | Regularly checking Scrum artifacts and progress towards goals. | Detects deviations and potential problems early. |
| Adaptation | Adjusting processes or plans based on the findings from inspection. | Allows the team to respond to change and correct course. |
These three pillars form the bedrock of the Scrum framework, enabling teams to manage complexity and deliver value in an iterative and incremental manner.
