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.

A failed test is not undesirable

When people can identify themselves in all their interactions with each other, it reflects a high psychological safety. But just like a failing test can be invaluable in coding, you need the test of “anonymous contributions allowed” to test if your psychological safety is indeed as high as you’d like it to be.

Read More

3 asynchronous techniques to help you communicate about design

As team size increases, communication becomes more complex. Small teams will eventually bring in new people. Such is life. Team size aside, you’ll find that complex decisions lend themselves better to the written word. Moreover, there are limits to what people can remember, so it makes sense to commit things to writing. If we’re designing continuously, we’re also communicating about it all the time. In today’s post, I want to share three asynchronous techniques to communicate about design.

Read More