Purpose:

It provides a simple means for Scrum Team members to keep each other up to date without spending a lot of time in meetings or having to write and read status reports.

Objective:

A quick discussion among Scrum Team members of progress completed, plan work, and problems.

Description:

The daily stand-up is not a status meeting. The intended purpose is for the Scrum Team members to share with each teammate their agenda for the day and to set their focus. No one should attend a daily stand-up with a pen and paper to record minutes! Just listen. If someone mentions a block and needs the Scrum Master’s help, action can be taken, preferably after the daily stand-up.

Every day, the Scrum Team assembles for a stand-up meeting, usually in front of a Scrum board, to make sure they are working together, assess how they are doing, and plan the day’s work.

To minimize disruption, it is important that the meeting is kept strictly to time and happens at the same time and place every day. It is not a status update, and no-one other than the Scrum Team is permitted to participate.

The meeting avoids duplication of effort or the risk that any item will be left undone. It also forces the team to articulate anything that is missing and act on it, as well as encouraging cross-functional working or swarming on any particularly intractable problem.

RASIC:

Daily Scrums

Inputs:

  • Task on Sprint Backlog has been updated

Outputs:

  • Sprint Backlog and task progress updated
  • Sprint Log
    • Update Impediment Backlog
    • Updated Comfort Level
    • Scrum of Scrum’s agenda items
  • Arrange additional meetings

Controls:

  • Working Agreement
  • Definition of Done
  • Sprint Log

Task Instructions:

What did you do yesterday?

    1. Using the Sprint Backlog, each Sprint Team member is responsible for providing a quick rundown of what got done yesterday, and if anything did not get done, then why.

This isn’t the time for each person to run down their whole to-do list – they should focus on the large chunks of work that made up their deep focus time, and the activities that are relevant to your team as a whole.

What are your goals for today?

    1. Using the Sprint Backlog, each Sprint Team member is responsible for providing what they plan to accomplish today, in other words, what they can be held accountable for in tomorrow’s daily scrum meeting.

What obstacles are in your way?

    1. Using the Sprint Backlog, each Sprint Team member is responsible for describing anything preventing contributors from getting your work done.

Things to bring up here might be technical limitations, departmental and team dependencies, and personal limitations (like vacations booked, people out sick, etc.).

2. Using Daily Scrum Log, [the Project Manager] with support from Sprint Team member(s) is responsible for documenting identified impediments.

How close are you to hitting your Sprint goals, what your comfort level?

    1. Using Daily Scrum Log, [the Scrum Master] with support from Sprint Team member(s) is responsible for documenting comfort level.

This will help the scrum master get an idea of how the team is feeling about how their day-to-day activities are impacting overall goals for the team, and how contributors are feeling about the pace of the sprint.