Go async-first with your team.
If you and your team wish to work async-first and you’re not sure which practices to adopt, you've reached the right place. This method stack offers ideas for small changes you can implement on your team to go async-first, one step at a time. The launch video on this page (from a few years back) offers a quick overview.
Use the filters below to find async-first methods that are relevant to your team. For detailed articles, check out the blog.
Shift left on retros
Think retro as a process that has two parts - take inputs asynchronously and run it synchronously.
Demos only when necessary
Let’s be honest. Teams don’t always have something big to showcase every sprint. Without substantive demos, the sprint reviews become a formality and a reporting exercise. Take a pragmatic approach to sprint reviews instead.
Drop the sprint planning meeting
Sprint planning is amongst the most time consuming activities for development teams. One could argue that the value you get is not proportional to the effort you put into these meetings. With some effort you can drop sprint planning meetings completely.
Make your standup async
If all you want to share is a “yesterday, today, blockers” update, you don’t need a standup meeting.