Make time-zones your ally. By alternating facilitation responsibilities across locations, you can make cross timezone workshops and inceptions less stressful for everyone.

Imagine calling someone on the phone, going hello! then putting them on hold!

Use the flexibility of remote work to work out your “pairing” hours. Get into the practice of writing good commit messages and pass on the baton.

Between the PO, tech lead and tester, you have representation for the three amigos of agile software development.

DoR allows the team to set a standard for user stories that developers pick up. The DoD ensures developers aren’t aiming for a moving target.

Most project management tools allow you to define a workflow for your team and visualise that workflow as a task board. When you revisit your workflow be careful not to design for the exceptions and worst-case scenarios.

Most project management tools allow you to define a workflow for your team and visualise that workflow as a task board. Your task board should be the source of truth for all the work your team is up to.

It’s much easier to apologise than to get permission. In this world of computers, the best thing to do is to do it.

Broadcast how your team will interact with other teams, using a TEAM API.

This play has examples of how you can bring the phrase “async-first” into everyday conversation, by making it a catchphrase.

While there is value in getting people together, we need to acknowledge that collaboration and creativity have little correlation with synchrony.

Agreeing on response times for various collaboration tools and channels that you use on the team is important.

Instead of trying to get everyone to agree on every decision, adopt a consent based decision making process as your default.