Three Pillars of Scrum
Fleetingthree pillars of scrum
Those are also the three pillars of continuous improvement.
- you need transparency to ensure things can be seen,
- you need inspection to ensure you actually will look at those things,
- you need adaptation to ensure that whatever you saw will change if need be.
transparency
The scrum artifacts are made available to everyone to see.
These decisions are visible in the content and ordering of the Product Backlog, and through the inspectable Increment at the Sprint Review
highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint in order to achieve the Sprint Goal
More likely made possible thanks to the values of openness and respect.
The emergent process and work must be visible to those performing the work as well as those receiving the work
important decisions are based on the perceived state of its three formal artifacts.
Transparency enables inspection. Inspection without transparency is misleading and wasteful
transparency can also be applied toward oneself, yet in that case I think we’d rather talk about intellectual honesty.
inspection
The scrum artifacts are made so that one can inspect the progress towards their respective goals.
The daily scrum gives a dedicated time to inspect the progress towards the sprint goal.
To do so, the work made by the team is split in inspectable increments that can be reviewed at the sprint review.
These decisions are visible in the content and ordering of the Product Backlog, and through the inspectable Increment at the Sprint Review
More likely made possible thanks to the values of commitment and focus.
Failure to operate any events as prescribed results in lost opportunities to inspect and adapt.
The Scrum artifacts and the progress toward agreed goals must be inspected frequently and diligently to detect potentially undesirable variances or problems
To help with inspection, Scrum provides cadence in the form of its five
Inspection enables adaptation. Inspection without adaptation is considered pointless
adaptation
After inspecting the scrum artifacts, the team has to find the courage to adapt when it realizes that it is needed, relying on the openness and respect.
The daily scrum is a place to adapt when the sprint goal may be jeopardized, yet it is stressed that the team should not wait until the daily to adapt.
The team can adapt only if it has a clear idea of what it has committed to and if it focus on either the sprint goal or the product goal.
Failure to operate any events as prescribed results in lost opportunities to inspect and adapt.
Notes linking here
- only one product owner
- Agile & Scrum Don’t Work | Allen Holub In The Engineering Room
- being committed towards the sprint goal does not necessarily mean always working towards it
- commitment (scrum)
- courage (scrum)
- daily scrum
- focus (scrum)
- Footnotes
- gtd and scrum
- intellectually honest
- method is a tool, not a toolbox
- misconceptions about scrum
- misconceptions about scrum became the most sensible hypothesis
- métaphore salade vs pâtes
- openness (scrum)
- product goal (scrum)
- respect (scrum)
- scrum
- scrum artifacts
- scrum events
- scrum is not agile because formally defined?
- scrum team
- sprint
- sprint backlog
- sprint goal
- task force
- what if the scrum team fulfills the sprint goal before the end of the sprint?