Daily stand-up meeting

by Dan Tivadar
29 sep 2016
Software development

▶ The stand-up has particular value in Agile software

development processes, such as Scrum or Kanban, but can be utilized in
context of any software-development methodology.
Software development

▶ The stand-up has particular value in Agile software

development processes, such as Scrum or Kanban, but can be utilized in
context of any software-development methodology.
▶ The meetings are usually timeboxed to between 5 and 15 minutes, and take
place with participants standing up to remind people to keep the meeting
short and to-the-point. The stand-up meeting is sometimes also referred to as
the "stand-up", "morning rollcall" or "daily scrum".
Software development

▶ The meeting should take place at the same time and place every working day.
Software development

▶ The meeting should take place at the same time and place every working day.
▶ All team members are encouraged to attend, but the meetings are not postponed if
some of the team members are not present.
Software development

▶ The meeting should take place at the same time and place every working day.
▶ All team members are encouraged to attend, but the meetings are not postponed if
some of the team members are not present.
▶ One of the crucial features is that the meeting is intended as a communication
vehicle for team members and not as a status update to management or to other
stakeholders.
Software development

▶ The meeting should take place at the same time and place every working day.
▶ All team members are encouraged to attend, but the meetings are not postponed if
some of the team members are not present.
▶ One of the crucial features is that the meeting is intended as a communication
vehicle for team members and not as a status update to management or to other
stakeholders.
▶ Although it is sometimes referred to as a type of status meeting, the structure of
the meeting is meant to promote follow-up conversation, as well as to identify
issues before they become too problematic.
Software development

▶ The meeting should take place at the same time and place every working day.
▶ All team members are encouraged to attend, but the meetings are not postponed if
some of the team members are not present.
▶ One of the crucial features is that the meeting is intended as a communication
vehicle for team members and not as a status update to management or to other
stakeholders.
▶ Although it is sometimes referred to as a type of status meeting, the structure of
the meeting is meant to promote follow-up conversation, as well as to identify
issues before they become too problematic.
▶ The practice also promotes closer working relationships in its frequency, need for
follow-up conversations and short structure, which in turn result in a higher rate of
knowledge transfer – a much more active intention than the typical status meeting.
Software development

▶ The meeting should take place at the same time and place every working day.
▶ All team members are encouraged to attend, but the meetings are not postponed if
some of the team members are not present.
▶ One of the crucial features is that the meeting is intended as a communication
vehicle for team members and not as a status update to management or to other
stakeholders.
▶ Although it is sometimes referred to as a type of status meeting, the structure of
the meeting is meant to promote follow-up conversation, as well as to identify
issues before they become too problematic.
▶ The practice also promotes closer working relationships in its frequency, need for
follow-up conversations and short structure, which in turn result in a higher rate of
knowledge transfer – a much more active intention than the typical status meeting.
▶ Team members take turns speaking, sometimes passing along a token to indicate the
current person allowed to speak.
Software development

▶ The meeting should take place at the same time and place every working day.
▶ All team members are encouraged to attend, but the meetings are not postponed if
some of the team members are not present.
▶ One of the crucial features is that the meeting is intended as a communication
vehicle for team members and not as a status update to management or to other
stakeholders.
▶ Although it is sometimes referred to as a type of status meeting, the structure of
the meeting is meant to promote follow-up conversation, as well as to identify
issues before they become too problematic.
▶ The practice also promotes closer working relationships in its frequency, need for
follow-up conversations and short structure, which in turn result in a higher rate of
knowledge transfer – a much more active intention than the typical status meeting.
▶ Team members take turns speaking, sometimes passing along a token to indicate the
current person allowed to speak.
▶ Each member talks about progress since the last stand-up, the anticipated work
until the next stand-up and any impediments, taking the opportunity to ask for help
or collaborate.
Three Question
Three Question

▶ 1) What did you do yesterday?

Three Question

▶ 1) What did you do yesterday?

▶ 2) What will you do today?
Three Question

▶ 1) What did you do yesterday?

▶ 2) What will you do today?
▶ 3) Are there any impediments in your way?
Three Question

▶ 1) What did you do yesterday?

