These days the agile tools and practices are becoming something very helpful and interesting to start using in our teams on a daily basis. As the world is turning more remote and digital we have to change and adopt strategies that were never considered in the past. One example of this is the agile stand-up; and even more interesting, the async agile stand-up.
You may wonder what’s the difference between these two types of stand-ups. The answer is very simple.
How a traditional agile stand-up works?
In a traditional agile stand-up the entire team schedules a meeting and joins in a call or in-person meeting to discuss three basic questions:
- What did you work on yesterday?
- What are you planning to work on today?
- Do you have any blocker?
With these simple questions all the people in a team can have a good idea of what others are doing, identify if someone else is working in something similar and if anyone in the team needs help to solve a problem.
This meeting usually takes from 15 to 30 minutes for a team of 8-10 people.
How do async agile stand-up works?
The idea is pretty similar, an async agile stand-up is also based on those 3 questions. The main difference is that the team members don’t have to be in a meeting at the same place or at the same time in order to complete the stand-up; they can send a written or recorded status that can be reproduced by the team in the future.
Being this said, let’s go and explore the 3 reasons why doing async agile stand-ups is a good idea.
Avoid recurring meetings
If you are like me, probably you don’t like to have recurring meetings. Don’t get me wrong on this, meetings are good if they have a goal, and if all the people have the time and energy to bring value to the conversation. Sadly a lot of live stand-ups, with the time, turn into something that is not funny and that can generate the feeling of an obligation at a certain time.
On the other hand, async stand-ups have a component of flexibility that is great for the teammates. Doesn’t matter if you are not available every day at 9 a.m. because you can submit your status at 8 a.m. or 11 a.m. and another person in the team can read it at 1 p.m.
Of course, the team has to make an agreement on the window of time when everyone can submit the status, but is a fair price to pay in exchange for all that flexibility.
Build a history
If you are not the type of team that has a person taking notes every morning, with the past of time you won’t remember the history of your own project. Probably a person faced an issue and followed a certain path to solved that was mentioned during the stand-up meeting but no one remembers.
You could also be a manager who was unable to attend a few meeting because you had another issue to solve and now you have to ask your team for a quick summary of the last days.
In async stand-ups these situations don’t exist. Everything is in words, audio or video. If someone asks for something, the history will be there.
Remote work is easier
Have you tried to coordinate a meeting with people in the Pacific, Central European, and APAC timezones? can you imagine having daily stand-ups with people distributed in those timezones? With traditional meetings, it’s very complicated or pure suffering for some people in your team.
As I mentioned before, the flexibility is great for these cases. You can easily set up a time window so that everyone has a good period of time to submit the status and others can read it. There are no limits.
In case you are looking for a tool to try out async stand-ups feel free to try Regos Team Status for Jira cloud and start having async agile stand-ups and history report in Jira.
We hope this article was helpful for you and your team and that you start running async stand-ups. If you have tried them before don’t hesitate and share your experience!