Multiplicity: All about Expanding your Product Line
Everything (you need to know) about the Daily Scrum
August 7, 2015
What is the Daily Scrum?
The Daily Scrum, also known as the daily scrum meeting, daily stand-up meeting, daily huddle, morning roll-out, etc., is for the team to self organize towards achieving their Sprint Commitment. To put it plainly, it is a recurring meeting where your team gathers to provide individual updates about what has been done, what needs to be done, and where there are issues on each day of a sprint.
What is the PURPOSE of daily scrum?
Daily Scrums improve communications, identify barriers and impediments to development, highlight and promote expeditious decision-making, and improve the development team’s level of knowledge.
The biggest and most significant purpose of the daily scrum is to raise blocking issues that are preventing forward progress, or risk issues that the Scrum Master might need to take action on.
In addition, 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.
What are the OBJECTIVES?
Team Goal – Everyone needs to approach the Sprint as a team goal, not only a set of individual goals.
Team Ownership – Each team member should own and share responsibility of the full sprint backlog.
Accountability – The team should hold each other accountable for achieving their daily commitments.
Team Sync – The daily scrum is for the team to review progress toward their Sprint goal.
Assess Risks – The team assesses any risks to their Sprint commitment.
Adjust Plan – The team makes adjustments to their plan to meet the Sprint commitment.
What are the RULES?
Same time - It is recommended to hold the meeting first thing in the morning (or as soon as everyone is available).
Duration - Timeboxed to 15 minutes (optimum) and no longer than 30 minutes.
Same location (if it's possible).
A multimedia conference room (if you have remote teams).
All team members are required to attend scrum meetings.
It is the Scrum Master's responsibility to enforce the rules.
Every team member needs to attend the daily scrum, so he or she is engaged in the entire team progress.
Always start on time.
Same time, same place, every day during the sprint to reduce complexity.
Everyone is standing up - It helps to keep the meeting short and to the point.
Everyone forms a circle - If you stand in a circle during your morning huddle, you can simply decide to go through the circle either clockwise or counter-clockwise. This ensures everyone gets a chance to speak. An alternative is to talk through one product backlog item before moving on to the next.
Only those who are committed (Scrum Master, Product Owner and Development Team) to a Sprint goal are allowed to speak.
Speak to every team member, not mainly to the Scrum Master.
Other stakeholders (For example, Head of Marketing, Enterprise Architect, or a developer from another project) may join the meeting but they are only to listen.
During the daily scrum, each team member answers the following 3 questions:
What did you do yesterday?
What will you do today?
Are there any impediments in your way?
Put time limit on individual to prevent one dominating the conversation.
Assign a note-taker to record the raised obstacles.
Write down the notes on a whiteboard or a shared document editor for easy reference and review.
Any impediments that are raised in the scrum meeting become the Scrum Master's responsibility to resolve as quickly as possible. In cases where the Scrum Master cannot remove these impediments directly himself (e.g., usually the more technical issues), he still takes responsibility for making sure someone on the team does quickly resolve the issue.
Remind the team to follow-up the tabled issues- The Development Team or team members should meet immediately after the Daily Scrum for detailed discussions, or to adapt, or re-plan, the rest of the Sprint’s work.
Keep the team on track by mentioning these 3 topics before concluding a meeting:
The number of days are left in the Sprint — This reinforces the urgency of a looming deadline.
Total points have been signed off by the Product Owner — This reinforces that it only matters if we complete stories (not just getting to code complete).
The remaining hours compared to the target plan — This provides a view of how the team is progressing, most easily represented in a Sprint Burndown Chart.
End every meeting on a positive note! - Recognize other team member accomplishments, share personal project wins and client updates.
Tools and Materials
A timekeeping device.
Scrum task board to represent the Sprint Backlog.
Sprint Backlog – Allows the team to have visibility into all of the tasks remaining to achieve their sprint commitment.
Sprint Burndown Chart – Allows the team to quantify the amount of work remaining and if the team is on track.
Additional accommodations for the distributed teams
Audio and Video.
Shared Agile Work Management Software.
Collaborative Shared Document Editor.
What Daily Scrum is -- and What it is not
An integral part of Agile Scrum practices and success.
An opportunity for team members to synchronize their work.
A commitment and coordination meeting for the entire team.
It is not a sit-down meeting.
It is not a problem-solving or issue resolution meeting.
It is not a project status meeting for the Scrum Master or management.
One last point, the overall project progress can be communicated with as burn-down, burn-up, cumulative flow diagram, etc. using a big visible chart or on a widescreen monitor. The daily scrum is not a replacement of the status reports for project management updates.
“Individuals and Interactions over Processes and Tools” - Manifesto for Agile Software Development