Scrum as facilitator of daily scrum

If a team is in early stages of Scrum the Scrum Master should teach the Development Team the purpose of the Daily Scrum. The purpose is doing inspect and adapt towards the Sprint Goal and not mechanically answering questions.

What do you think, if the Scrum Master asks the questions in Daily Scrum to whom will the developer address the answer? Who should be most interested in the answer?

Imagine you are the Scrum Master of a new team. How would you coach the team to conduct a Daily Scrum, and what outputs would you suggest are valuable? Do you think that if the Development Team restricted themselves to answering standard questions, that would be enough to "synchronize activities and create a plan for the next 24 hours" as the Guide states?

Internalize "why" there is a Daily Scum.  Rather than ask the team to answer the three questions, wouldn't it be more beneficial for the Scrum Master to teach the team why those questions can be helpful in understanding how they are progressing towards the sprint goals, and why those questions can help the team re-plan for the day to move closer towards the sprint goal?  And teach them to stay within the 15 minute timebox, perhaps?  Maybe he can also use the retrospective to remind the team about Scrum values such as Focus, if the team is focused on distractions during the Daily Scrum.

All the best,

Chris 

Just as a little technique... I often find the situation for a Scrum Master is not starting with a brand new team who have never had a Daily Scrum before.  It's usually an existing team and they have a Daily Scrum but it's really a status update meeting. 

Rather than trying to coach them to fix their Daily Scrum, I let them have their status update meeting.  I schedule another meeting and call it Inspect and Adapt meeting or something similar (with the objective of the meeting to match a real Daily Scrum), and that for them is brand new.  Then they can get good at that from the start.  After a while, I inform them that that's what a Daily Scrum actually is.  We then just change the names around.  Eventually, they realise the status update meeting is redundant.

Just as a side note: A fun way of helping the team to create better recurring meetings (in general, not only daily) is the altitude game:



http://gamestorming.com/altitude/

It's really easy to understand and using those paper darts is a fun way of letting someone know that they're getting of track. As everybody has committed to and therefore knows what "off track" means, but forgets sometimes, the smirking and laughing usually already starts as soon as someone even just starts to look at one of the paper darts, as just then they realize in an amusing way that they went off track without realizing :-)