Gareth Lees-West

Those three questions

Something I've heard a lot from working in environments using the Scrum framework is an observation comment around the daily scrum/ standup. A general rule of thumb "it shouldn't feel like a status update"- that`s true, the intent is for the team to get together and discuss how they are working together to meet the sprint goal. They talk together on how they can help each other out. Why does it matter? Giving status updates creates a different dynamic and a less open conversation. Its directive and not as motivating, and furthermore its not conductive to a conversation and with that, collaboration.

With that in mind i was happy to see the three example questions removed from the most recent review of the scrum guide- I'm sure the practice will remain for many but I`ve always found them to be a bit unhelpful.

What did you do yesterday, today and any obstacles.

These questions respond easily with a status update. They are also individualistic.

Could try instead?

I`ve seen success with an open starter question- "what shall we do today to work towards the sprint goal?" Or just "what's the plan" to prompt conversation. Or flip it round entirely- and people start with "how can I help someone in the team work towards our goal".

Taking a moment to reflect on the language, tone, body language at a daily scrum can be really insightful in terms of team dynamic. Observing how people in the team communicate with one another, how they ask each other for help, who are they directing their conversation to? You can see a lot about a team from observing the daily scrum.

If you want to avoid this feeling like a status update I feel like a good start is avoiding those 3 questions entirely.