Weave Design Tip:
Using Multiple Frameworks for Better Retrospectives
Every now and then we like to feature a framework created by one of our Weavers that we think has broad value in the community. In this design tip, I’d like to share two frameworks that extend the basic use of the Sailboat/Speedboat retrospective technique into something far more powerful. In the process, we can also explore how to design a canvas that includes multiple frameworks.

Sailboat + Kanban
This framework, designed by Agile Transformation lead Kamal Manglani from eBay, integrates Sailboat with a Kanban board to create a two-phase retrospective.

Phase one is a traditional retrospective, in which the team identifies impediments (anchors) and accelerants (puffs of wind). After a break, participants start Phase two and identify which specific impediments are under their control and which they will tackle, tracking their work in a simple Kanban board. 

The twist is that Kamal cleverly split the Kanban board into two parts: one for the participants and one for the leadership team. This allows the team to understand their role in helping the organization become more Agile, helps leaders identify their commitment to improvements and enables Agile coaches to track multiple forms of progress in a very simple manner. 

This framework is also designed to leverage Weave’s long-running forums, in which you can start a forum and leave it running for days, weeks or even months. Of course, I don’t really expect that you’ll use the same framework or even the same retrospective technique for months at a time – your team would likely get bored and the quality of the interaction would degrade. But Kamal’s insight shows that you can integrate multiple frameworks into a single image, creating greater impact in the team.
Give Kamal's framework a try! Just click on the image and you'll start a new forum in Weave.
Multi-Framework Retrospectives
I was recently asked to give a “lessons learned” talk to a major client. I strive to make my keynotes and private talks as interactive as possible, and when our client told me that the attendees were going to be remote I found myself inspired by Kamal’s framework and challenged myself to design a multi-framework canvas that would keep the attendees engaged while I was speaking.
I developed my presentation by selecting a “ baker’s dozen” (13) key lessons I’ve learned over the years that I felt were applicable to my clients’ situation. It wasn’t easy – there are many more lessons that one person learns in a lifetime. But 13 felt like the right number. I then developed a custom canvas with 6 frameworks and introduced it during my talk. 

I wanted to keep participants engaged and to promote collaboration and insight across the distributed teams. Fortunately, Weave made this really easy: I created my canvas and then created a Weave Gala. I limited the gala to 4 participants, with four colors of notes in the framework, one for each of the participants.

About 10 minutes into the talk I introduced the canvas to the participants and during the talk, at appropriate times, I invited participants to share their thoughts. At the end of the talk, while I was answering questions, a colleague downloaded and analyzed the data and we quickly presented some of the key insights:

  1. The #1 Agile value is: Individuals and Interactions over processes and tools
  2. The #1 Scrum value is: Focus
  3. The #1 Practice the team wanted to try was Continuous Integration, with Simple Design a close 2nd.
  4. For the Satir Change Curve, there is a mix of "Practice and Integration" and "Chaos".
  5. The Curve Jump framework identified JBoss, Fortran and C++ as technologies identified for RIP, with a healthy mix of promising new technologies that could/should be considered.

It was quite a success! Nearly all of the participants shared that they found the talk highly engaging! While I’d like to think it was because I gave a great talk, I suspect using Weave was the key as the participants could share their thoughts on the presentation with each other while I was speaking. 
Creating Your Own Retrospective Frameworks
If you’ve been practicing Agile long enough you’re going to find that you need to vary your retrospectives - teams find using the same technique boring and the quality of the retrospectives degrades rapidly as a result.

Creating custom frameworks is a great way to keep your teams engaged. This video gives you all of the details you need - and you're only limited by your imagination! As shown earlier, if you can draw it you can use it as a framework in Weave.
Keeping Retrospectives Fresh
Looking for more information on how to keep retrospectives fresh?

We invite you to review the Scrum Alliance Collaboration at Scale Webinar Keeping Retrospectives Fresh that Luke Hohmann produced with Ben Linders and Shahzad Zafar
Learn How to Customize Sailboat
Sailboat / Speedboat are two of the most powerful retrospective techniques ever invented! In this one hour course you'll learn how to plan, facilitate and analyze the results of Sailboat / Speedboat retrospectives to generate the high-impact results that drive Agility.