An important part of agile culture is to be honest and forthcoming about your mistakes, so I'd like to share one that I've made in a key diagram that exists in both our Disciplined Agile Lean Scrum Master (DALSM) courseware and in the book Choose Your WoW! This blog posting is my "failure bow" regarding mistakes that I made in the flowchart for how to choose between DA life cycles.
Figure 1 presents the original flowchart as it currently appears in the book and courseware. Don't worry, we're in the process of updating both. I'm writing this blog now because I want to make this update publicly available as quickly as possible to support people's learning journeys. There are two problems in Figure 1:
Figure 1. Choosing a DA lifecycle (original diagram).
The update to the diagram is presented in Figure 2. You can see that we've changed one of the Yes options to be No. More importantly, we've reworded the decision point so that it's clearer. We had several people point out that they didn't understand the original wording of the question about potential disruption. I had written that question from the point of view of a team composed of people with a traditional background. But, many teams now have an agile background, having gotten started with a framework like Scrum only to find it insufficient for their needs. Such teams wouldn't be disrupted, at least not very much, by adopting the Agile lifecycle. Thus we've reworked the question to instead ask about the team's agile background.
Figure 2. How to choose a DA life cycle (updated).
An important point that I would like to make about the flowchart of Figure 2 is that this is the logic that we suggest you follow, but you may still decide to make other decisions. For example, consider the decision point in the bottom-right corner. You may be working with a team that is new to agile but still decide to adopt the agile lifecycle over the lean lifecycle because you're willing to invest in the time and expense of training and coaching them in agile ways of working (WoW). Fair enough, that's your call.
I hope that this update has cleared up any confusion you may have had around this diagram.