Standard | How to Facilitate a Standup Meeting

Standup meeting, also called daily standup or scrum meeting, is used in agile project management to keep the team closely collaborated. The discussion, in general, focuses on solving problems and making decisions within the project team. To run standup meetings successfully, we can look at the following best practices: 

Select Clear Objectives  The meeting allows teams to share updates briefly and get teams aligned and focused on goals. Note that this is not a status meeting, so updating the status should be relevant to the dev discussion. 

Keep it short. Standup Meeting should be brief (aim for not more than 15 mins). It's a quick check-in rather than a lengthy discussion.

Cadence: Choose how often to meet (daily/ every other day or once weekly) depending on the workload and deliverables but make it consistent.

• Recurring: Meet at the same time, whatever is the cadence. Ensure everyone involved is available.
• In-charge: The project manager should be in charge of keeping the meeting productive. 
• Clear Structure: Everyone involved should share the below three
  • What's Completed since the last meeting
  • What is Planned to be completed before the next meeting
  • Issues and help needed (Schedule for a separate meeting to discuss the issues should be decided during the standup meeting)
• Walk the board (optional): Instead of doing a round-robin, the project manager should display a visual project management report or project plan so that the standup meeting moves through each work item. 
• Meeting Minutes (optional): sending minutes after the meeting, incredibly the actionable ones. This will also help any team members who could not stay on the same page as the rest of the group. Minutes should be shared on the same day (preferably within 2 hours)​

Communication suggestion: Although we have standup meetings, we recommend offline communication with your team and business users. ​
Standup meetings should focus on problem-solving rather than status checking. Otherwise, the discussion can become a micromanagement burden to the project team. ​