{"id":4638,"date":"2021-09-09T18:10:45","date_gmt":"2021-09-09T18:10:45","guid":{"rendered":"https:\/\/geekbot.com\/blog\/?p=4638"},"modified":"2024-01-11T13:04:29","modified_gmt":"2024-01-11T13:04:29","slug":"daily-huddle-best-practices","status":"publish","type":"post","link":"https:\/\/geekbot.com\/blog\/daily-huddle-best-practices\/","title":{"rendered":"5 Daily Huddle Best Practices (In-Depth Look)"},"content":{"rendered":"\n

Daily huddles are an important part of keeping your Scrum team on track with their sprints. But as we\u2019ve previously written about<\/a>, they\u2019re often seen as a waste of time. This usually means your daily huddles aren’t as effective as possible (i.e. the meetings last way too long, engineers get interrupted just as they become fully immersed in coding, and so on).<\/p>\n\n\n\n

To help your team get back on track with running productive daily huddles that solve blockers and improve sprints, we cover 5 daily huddle best practices<\/strong> in this article. <\/p>\n\n\n\n

    \n
  1. Keep Daily Huddles Brief<\/a> <\/li>\n\n\n\n
  2. Don’t Problem Solve During the Daily Huddle<\/a><\/li>\n\n\n\n
  3. Make Sure One Person Speaks at a Time<\/a><\/li>\n\n\n\n
  4. Incentivize Attendance<\/a> <\/li>\n\n\n\n
  5. Schedule the Daily Huddle at the Start of the Day<\/a><\/li>\n<\/ol>\n\n\n\n

    We also look at how Scrum teams (from Zapier<\/a> to GitHub<\/a>) use our asynchronous meeting tool to run faster and less disruptive daily huddles in Slack and MS Teams.<\/p>\n\n\n\n

    Note<\/strong>: Geekbot is free for teams of 10 or fewer. For teams over 10, Geekbot is $2.50 per user per month. Start your free trial today<\/a>.<\/em><\/p>\n\n\n\n

    <\/div>\n\n\n\n

    1. Keep Daily Huddles Brief<\/h2>\n\n\n\n
    <\/div>\n\n\n\n

    Daily huddles (also known as daily scrum meetings<\/a>) are meant to be brief \u2014 15 minutes at the longest, from start to finish. But daily huddles can quickly drag on, for several reasons, including:<\/p>\n\n\n\n