Methodology - Do you do Daily Scrums (aka stand-up meetings)?
Last updated by Tiago Araújo [SSW] 5 months ago.See historyTight project teams have a Daily 'Scrum' every day at the same time.
It was once called a 'stand-up meeting' but that discriminates people in wheelchairs.
It is best to have it standing up, so it's short and to the point. No-one wants to stand around waffling.
Everybody knows the 3 essential questions:
-
What did you do yesterday?
- Including having Azure DevOps (or other task tracking system) up-to-date
-
What are you going to do today?
- Make sure the task board has your current task "In progress"
-
Do you have any roadblocks?
- Explaing issues/impediments
Asking these questions of every team member means no-one can hide and everyone remains connected. Further, you can notice what was promised and what was performed. This enables the team to discover issues quickly and keep abreast of the progress.
The team's successes and failures are shared, and anyone who knows the answer to someone else's problem can help with a solution, after the meeting.
Video: Watch a Daily Scrum at Microsoft (short - 4 min)Video: Watch a Daily Scrum at Microsoft (long - 12 min)
"Great video guys. Remember, it is ok to change Scrum, actually, it is necessary for success. Just adhere to the values of Scrum." Stephen Forte (Board member ScrumAlliance.com)
Follow these essential tips to improve your Daily Scrum meetings:
Tip #1: Be prepared for the meeting
Before you join the Daily Scrum, check the group to see what your colleagues have been discussing and working on, and check the portal to confirm the meeting time. If you’re joining a new project or re-joining a previous one after some time away, these steps are important to keep yourself up-to-date and abreast of progress.
Then you’ll be able to say to your Scrum Master: “I've had a look at the Teams group. I am ready to join the daily Scrum”.
Tip #2: Have your Scrum Master to review the Sprint progress at the end
At the end of the Scrum, the Scrum Master should review the current burn down to check on the progress of the team.
Tip #3: Keep a schedule of the Daily Scrum times on a wall (+ have a recurring appointment in Outlook)
| To: | {{ TEAM }} |
| Recurrence: | Everyday |
| Subject: | Daily Scrum – {{ PROJECT NAME }} |
Hi {{ TEAM NAME }}
As per our conversation, the Daily Scrum will be held each day.
- Project: XXX
- Scrum Master: XXX
- Task board: XXX
<This email was sent as per Do you do Daily Scrums?>
Figure: Schedule a recurring Daily Scrum meeting in Outlook using this template
Tip #4: Keep to the schedule - Same place, same time
If a team member is missing at the beginning of the Daily Scrum, and they are not absent for any other reason, you should attempt to call them in via Microsoft Teams or your preferred communication platform. This should be done at the beginning of the meeting. If they do not respond simply continue the meeting without them. Don't worry. People learn.
If the Scrum Master is not a full-time member of the team (often they are), they should attend every now and then to check the Scrum process is being followed and the Daily Scrums are being used synchronize the team and not a general meeting.
Notes:
- The Product Owner (often the client) is not required at the stand-up meeting. If they wish to turn up, remind them that they have tape stuck over their mouth, so they don't talk
- If you are not doing an approved Sprint and doing ad-hoc work, then best if the Product Owner (aka client) attends (see Ad Hoc work)
Tip #5: Update tasks before the Daily Scrum
Daily Scrums are more effective when team members arrive when their tasks are already updated.
See Do you update your tasks before the daily stand-up meeting?
Tip #6: Don't go into detail
Keep your answers short and concise. Do not stray from the 3 main questions. Don't let your Daily Scrum become a general meeting.
Remember to use the "Parking Lot", the place for any discussions that stop the Team from answering the 3 main questions. Only interested people stay for the "Parking Lot" to discuss issues after the Daily Scrum.
Tip #7: Avoid distractions - No phones / no checking email
Technology in the Daily Scrum causes people to lose focus on the goal. The goal is for the team to synchronize by sharing what they are doing. Avoid giving people the opportunity to be distracted easily by forbidding email, SMS and mobile phones from the Daily Scrum.
Tip #8: Use a task board (even better use an electronic one)
A task board allows people to visualize what the team is talking about.
Tip #9: Carry a pen and paper
Use a pen and paper to jot things down. A whiteboard is also great for "Parking Lot" topics that arise, to be discussed after the meeting.
Tip #10: If you have raised impediments, consider contacting the Product Owner
Often the Product Owner won’t be at the Scrum. However, call the Product Owner if you have an impediment (aka roadblock). Communication with the Product Owner is essential and if you haven't touched base with him in the few days, then do so. A disconnected or absent Product Owner is a sign of dysfunction.
Tip #11: Store Daily Scrums in the Teams team so the PO can easily access it
Sometimes, the Product Owner will want to see the Daily Scrum for many teams. Adding them to every meeting would create lots of noise in their calendar. Instead, make the Teams meetings easy to find so they can locate the Daily Scrum for any project via the Teams team.
What to do when you're working for a PO directly
If you don't have a team, and you're doing ad hoc work for a PO directly, it's best to contact him for the Daily Scrum every day if possible, and follow up with an email. This will keep the 2 of you synchronized.
Tip #12: Enter Scrum meetings into your timesheets
Once you have completed your stand up, add “S” to your timesheet as per Rules to Better Timesheets.
Tip #13: Send a Daily Scrum email
To prevent misunderstandings or potential disagreements, send your Daily Scrum update via email. This ensures that everyone on your team is aware of your current tasks, even if they were unable to attend the meeting. 😊
Note: Be sure to include the project name in both the subject line and the email content, as people often read the message without referencing the subject.
| To: | Bob Northwind |
| Cc: | {{ ANYONE YOU'RE WORKING WITH }} |
| Subject: | {{ YOUR NAME / PROJECT NAME }} - Daily Scrum |
Figure: Good example - Always include what you previously worked on and what you plan on doing today
Tip #14: Use IM
After you have sent your email, you can also make it front and center by sending them a ping on IM. “Check your email for my Daily Scrum” or paste in the below (a lightweight version with only what to do).
Use Teams or Skype to bridge gaps in geography.
Focus on the Flow
"Extend this rule to focus on 'flow of value', not just people. In a continuous flow mindset, the daily standup is less about the people... it's about flow. The team faces the Scrum board and goes ticket by ticket for all the items in the 'work in progress', finding out what is needed to get it to the next stage... respecting work in progress constraints." Joel Semeniuk
When using email or IM try to be brief and as specific as possible:
Hi Bob
I have XX days until my next client booking. I have XX emails in my inbox. Yesterday I was on sick leave.
Today I am working on:
- Timepro PBIs
- Tidy inbox
Figure: Bad example - Lack of details... For example, saying "Yesterday" - if it's Monday, you wouldn't say “Yesterday was Sunday"... so if you were sick, it's more useful to go back to the prior day you were working
Hi Bob
I have XX days until my next client booking. I have XX emails in my inbox. Last Friday I was on sick leave.
Today I am working on:
- TimePro - Adding new button to the next day
- Getting my emails on "SSW.com" to zero
Figure: Good example - Clear details
Tip #15: Auto-generate your Daily Scrum with AutoScrum
AutoScrum will scan your Azure DevOps repositories and find all the PBIs that you worked on yesterday and that are In Progress today.
More details: github.com/AwesomeBlazor/AutoScrum.
More information
What should I do when blocked?
When you are blocked, you should ideally take steps to unblock yourself. However, you should know when to ask for help and understand what mode of communication is best for your task.
The ideal people to ask for assistance are:
- A fellow Developer that is Senior or knows the tech
- Your Scrum Master who can reach out to the Product Owner when issues reach beyond developing your project
What happens when you run out of tasks?
The goal is to be productive for 8 hours of the day, so communicate with the rest of the developers and work with them on any other outstanding tasks. If there are no more tasks then take the next task from the top of the Sprint Backlog.
What happens if there is a major incident?
It is important that any major incidents are dealt with first. Start with any major incidents that occurred in the last 24 hours.
Learn more about the meetings in Scrum:
- Sprint Planning Meeting
- Sprint Review Meeting
- Sprint Retrospective Meeting
- Daily Scrum (Stand-up) Meeting (this rule)
Tip: It can be helpful to finish the Sprint Planning meeting with the first Daily Scrum of that Sprint.
- Do you participate in Daily Scrum meetings?
- Do you use the status message in Teams?
- Do you keep track of a "Parking Lot" for off topic items that are important?
- Appointments - Do you make your Teams meetings easy to find?
- The War Room - Does your development room have an electronic task board?
- Do you know when and how to ask for help?
- Do you know when to send an email, a chat message, call, or organize a meeting?
- Do you participate in Daily Scrum meetings?
- Do you use the status message in Teams?
- Do you keep track of a "Parking Lot" for off topic items that are important?
- Appointments - Do you make your Teams meetings easy to find?
- The War Room - Does your development room have an electronic task board?
- Do you know when and how to ask for help?
- Do you know when to send an email, a chat message, call, or organize a meeting?