Daily Standup.md

Daily Standup

You should conduct these every time the team meet, which should be agreed in advance.

1 Schedule Meetings

At the start of the sprint you should spend 15 min with the team and agree the dates and times that you will meet during the current sprint, ideally every day or two. Once these dates and time have been agreed:

1. the Scrum Master should add these to the group calendar in MS Teams, setting an alert for 1 hour before each meeting.
2. Once these events have been scheduled, every member of the team should accept them to ensure they appear in their personal calendar.
3. Emphasise that this is the time the meeting will start and that the team members should arrive before this time.

2 Preparation

This should be carried out by the Scrum Master an hour before the start of each meeting.

It is very important that the Scum Master comes to each meeting fully prepared, nothing wastes time more than sitting around at the start of a meeting waiting for this to be completed!

1. Check that the Kanban board is up to date.
   1. Send a message to the rest of the team an hour before the meeting asking everyone to check and update their tasks.
   2. Are there any tasks that have been sitting in the In Progress column for more than a day? Make a note.
   3. Is the task allocation done correctly? Each task in the middle column should be allocated to a single team member and each person should have one and only one task in that column.
   4. Are there any tasks in the left column that have been allocated to team members? If so, remove the allocation and make a note to explain the process to that person.
   5. If the board is electronic, print off an A3 paper copy.
2. Calculate the progress metrics and make a note:
   1. Add up all the 'hours' for the tasks in the first two columns, this is the Work Outstanding (WO).
   2. Calculate how many Days Remaining (DR) are left before the sprint review meeting (this date should have been provided by the lab tutor).
   3. Update the Burn Down chart, this will show whether your team are On Schedule.
   4. Divide WO by DR and round up. This is the Required Burn Rate (BR), the amount of work needed per day to completed the user story on schedule.

3 Conduct the Daily Standup Meeting

This process should start on schedule and be led by the Scrum Master and should take not more than 10 min to complete. The Scrum Master should bring:

1. The printout of the Kanban board.
2. A notebook (containing the information from the previous standup if this is not the first).
3. A pen.
4. A 1 minute electronic kitchen timer (this can be borrowed from the lab staff).

As soon as the team are assembled, the Scrum Master needs to start the meeting. If there are members absent the meeting should start without them. Each section of the meeting is timeboxed and your team should use a simple kitchen timer to enforce this.

1. The Scrum Master asks everyone to put away all electronics devices including phones and computers and to form a small circle. The printout of the Kanban board should be visible to all.
2. The Scrum Master now gives a 60 second project update, including:
   1. Is the project ahead or behind schedule?
   2. The Work Outstanding (WO) in hours.
   3. The Required Burn Rate (BR) score.
   4. The date and time of the next agreed standup meeting.
3. Now each member of the team (working clockwise from the Scrum Master) is given a maximum of 60 seconds to answer the following three questions:
   1. What have you done since the last meeting? If this is not the first meeting, the Scrum Master should prompt them to say what they had agreed to do if they can't remember.
   2. What task(s) will they complete before the next meeting? The Scrum master should make a note of the tasks using a notebook and pen.
   3. Are there any issues that might stop them from achieving these goals? The Scrum Master should make some brief notes. The issue(s) raised must not be discussed during the standup meeting! If the person has left a task in the In Progress column for more than 24 hours, the Scrum Master should gently prompt!
4. The Scrum Master indicates that the meeting is over. The team now get back to work.

4 Issue Resolution

The Scrum Master reviews their notes, looking at the issues that were raised.

1. Add up the duration of all the tasks the team have agreed to deliver by the next meeting. Does this meet the BR requirements? If not, they should have a chat to the more skilled members of the team to see if they can help by taking on some extra work.
2. They spend no more than 5 min meeting individually with each team member that raised the issue helping them to resolve it. This might involve getting another member of the team to assist or pointing them to some suitable resources.
3. Now the Scrum Master can get back to work...