So far, in our series focussing on Agile Framework and Scrum, we’ve covered retrospectives in general, check-ins in particular, and we’ve shown you a crate full of examples why draw.io’s Board Macro is the go-to solution for creating visual tools that make the entire process run more smoothly (and effectively). Read on for our next topic: Inspect and Adapt with draw.io Board Macro.
(And for those just joining us, the links below will quickly get you up to speed):
draw.io for Agile Retrospectives
Agile Check-ins with draw.io’s Board Macro
Inspect and adapt
First, what does it mean to inspect and adapt? And where does the concept come from?
Inspect and Adapt is an essential part of the role of an agile coach. Whether it’s processes that aren’t even running yet, or minor improvements that make the current workflow even more successful, you need to have the individual components disassembled in order to identify (inspect) them. Only then can you improve (or adapt) them.
Inspect and adapt requires the acknowledgment that no individual has all the answers, and no single approach to a problem is going to succeed all of the time. Only by taking the time to periodically check in with the team and evaluate progress can we be assured that the train will stay on the tracks.
When we truly follow the concept of inspect and adapt, our teams are more likely to maintain an ongoing cycle of improvement that feeds on past successes (and failures) in order to maintain a course toward future success. As you continue to inspect and adapt, you can steadily progress toward your goals.
How can we help?
As with the topics in our earlier blogs mentioned above, there are many ways to get the job done. But the most effective format for a successful inspect and adapt session is a visual one. There are a variety of visualization models that can help take you through the steps of the process. And each one is more easily created and manipulated using draw.io’s Board Macro.
After you’ve checked in and you’re ready to get down to business, your team’s first task is to identify the topics of conversation. Because, as we mentioned in an earlier post, in Agile/scrum meetings, the team drives the bus. No control freak telling them what to do or how to think. No set agendas. It’s all up to the team. But how to decide?