▶ 2) What will you do today?
▶ 3) Are there any impediments in your way?

▶ Standing, rather than sitting, reinforces the idea that the meeting is intended
to be short and discourages wasted time.
Three Question

▶ 1) What did you do yesterday?

▶ 2) What will you do today?
▶ 3) Are there any impediments in your way?

▶ Standing, rather than sitting, reinforces the idea that the meeting is intended
to be short and discourages wasted time.
Three Question

▶ 1) What did you do yesterday?

▶ 2) What will you do today?
▶ 3) Are there any impediments in your way?

▶ Standing, rather than sitting, reinforces the idea that the meeting is intended
to be short and discourages wasted time.
▶ The stand-up is not meant to be a place to solve problems, but rather to
make the team aware of current status. If discussion is needed, a longer
meeting with appropriate parties can be arranged.
SDL Daily reporting
You must do...
SDL Daily reporting
You must do...
▶ Have your project management tool visible
SDL Daily reporting
You must do...
▶ Have your project management tool visible
▶ Specify the ID of the task
SDL Daily reporting
You must do...
▶ Have your project management tool visible
▶ Specify the ID of the task
▶ Specify the NAME of the task
SDL Daily reporting
You must do...
▶ Have your project management tool visible
▶ Specify the ID of the task
▶ Specify the NAME of the task
▶ Specify the status of the current/previous task
SDL Daily reporting
You must do...
▶ Have your project management tool visible
▶ Specify the ID of the task
▶ Specify the NAME of the task
▶ Specify the status of the current/previous task
▶ Describe in one sentence the progress for the current task
SDL Daily reporting
You must do...
▶ Have your project management tool visible
▶ Specify the ID of the task
▶ Specify the NAME of the task
▶ Specify the status of the current/previous task
▶ Describe in one sentence the progress for the current task
▶ You have to talk about the impediments or the blockers
SDL Daily reporting
You must do...
▶ Have your project management tool visible
▶ Specify the ID of the task
▶ Specify the NAME of the task
▶ Specify the status of the current/previous task
▶ Describe in one sentence the progress for the current task
▶ You have to talk about the impediments or the blockers
▶ Is recommended to provide a time estimation
SDL Daily reporting
You must do...
▶ Have your project management tool visible
▶ Specify the ID of the task
▶ Specify the NAME of the task
▶ Specify the status of the current/previous task
▶ Describe in one sentence the progress for the current task
▶ You have to talk about the impediments or the blockers
▶ Is recommended to provide a time estimation
▶ Stay focused
SDL Daily reporting
You must do...
▶ Have your project management tool visible
▶ Specify the ID of the task
▶ Specify the NAME of the task
▶ Specify the status of the current/previous task
▶ Describe in one sentence the progress for the current task
▶ You have to talk about the impediments or the blockers
▶ Is recommended to provide a time estimation
▶ Stay focused
▶ Ask questions that can be answered YES or NO
SDL Daily reporting
Don’t do that...
SDL Daily reporting
Don’t do that...
▶ Talk about personal life or problems
SDL Daily reporting
Don’t do that...
▶ Talk about personal life or problems
▶ Don’t specify just the Id of the task, without name
SDL Daily reporting
Don’t do that...
▶ Talk about personal life or problems
▶ Don’t specify just the Id of the task, without name
▶ Describe the functionality of the task
SDL Daily reporting
Don’t do that...
▶ Talk about personal life or problems
▶ Don’t specify just the Id of the task, without name
▶ Describe the functionality of the task
▶ Describe the implementation method that you’ve chosen
SDL Daily reporting
Don’t do that...
▶ Talk about personal life or problems
▶ Don’t specify just the Id of the task, without name
▶ Describe the functionality of the task
▶ Describe the implementation method that you’ve chosen
▶ Talk more than 3 minutes
SDL Daily reporting
Don’t do that...
▶ Talk about personal life or problems
▶ Don’t specify just the Id of the task, without name
▶ Describe the functionality of the task
▶ Describe the implementation method that you’ve chosen
▶ Talk more than 3 minutes
▶ Interrupt the other colleagues from their speech
Q&A

???