The tactic of DevOps minimum viable adoption

Not all your teams by default will follow the same DevOps evolution journey and reach the same adoption level at the same time. They have different starting points, capabilities, ambitions, contexts, and the like. Nonetheless, you need to somehow get them to align on certain DevOps evolution commonalities, defining the key evolution milestones that they all need to meet. To define and group those commonalities, I like to use the term DevOps minimum viable adoption. With this term, in this book we define the common DevOps adoption milestones that all the teams need to reach, no matter their situation, context, conditions, circumstances, or starting point. The concept is twofold and links very well to the production readiness review (PRR) framework that we discussed in the previous chapter. In my relatively extensive experience with DevOps adoption across the financial services industry, DevOps minimum viable adoption is the most pragmatic...