Are Daily Standups becoming too long and turning into status reports for your remote Agile teams?

All answers to this question.

Remote standups often fail because people feel the need to justify their 8-hour day. To fix this, use a digital board like Jira or ADO and "walk the board" from right to left (starting with what is closest to 'Done'). This shifts the focus from "what I did" to "how we move this card to completion." If a technical discussion starts, the Scrum Master must intervene and suggest a "parking lot" or "16th minute" meeting for only those involved. Keeping it strictly about blockers and the Sprint Goal is the only way to respect everyone's' time and maintain the 15-minute timebox.

   Answered 2024-01-07 by Patricia Moore

Do you have a "no-manager" rule for your standups, or is a supervisor present? Often, the presence of leadership subconsciously forces developers into a reporting mode rather than a peer-to-peer sync.

   Answered 2024-01-10 by Thomas Clark

• Thomas, we do have a Director who attends "to listen," but it definitely changes the vibe. We started asking the Director to keep their camera off and save all questions for the very end. This has helped the developers talk to each other again instead of performing for the boss. It made a huge difference in the meeting's' duration and utility.

     Commented 2024-01-12 by Daniel Lewis

Try using a timer and a "talking stick" (even a virtual one). Once the time is up for a person, they must pass it on. This discourages long-winded technical explanations.

   Answered 2024-01-15 by Barbara Taylor

• Good idea, Barbara. We actually use a randomizer tool to pick the next speaker, which keeps everyone on their toes and prevents the "zoning out" that happens in remote calls.

     Commented 2024-01-17 by Jessica Williams