This idea came up when time ago I attended for the first time one team Daily Standup, one team that I would start working with them as Scrum Master.
In order to give you some context, this is the situation: The team meets 2 times per week in a meeting of 30 minutes.
So the Daily Standup started and each of them was giving an update about what was going on, what each of them worked on, what they would be doing including the Product Owner.
The team finished talking about general topics about the projects, updates, things to know, etc.. which is totally fine if the team knows that the goal of the meeting is this one, but since the meeting is called Daily Standup then for me it felt weird.
To be honest, I felt the meeting much more useful for the Product Owner than for the Development team, but this is just what I felt.
While they were doing it I thought in an easy assessment to help me to see the health of the Daily Standup, and also to visualize team’s opinion about it.
So as you can see in the image I basically presented a score from 1 to 5, where:
1 is – Everything it was said I already knew and was not sprint objective related, it was general project stuff, so I got information which was not relevant for a Daily Standup.
3 is – Most of the things I already knew, but there were certain comments from other developers that made me be aware of the progress of the sprint and potential problems or bottlenecks I could have.
5 is – It was short and concise and we were able to share relevant information for the whole team, so we will potentially avoid problems/bottlenecks thanks to what was shared.
And to finish… I’m not sure if it’s relevant but, if you sum all the scores and divide them by the number of people you will get the average, which in this example is below 3.
As a good read, I would like to recommend this post from Jason Yip where writes about Patterns for Daily Standup Meetings
