In previous posts, we’ve discussed Agile Retrospectives in general and how draw.io’s Board Macro can help make them more efficient and effective, streamlined and sexy, functional and fun. Now we focus on specific aspects of the agile framework process to show you even more great examples and give you inspiration for your next agile retrospective. Here’s how to do agile check-ins with draw.io’s Board Macro.
For those who may be coming in cold on the agile framework, here’s a Cliff’s Notes version of the overall topic so you can easily follow along.
An Agile Retrospective is a team meeting held at the end of each Agile sprint (a short cycle of work that divides a larger project into more manageable chunks). Its purpose is to give the team an opportunity to reflect on how to make their efforts more effective, so they can tune and adjust their approach accordingly before the next sprint.
Retrospectives involve multiple steps that are crucial to their smooth completion as well as the comfort of the participants and their willingness to share honest opinions and evaluations of the process.
The first step is the check-in.
Check-in activities are a way to assess how participants feel at the moment of the meeting, whether it’s their feelings about the meeting in general or their evaluation of the previous sprint.
The check-in is also a way for the team to get to know each other better. Overall, the check-in can significantly influence the tone of the retrospective discussion. Check-ins are conversation starters for your team and can help ease everyone into the retrospective. Depending on the team mood, the check-in can have a powerful influence on the further course of the meeting.
So, do you just say, “Hey guys! How are you feeling?” No. There are more productive (and more fun) ways to get an accurate window into the mood of your team by employing Agile Check-ins with draw.io’s Board Macro.