Here is a teaser for “The Kanban Kick-start Field Guide“.
The document is almost ready by now, with some minor work left on the boosts in the “After the Kick-start” chapter. And, yes, there is a section about Depth of Kanban in there.
|The Cover of the book (it may change)|
Due to our constraints (few coaches for many teams, focus on evolution rather than direct better flow) the Kanban Kick-start has developed the following aspects that may differ from other ways/methods/processes for introducing Kanban:
The team is the driver. The coach is simply helping the team to set its kanban system in place.
In its purest approach, the coach does not design the kanban system for the team, the team does it. This may not become an optimal kanban system, but this is not the goal (yet).
The goal is to increase the team’s understanding about itself and its context so that it can evolve by itself and become what it must.
At the end of the workshop, the team has a visualization board, explicit work policies and a way-of-working with the board.
The workshop, the board and the policies are for the team and by the team.
The agenda of the Kick-start is modular to fit teams with different maturity.
The Kanban Kick-start is packaged in such a way to be easily “sold” to managers under stress: It is a one day workshop with the whole team (6-8 hours).
Not everything actually happens during one day, some preparation are required before the workshop with the manager and team-lead.
The coach is also required to follow-up the team after the workshop to: a) help the team implement the kanban concepts that didn’t stick during the workshop (or that were left out), and b) make sure that the team can sustain its kanban system (by adapting the system or coaching the team).
Table of Contents
The current table of content looks like this:
Glossary of Frequently Used Terms
Check back soon for the real stuff!