Your daily standup should be asynchronous. Here’s why

<p>The first time I joined a team that did an asynchronous daily standup meeting &mdash; or daily Scrum &mdash; I admit I was sceptical.</p> <p>The idea of not having a fixed time for checking in with everyone seemed counterintuitive (at best &mdash; at worst, maybe a recipe for chaos).</p> <p>Were big updates falling through the cracks? Were people staying aligned without their regular, scheduled, synchronous interactions?</p> <p>The answer turned out to be a resounding&nbsp;<em>&ldquo;no&rdquo;</em>. Here&rsquo;s why.</p> <h1>Traditional vs asynchronous daily standups</h1> <p>The traditional standup emerged in the early 2000s and has been a go-to strategy for years.</p> <p><strong>But the realities of modern development &mdash; particularly for remote teams and distributed teams, and the flexible schedules that characterise modern software engineering teams &mdash; demand a new approach.</strong></p> <p>We don&rsquo;t use tech from the early 2000s &mdash; shouldn&rsquo;t our approach to building tech also be changing?</p> <p>&nbsp;</p> <h2>Option 1 &mdash; The asynchronous stand-up</h2> <p>Instead of logging in for a live meeting, team members share their updates within a dedicated platform or tool (more on this later) at a time that works for them within the day.</p> <p><a href="https://alex-omeyer.medium.com/your-daily-standup-should-be-asynchronous-heres-why-58f5da75ff0e">Visit Now</a></p>