We use an agile workflow (scrum) based on two-week sprints, but these are coordinated and planned asynchronously. Getting a solid sense of how our asynchronous process works requires running through it a few times. It’s a different way of working compared to the synchronous one most companies use. However, here’s a basic overview: 1. Near the end of the current sprint, Epic Owners create, schedule, and tentatively assign tickets for the next sprint. 2. Over the next few days, developers read over the tickets, estimate, and trade these tickets around until each feels confident with the amount of work they’re committing to. 3. We use a few custom-made tools to make this easier—an app that helps us track our committed hours, as well as a checklist that we run through each sprint to verify we’ve not missed anything. 4. At the end of the sprint, each person posts an update video to later review.  5. The next sprint starts, and everyone reviews these videos when they begin their work.  6. To make sure we do get some face time, we have social chats scheduled during the sprint.  7. In addition, a retrospective thread is updated with anything we might be able to celebrate or improve about our processes. You can get a more detailed explanation of the process in our handbook.