Remember that Scrum is founded on empirical process control, and that adaptation is the third pillar, following transparency and inspection.
During each of the Scrum Events, and throughout the Sprint itself, the Scrum Team and the stakeholders adapt what they deem necessary in order to minimise any deviations to acceptable limits which they have identified during inspection.
Adaptation is making adjustments in order to minimise any deviations to acceptable limits concerning agreed goals.
Let’s have a look at the Daily Scrum.
Based on insight in progress towards the Sprint Goal, the team might identify it is not make the progress it was expecting. A conversation to minimise this deviation takes place and the outcome of this is shown in the Sprint Backlog.
The Sprint Backlog is adapted.
Work is indicated as in progress, or done. Work no longer deemed necessary is removed. Newly identified work that is needed to achieve the Sprint Goal is added.
Correct, the Developers might change and add work. This is very logical: while building the team learns and discovers and as such have to adapt their plan to achieve the agreed Sprint Goal.
But hey, this is more work!? Maybe. Does it matter though? The team has agreed to work towards the Sprint Goal – the commitment for the Sprint Backlog. The selected Product Backlog Items and the plan discussed during Sprint Planning was their view at that given moment. The team learns. And so need to adapt.
Sprint Goal = commitment for the Sprint Backlog
As the Sprint Backlog is what we adapt during the Daily Scrum, and given the Sprint Backlog is managed by the Developers, only the Developers need to attend the Daily Scrum. All Developers.
During the Daily Scrum, the Developers update the Sprint Backlog to show the remaining work (except for the Sprint Goal) in order to achieve the Sprint Goal.
Together with your Scrum Team, evaluate your Daily Scrum:
Do you discuss progress towards the Sprint Goal?
Does the Sprint Backlog show the remaining work to achieve the Sprint Goal in a Done Increment?
Are the selected Product Backlog Items, and the actionable plan to achieve the Sprint Goal updated as needed?
I hope you find value in these short posts and if you are looking for more clarifications, feel free to take contact.
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. We have some scheduled in the coming period.
Don’t want to miss any of these blog posts? Have the professional Scrum foundations series weekly in your mailbox.