Async agile 1.0, is distributed agile 2.0!
This blog expands on the ideas from “The Async-First Playbook”. You can either browse through the posts using the grid below, or start at the very beginning. Alternatively, use the search bar below to find content across the site.
Why you may find it tough to introduce asynchronous work in your organisation
Introducing change in large organisations is tough. Synchronous work has a 250 year old legacy and organisations are used to it for a number of reasons. As an advocate of asynchronous work, you need to be aware of the potential challenges you’ll face when you try to introduce a new way of working in any organisation.
This article outlines some of the obstacles you should expect.
There’s got to be a better way to work
Distributed agile software development projects rely too much on synchronous communication. This not only leaves too little time for deep work, it also leads to burnout, less diverse teams and knowledge and information sharing practices that don’t scale.
Asynchronous work has the potential to transform distributed agile so it’s fun, sustainable, inclusive and scalable.