How to run an efficient developer standup

efficient_standup.txt

I have found success in the following daily/n-weekly standup strategy for an efficient standup that stays within time for large engineering teams:
- Create a google slide with the standup agenda for the day that is shared for remote standups (for in person standups, the contents of this slide can
 be maintained on a whiteboard somewhere, or printed)
- The slide will serve as both a visual agenda / guide for the standup
- The slide will solicit discussion topics before standup begins, with the intention of discussing these topics at the end of standup. This way, only
 those interested in the discussion may remain after standup to discuss. This promotes streamlined standups by avoiding discussions among ICs, keeping status reports brief.
- The slide will reflect your knowledge on what your individual contributors (ICs) are currently contributing to and keep the standup ordering consistent, by listing both projects and associated contributors (ensuring the two are accurately synced). Keep the slide updated with what a given IC is contributing towards
- The standup ordering of your ICs should remain the same everyday. This leads to predictability in when each IC is expected to speak, so they can prepare. If any IC is not present, you can circle back to them at the end of the status portion of the agenda if they join late.
- The slide should offer an opportunity for ICs to discuss prioritization or raise issues not related to their current work, so transparency and constant communication
 between leaders/managers and ICs is facilitated/encouraged and allow for agile shifts in resources

The slide would be formatted as follows:
-----------------------------------------------------------------
1. Discussion Topic Solicitation

2. <Team> Stand-up

Project # 1

   Resource A, Resource B

Project # 2

   Resource C, Resource D, Resource E

Project # 3
   Resource F

3. Prioritization & New Issue Solicitation

4. Discussion of topics brought up in (1.)
-----------------------------------------------------------------