Daily stand-up meetings play an important role in the success of Scrum process-based projects. Most of us know this, and we know how they "should" be conducted. Yet, time and again, I see these meetings go astray. Here I hope to review the problems I commonly see, plus some solutions. I also hope to hear back from others about how they maintain the effectiveness of daily stand-ups.
It's often more important than we realize to guide and coach our teams about the usefulness of daily stand-ups. And it's worth it: Successful stand-ups can guide sprints throughout a Scrum-based project. Here are some useful tips:
Teach your team the basic ways of using time during the daily stand-up. Then be sure to follow them:
- The daily stand-up should be time-boxed.
- The ScrumMaster should facilitate regular daily meeting times. Don't change the time of this meeting if you can avoid it; Scrum requires discipline.
- Each member of the team should participate in this meeting. In some organizations, senior expert members sometimes hesitate to join. The ScrumMaster should coach them about the importance of their participation and the help they can provide to the team.
- Don't update the sprint backlog during this meeting.
- Team members should be active listeners so they know how the team as a whole is doing, and so they can help one another resolve impediments.
- Ensure that each team member remains present till the end of the meeting. Sometimes members want to leave after updating their own work plan, but the purpose of the stand-up is to understand how well we're doing to achieve sprint goals as a team.
Sprint status disclosure
In addition to respecting the basic processes outlined above, there are more subtle habits to maintain during daily stand-up meetings. One is the discussion of any impediments. It's easy for some members not to mention impediments — or to get bogged down in a long, large-group discussion of impediments that are relevant to just a few team members. Here are some ideas for avoiding these problems:
- Remember that the daily stand-up call is not a status meeting. The ScrumMaster needs to pay attention to make sure stand-ups don't tend in that direction. Guide team members to be open about their work progress and any hurdles, be they individual or team-wide.
- Use the stand-up to get any needed clarifications from the product owner (PO) regarding requirements (user stories) and sprint release issues.
- The ScrumMaster should list all the impediments faced by the team and help resolve them on a timely basis.
- Any technical discussion should be conducted after this meeting; only relevant members need to attend the technical discussions.
- The ScrumMaster will need to pay special attention to new Scrum teams, to help them follow the most effective stand-up processes.
Working with the product owner
Some specific tips make for best communication with the product owner during daily stand-up meetings. These are my suggestions:
- The team should think of daily stand-ups as a way to communicate effectively to the product owner, in addition to each other, about progress. No one wants any sudden surprises at the end of the sprint; these can be avoided if team members give regular and accurate updates during each daily stand-up.
- By the same token, the product owner should commit to attending this meeting daily so that he or she gets a better picture about team's commitment for the current sprint.
- The stand-up should go forward even if the product owner or the ScrumMaster can't join on a given day, whatever the reason.
Hurdles faced by new teams
Scrum isn't easy, as we all know if we've been able to dive deeply into it. It demands commitment from each team member, and new members aren't always used to this work culture. Below are some hurdles commonly faced by new Scrum teams:
- Lack of process knowledge: New Scrum teams need coaching and training about the Scrum process so they can effectively use the daily stand-up for its intended purpose. However obvious the process seems by now to the ScrumMaster, he or she needs to provide this coaching and process knowledge to new teams. In the same way, each team member must actively participate, to communicate how the team is doing and to fully learn the daily stand-up process.
- Hiding work details: It's important that every team member is transparent in his or her work and gives accurate updates. Members need to disclose any issues so they can be resolved on time, without impacting the entire team's commitment for the sprint. The ScrumMaster can help here, particularly in the realm of being transparent to the customer and encouraging the kind of customer involvement that can lead to a successful sprint. The daily stand-up isn't just about answering the same three questions every day; it's a perfect forum for discussing any gaps in the team's commitment and understanding of requirements.
Comparisons with the Waterfall process
New teams will almost invariably try to relate the Scrum-based process to Waterfall. This, however, is something to avoid. It's important to follow Scrum fully and correctly, and it's the ScrumMaster's job to make sure his or her team knows how to do this.
Not only is the team culture different in Scrum but the way the team works with the customer is usually different as well. This is another area for the ScrumMaster to focus on, since working with the customer is key in Scrum.
My hope is that the suggestions above can help guide new teams — as well as experienced ones — through the daily stand-up. Using this meeting as effectively as possible can set the tone for the entire sprint, helping a team understand its own progress and reach success.