The Scrum Guide says the following about the Daily Standup:
The Daily Standup or Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours. The Daily Scrum is held at the same time and place each day to reduce complexity.
During the meeting, the Development Team members explain:
- What did I do yesterday that helped the Development Team meet the Sprint Goal?
- What will I do today to help the Development Team meet the Sprint Goal?
- Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?
The Development Team uses the Daily Scrum to inspect progress toward the Sprint Goal and to inspect how progress is trending toward completing the work in the Sprint Backlog. The Daily Scrum optimizes the probability that the Development Team will meet the Sprint Goal.
Daily Scrums improve communications, eliminate other meetings, identify impediments to development for removal, highlight and promote quick decision-making, and improve the Development Team’s level of knowledge. This is a key inspect and adapt meeting.
We all the know the importance of the Daily Standup, but how many teams are actually gaining real benefits from the Daily Scrum or Daily Standup? This ceremony is not meant to be a ‘Status Report’, but in reality that is exactly what this meeting has become. If you have fallen into the ‘Status Reporting’ trap, then you may want to consider cancelling your Daily Standup all together or making some simple changes to shake it up!
5 suggestions to shake up your Daily Standup:
Yes, you read that correctly. If a team of 8 people all have to give an update at a 15 minute Standup, that is less than 2 minutes per participant to provide valuable information. If someone has a question, then forget about finishing in 15 minutes. Given the time crunch, team members will hesitate to provide all the information needed in order to allow the team to gain the full benefit from the meeting in favor of meeting the 15 minute deadline. Stretch a little; give the team some extra time to collaborate – isn’t that what it’s all about?
We all know that a team should be limiting the Work in Progress (WIP). Let’s say your team should be working on only three stories at a time: review each WIP story in-depth. Allow each person who is contributing to that story to provide their insights. Address all issues or questions, or put them in the parking lot for ‘Post Standup’. (See number 3, below.) Once you have completely discussed the WIP stories, ask if people are working or need to work on other stories. This should avoid the schizophrenia that occurs with the round robin approach.
As the team is reviewing each story they will have in-depth questions, concerns, and ideas. Use the time right after the Daily Standup to pair program or swarm around items from the Standup. I like to keep a white board at hand and I write down ‘Post-Standup’ items as they come up. This gives everyone an opportunity to participate, including Developers, Product Owners and Scrum Master. There is no set time-box for Post-Standup-it is all about collaborating and getting stories to completion.
If the Product Owner (PO) has questions about the story or wants to provide insight – let them. Why Not? This is the time when the team is trying to make sure they are meeting the objectives of the Product Owner. If the PO asked a detailed question that will take more that a few minutes, move it to Post-Standup.
Banter a little! Life is too short to just jump into the heavy details of the Daily Standup or Daily Scrum. Take a few extra minutes (see #1) to strike up conversations with your teammates. Use it as an opportunity to do a little team building and get to know each other. Come prepared with an interesting topic and throw it out to the group such as “Name three things that you think will be obsolete in 10 years”. You will be surprised how far a little fun will go!Talk to Us Today