How Retrospectives Can Support Learning in Lean Startup
The build-measure-learn feedback loop in lean startup aims to help entrepreneurs to learn about the needs of their customers. Agile retrospectives are a way to reflect and learn and to agree on changes that are needed. Below are some examples describing how lean startup can be supported with agile retrospectives to learn and take actions.
In the blog post 3 rules every entrepreneur should live by, Michelle Serro shared the benefits that she gets from doing agile retrospectives:
In Agile, “retrospectives” are meetings that take place at the end of a period of work (…) where the team sits together to talk about what’s working, what isn’t, what opportunities people are seeing, and which challenges they are facing. It’s about constantly checking in and questioning whether our stated approach is still making sense given everything new we’re learning as we iterate.
Michelle describes the 3 important rules for working that that she learned from retrospectives. The first rule is to “Acknowledge Early. Address Often” by using retrospectives to address issues quickly in a positive atmosphere:
People were eager to identify anything that was standing in the way of doing great work--that became the de facto agenda item for each meeting. What’s standing in your way? And, how can we remove that obstacle together? The goal is to learn and get better as soon as possible.
Her second rule is to "Disable Auto-Pilot" which helps her to stay alert:
With Agile, you simply are not allowed to assume everything is ok unless you hear otherwise. The point is to forever question whether you are still on the best path as a team and as a company given all the new input you receive each day.
The third rule “Plan to Pivot” fits retrospectives to the lean startup, as Michelle explains:
The retrospective asks not to simply look back on the past week, but all the way back to our initial intentions. What’s more, it sets the stage for the entire team to be willing to make a pretty dramatic change of direction as soon as you get the first hints that it may be required. That doesn’t mean throwing away everything you’ve done and starting over, but it does mean you are mentally open to identifying a better opportunity that may be completely tangential to the business you initially started.
“A static business model canvas is as useless as a static 60 page business plan” said Tristan Kromer in his blog post the one minute retro. His opinion is that retrospectives help you to get to the fundamentals of lean startup. He describes the one minute retro, which for him is a way to establish a habit of doing retrospectives:
- Set a timer for one minute.
- Ask the group, “What’s the one thing in the last sprint/meeting/day/fortnight that you would like to change or improve about the way we do business/our meeting format/our coding practice/the way we order lunch?”
- Start the timer.
- Write something down on your sticky note.
- When the timer goes off, collect all the feedback.
It’s the person running the retro’s job to take the feedback and choose one and only one thing to improve for the next time period.
Tristan explains that it is important to select only one learning from the one minute retro to work on to:
- limits scope creep (which exists in process improvements as well as technical specifications);
- gives the team small wins to help show positive progress;
- is just about all you can manage in a short sprint anyway.
One minute retrospectives help to learn and find quick wins in a limited amount of time, said Tristan:
The point here is to establish the habit of a retro rather than have a perfect retro. (…) Until you cover the basics, getting into the details is irrelevant.