Well, first, how often do we have one?
‘Obvious, toolshed, daily!!’ Well, apparently not so obvious to all. Some people think we need one twice a week.
Let’s go back to the purpose.
The purpose is to enable the team to make micro-adjustments in any dimension to land the plane more successfully.
What does ‘land the plane’ mean? Well, to deliver the team’s commitment (or promise) made in Sprint Planning to deliver 8 stories that sprint. (Well, it might have been more than 8 stories, depending on their size and the team velocity.)
What does ‘more successfully’ mean? Well, all 8 stories first. Higher quality, less technical debt. And maybe another story, or at least another story started. And given the usual ‘stuff happens’ around here (as it always does).
So, who is making the micro-adjustments? Well, anyone on the team. Probably really everyone on the team, both consciously and sub-consciously.
What a Daily Scrum should not be
Another stupid wasteful meeting.
A status meeting for the ScrumMaster.
A time to brag about all the wonderful things I did yesterday.
An endless discussion of, and attempt to fix, several impediments (with all team members present).
A time to hide the truth, because God knows what those stupid people might do with it.
Well, we work each day, so the situation is always changing.
And because a serious impediment could arise any day. And often we don’t recognize the impediment until we get together and see the impact on the team.
There is a saying: “Take care of the small problems and the big problems will take care of themselves.” Maybe not always true, but this might be one hypothesis behind the Daily Scrum. If we fix the small problems when they are small, they do not grow to become big problems.
Related to this is that the bad news does not get better with age. So, identify it quickly and hopefully fix is quickly, before the bad news becomes worse.
What do you mean ‘micro-adjustments’?
Well, anything really, that can help us be more successful.
Working together more or differently.
Getting new information.
Fighting over a problem.
Asking for help.
Fixing an impediment.
Getting clarification of a mini-feature.
Different automated testing.