How to Avoid Waste – a Lean Retrospective

In Implementing Lean Software Development: From Concept to Cash Mary and Tom Poppendieck categorised waste encountered in software development into:

  1. Partially Done Work
    Is work going from beginning to end in a single rapid flow? For example; are you building up large amounts of untested or undeployed work? Do you have long-lived feature branches?
  2. Extra Features
    Do your customers or users actually need what you’re building?
  3. Relearning
    Do you spend a lot of time rediscovering what you (or someone else on your team) already knew at one time?
  4. Handoffs
    Is your team truly collaborating, or handing off bits of work to each other, losing tacit knowledge in the process?
  5. Delays
    Does work typically spend lots of time stalled awaiting things like environments, someone to be available, or decisions to be made?
  6. Task Switching
    Do you find that you lose time to context switching frequently?
  7. Defects
    Does your team have a low defect rate? How late in the development process do you find defects? Could this feedback loop be shorter?

 

This retrospective format aims to facilitate a broad discussion around waste, using the 7 Wastes of Software Development as a skeleton. It focuses both on improving areas where we incur waste, but also on enhancing areas where we already do a good job of avoiding it!

 

If you’re familiar with the format presented by Diana Larsen and Esther Derby in Agile Retrospectives: Making Good Teams Great this exercise fits really well into the “Gather Data” phase.

 

  1. To get started, populate the room with 7 flip-chart sheets, each representing a category of waste. Be sure to give enough room for small groups to congregate around them, so spread them out around the room!

  2. Begin with a brief description of each of the different types of waste (see here for a more in-depth discussion on each). Let the team know that the core questions they’re trying to answer are:

Where are situations where we incur this type of waste?

 

Where do we do a good job of avoiding this type of waste?

  1. Now, lets gather some data! Break into groups of 2-3 people. Where possible, try to get a mix of roles in the groups. This helps to build awareness of the waste everyone else is dealing with on your team.
  2. Then, each team selects their first topic and spends a short amount of time writing post-its to answer the two questions above*. I generally timebox this to 2 or 3 minutes per topic. When the timebox is up, cycle to the next category until everyone has had an opportunity to contribute to each.
    * hint – limit this to two post-its per person for each topic to avoid getting swamped with data!
  3. The next stage is to decide on what’s important for the team to address. I generally use simple dot-voting for this, and follow up with a bout of lean coffee to dig deeper, explore some root causes and ultimately generate some experiments we can try to help reduce this type of waste!

 

Have you tried this before? Let us know how you get on in the comments!

 

 

 

Tony O'Halloran
2 Comments
  • Justin Blass
    Reply

    Hey TONY! This is a great retro. I ran this retro with some minor variations for two teams recently both cases brought up plenty to explore further. If I were to run it again – I want to supply a few more follow up questions related to each waste (some waste didn’t get much attention). However we didn’t rotate through each waste in small groups (that would likely have helped). Love the visuals you use. All in all – a good retro to keep things lean!

    September 4, 2017 at 1:49 pm

Post a Comment