“A leader is one who knows the way, goes the way, and shows the way.” John C. Maxwell
For over three years I have been working on a new version of the Kanban Ace Method. In summary Kanban Ace is an innovative way to organize and manage teams, it helps them improve the way they work so that any product, initiative, service, or even a whole organization can be more effective in delivering value to the customer.
The way forward was not clear, it felt like looking through a dense fog, particularly since Kanban Ace was fairly complete, we even teach courses online about it! So the temptation to write a book on what was already available was strong. However, two things dissuaded me: First there are many good introductory books about Kanban, and even though they are not the same flavor of Kanban Ace they are pretty good, and we do have a lot in common, futhermore I have deep respect for those authors. Second, I wanted to advance the state of the art, and solve problems I was seeing over and over in larger organizations struggling to do Agile Transformations.
This last challenge is difficult, how can we do an Agile Transformation for many agile teams? Teams of teams with hundreds or thousands of people inside of them. This journey of discovery took me into several useful detours: the Scaled Agile Framework, Large Scale Scrum, Disciplined Agile Delivery, the Spotify model of Tribes and Chapters, and several modern military strategies. The more I read about them, and the more I experimented with my own Kanban Ace solutions for scaling, it became clear that this was the future of Kanban Ace.
Announcing “Scalable KAFE”
Now you may say not another one! But do believe me this one is very different from the rest. It can work well with others, and it will allow you to use the best from other frameworks inside a coherent whole that is lighter and less complex, that is why I call it SCALABLE it will fit your organization.
KAFE stands for Kanban Ace for Effectiveness. Effectiveness is at the heart of the agile strategy for large organizations: improving the whole system is much more important than a tiny part of it, and many times software development is a small piece of the puzzle as Klaus Leopold makes very clear on his latest book and on this diagram:
Three key pieces of KAFE have already been written in the past two years, one has even been published in full (the Akashi Bridge) and the last one is ongoing. They are at the core of this new framework:
1. KAFE’s Akashi Bridge.
From the beginning it became clear that there is a need to welcome fellow Scrum practitioners into a larger team that also includes Kanban. The Akashi Bridge is a technique available today that makes it easy for Scrum teams to adopt Kanban Ace, keep all the roles and features they love from Scrum, and gain all the power of Kanban.
2. KAFE’s Scale.
A neutral and universal way to measure objectively the level of agility vs. complexity introduced by any scaling framework, and to pick and choose key elements for your Enterprise Agile Transformation version of Scalable KAFE. Initially we will support SAFe fully, but we will also provide you the tools and criteria to use it for any scaling framework.
3. KAFE’s Ship.
As wonderful as having a fully multi-functional team is, the fact is that it is not always possible to have many agile teams become fully multi-functional. The reasons are scarcity of specialists, scarcity of budget, and the need to work with teams using both Scrum and Kanban. KAFE’s Ship will allow you to build a Scalable Group of Agile Teams, where agility is encouraged, but limitations are also acknowledged and minimized. It shows clearly what the ideal would be (fully multi-functional) but it also provides great coordination and agility today.
4. KAFE’s Gear Levels
This technique is based on this principle: To improve an organization start at the top, where changes have a massive multiplier effect. One single improvement at the top, will become a massive improvement at the team level.
KAFE’s Gears Levels are:
- The Strategy and Vision Level
- The Portfolio Level
- The Program Level
- The Team or Operational Level
Our approach is similar to Klaus Leopold’s Flight Levels, but we also make it clear that the way the system works, the MOVEMENT can also be modified, or upgraded, this is Lean Agile Organizational re-design for higher flow and efficiency.
5. KAFE’s Movement
Notice that very level inside of an organization is connected hierarchically, and to each other, like gears in a mechanical watch to form a system. Realize that those gears, the teams, the people, the processes, can be re-positioned, and re-designed for higher efficiency and better collaboration and flow.
This re-design will allow us to create new organizational collaboration structures, or a new “movement” that makes the organization tick better. Those movement can be localized or they can reach the whole company. The way those movements are built is part of Lean Agile Transformation at scale.
Update – The Consulting Life
It seems almost unreal to me that I am updating this page 2 years after actually writing it. KAFE was delayed by very demanding work doing several Agile Transformations using SAFe, Scrum and Kanban at large companies who wanted Agile to work at scale. I see this as a good delay, since I now have plenty of real life experience making Agile work in large organizations.
However several key part of KAFE are already written, and have been used in several companies including: KAFE’s Akashi Bridge, KAFE’s Scale, KAFE’s Ship, KAFE’s Gear Levels and Movement; they have helped me deliver agile at scale. Contact me if you’d like me to lead your Agile Transformation at your company or organization, unlike most Agile Coaches, I will remain impartial and deliver a custom solution that works for you.