Guidelines for Stand-Up Meeting

Setup stand-up meeting for my team.

Purpose of this meeting is to improve communication among the team and promote team focus.

Rules for Stand-Up:

• Arrive on time or early.
• All team members attend and participate.
• Last arrive speak first and choose who should speak next.
• The meeting  duration is not more than 20 minutes. (1 -2 minutes person and 5 minutes for discussion).
• Maintain your own task list and note the actions or tasks items you volunteer for.
• Be prepared to present three topics and keep your report specific, precise and short in order to help the meeting end within 20 minutes.
  • Eg: Notes:

  • What did I do since the last meeting? ------------------------------------- -- Designed new feature -- Implemented component X -- Fixed bug related to Y -- Updated confluence about support task Z -- X details communicated to FAL & RMS -- Read up on X API & ABC technologies   What will I be doing until the next meeting? -------------------------------------------- -- Project meeting related to XYZ -- Code review / Peer review -- Implement component XYZ -- Redactor code base  related ZYU   What obstacles are blocking my progress & any issues? ----------------------------------------------------- -- Item 1 -- Item 2

• Listen to other team member's status in case it might relate to your tasks or impact you.
• Don't interrupt people when they are talking. Pay attention to other team members and note items that you¿ll need to cover in follow-up discussions.
• Don't agree to decisions or action you don't understand. Ask questions and insist on answers when you need clarification.
• If you raise an issue, blocker or question that can't be resolved in a minute, ask to discuss with the parties involved after the meeting
• No story telling.
• No problem solving.
• Speak to the team.
• Latecomers ???

References:

1. It's Not Just Standing Up: Patterns for Daily Standup Meetings
2. Scrum guide