Tight 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:

1. What did you do yesterday? (and did you update TFS/other bug tr​acking system)?
2. What are you going to do today? (and my current task on the physical taskboard has my picture on it)
3. Do you have any roadblocks? (aka 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 discovers 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.

Figure: Watch a Daily Scrum at Microsoft (short)

Figure: Watch a Daily Scrum at Microsoft (long)

Follow these essential tips to improve your Daily Scrum meetings:

Tip 1: Have your Scrum Master 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.

Figure: The burn down chart in tfs.visualstudio.com (TFS 2012)

Tip 2: Keep a schedule of the Daily Scrum times on a wall (+ have a recurring appointment in Outlook)

Hi [Team name],

As per our conversation, the Daily Scrum for [Project Name] will be held at [Location Name] 11:00AM (Sydney Time) every working day.

It must be held for 15 mins maximum as per standards:

Methodology - Do you do Daily Scrums (aka stand-up meetings)?

Regards,
[Scrum Master]

Figure: Schedule a recurring Daily Scrum meeting in Outlook using this template

Tip 3: Keep to the schedule. Same place, same time (and start even if people are missing)

Get started on time. Especially in the beginning, people will be late, but the meeting should be held with the remaining people. 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.

Note #1: The Product Owner (often the client) is not required at the stand up meeting. If he wants to turn up, remind him that he has tape stuck over his mouth, so he does not talk. 

Note #2: 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 4: Do you update tasks before the Daily Scrum?

Daily Scrums are more effective when team members arrive with their tasks already updated.

See SSW rule Do you update your tasks before the daily stand-up meeting?

Tip 5: Don't go into detail

Keep your answers short and concise. Do not stray from the 3 main questions. Remember to use the "Parking Lot" to record topics to discuss after the Daily Scrum.

Tip 6: No phones + no checking email. No distractions.

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 7: Use a task board (even better use an electronic one)

A task board allows people to visualize what the team is talking about.

Figure: The Task Board from tfs.visualstudio.com (TFS 2012)

Tip 8: 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 9: Don't let your Daily Scrum become a general meeting - use a "Parking Lot".

A "Parking Lot" is the place for any discussions that stop the Team from answering the 3 main questions. Only interested people stay for the "Parking Lot" to be discuss issues after the Daily Scrum.

Tip 10: If you have raised impediments, consider contacting the Product Owner

Figure: 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: 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 syncronized.

Tip 12: How do you 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: Use Skype or Lync

Use Skype or Lync to bridge gaps in geography. 

More information:

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 occured in the last 24 hours.

Figure: Daily Scrums will alert everyone if there is a major problem and get all brains aligned in the right direction. There is no sense in putting a Band-Aid on a patient's scraped knee if there is a big knife in his eye!

​

Figure: If you like this, retweet  https://twitter.com/AdamCogan/status/168175594209681408