Typical Agile transformation roadmap
Alex Crossley
Simplifying how to stay ahead by delivering value to customers continuously and sustainably by coaching business people and technologists to work together.
Yes, yes, I hear you... "There is no typical Agile transformation!", well I am telling you there is. I am not saying all teams are in the same starting position, or that the same solutions work in every environment, but there are so many similarities that I can call them typical.
I have led teams for over 20-years and been transforming them to Agile for around the last 10-years. Here is my take on this.
Let me put it this way; a pizza is a pizza, but there are many topping that fundamentally change the pizza. However, before we even start on talking about the toppings, let's just agree that we need a base, a sauce, and some cheese. Even these might vary, gluten-free (ugh) or BBQ sauce, but these choices are fairly limited and in the end if you go with a wheat base, tomato sauce, and mozzarella cheese; then you are on safe ground. What I am suggesting is the Scrum and Kanban are your safe margarita pizza. The base is a cadence, the sauce is the ceremonies and the cheese is the team and servant leaders. Get these three ingredients right, and then think about how to take it to the next level.
What about the toppings? Yeah, these aren't so typical and so you might prioritise some over others and your team might have a preference. Measures is pretty standard, and so is progressive elaboration. I'll maybe leave these topics for a future article.