Scrum Meeting
During the sprint, it’s extremely important for the team to work collaboratively to best achieve the sprint goals. The daily scrum meeting is an important mechanism for the team to synchronize their work, remaining informed about the work being done across the team and raise impediments to be addressed.
All of the team members, including the ScrumMaster and Product Owner, are required to attend that daily scrum meeting. Any team member who cannot attend should get together with (or call) another team member prior to the meeting so that they can act as a proxy for the absent team member.
The daily scrum meeting follows a specific protocol that is designed to cover the necessary items as efficiently as possible. In general, a daily scrum meeting should take about 30 seconds per team member on the average. Any daily scrum meeting that lasts longer than 15 minutes should be a cause for concern.
The daily scrum meeting is ideally conducted as a “stand up meeting” with all of the attendees gathered in a large circle, standing and facing each other. The team starts with the first person (who goes first is up to the team), and goes around the circle until each team member has participated.
Each team member briefly talks about the key events and issues of their work. This reporting is to the entire team, not just to the ScrumMaster, so be sure to speak loudly and clearly so that everyone (including remote team members on the speaker phone) can hear and understand.
There are three key questions that are answered by each team member:
It also important that each team member actively listen to their peer’s reports. If you do not understand a report or how the work reported relates the team’s sprint plans, it is appropriate to ask questions or follow up after the meeting.
Only the team members report during the daily scrum meeting. If the ScrumMaster has updates of their own, such as impediments that are being worked on or general team announcements, the ScrumMaster can take a (30 second) turn in the circle. Similarly, the Product Owner can report on items such as work being done to write or clarify stories, etc...
Once all of the team members have reported, the ScrumMaster should call an official end to the daily scrum meeting. It is important to have a clear, crisp end to the daily scrum meeting so that team members not involved in the subsequent discussion can leave and get some work done. If follow-on discussions are needed, the appropriate people can remain, perhaps grab a chair, and continue the discussion.
Non-team members are welcome to attend the team’s daily scrum as observers. They may not interrupt or comment during the daily scrum meeting. If they have questions or issues to raise, they can approach the ScrumMaster either before or after the daily scrum meeting.
All of the team members, including the ScrumMaster and Product Owner, are required to attend that daily scrum meeting. Any team member who cannot attend should get together with (or call) another team member prior to the meeting so that they can act as a proxy for the absent team member.
The daily scrum meeting follows a specific protocol that is designed to cover the necessary items as efficiently as possible. In general, a daily scrum meeting should take about 30 seconds per team member on the average. Any daily scrum meeting that lasts longer than 15 minutes should be a cause for concern.
The daily scrum meeting is ideally conducted as a “stand up meeting” with all of the attendees gathered in a large circle, standing and facing each other. The team starts with the first person (who goes first is up to the team), and goes around the circle until each team member has participated.
Each team member briefly talks about the key events and issues of their work. This reporting is to the entire team, not just to the ScrumMaster, so be sure to speak loudly and clearly so that everyone (including remote team members on the speaker phone) can hear and understand.
There are three key questions that are answered by each team member:
- Last 24h? - What have I worked on since the last daily scrum meeting? Be specific in terms of which tasks were worked on and/or completed.
- Next 24h? - What will I be working on until the next daily scrum meeting? Again be specific in terms of the tasks. If you’ve just completed a task indicate your new task, or let the team know you need some help in choosing the next task (you can meet to discuss this right after the meeting).
- Impediments? - What impediments are getting in my way? Thes impediments become the responsability of the ScrumMaster to note them and follow up after the meeting. You can also briefly mention if you need to collaborate with another team member or if there are any other significant things the team should be aware of (with further discussion deferred until after the meeting).
It also important that each team member actively listen to their peer’s reports. If you do not understand a report or how the work reported relates the team’s sprint plans, it is appropriate to ask questions or follow up after the meeting.
Only the team members report during the daily scrum meeting. If the ScrumMaster has updates of their own, such as impediments that are being worked on or general team announcements, the ScrumMaster can take a (30 second) turn in the circle. Similarly, the Product Owner can report on items such as work being done to write or clarify stories, etc...
Once all of the team members have reported, the ScrumMaster should call an official end to the daily scrum meeting. It is important to have a clear, crisp end to the daily scrum meeting so that team members not involved in the subsequent discussion can leave and get some work done. If follow-on discussions are needed, the appropriate people can remain, perhaps grab a chair, and continue the discussion.
Non-team members are welcome to attend the team’s daily scrum as observers. They may not interrupt or comment during the daily scrum meeting. If they have questions or issues to raise, they can approach the ScrumMaster either before or after the daily scrum meeting.
