Cumulative Flow diagram is a very good starting point for stop-the-line or retrospective meeting. Here is a real example from TargetProcess development.
Posts Tagged Kanban
Following on from his description of the Kanban implementation at Lonely Planet, Bruce Taylor has now made a related presentation available – Little Bits of Cardboard.
Simple yet effective technique to discover wait and waste in your development flow. All you need to do is to visualize a complete flow of a single user story.
I’ve posted some thoughts on describing processes in terms of safeguards and ski-slopes, and how that can help teams decide an appropriate process.
One of the joys of working as a coach for EMC Consulting are the regular opportunities to have deep conversations on various topics with my colleagues when we are in the office together. For example, earlier this week myself and Simon Bennett began to discuss way of talking to our clients about process such that we can guide them towards the most appropriate choice. However much we may have our preferred approaches, they may not always be the best solution in any context. In the course of the conversation we compared various styles including waterfall, scrum and kanban, and looked at them on various scales, including risk, reward and control. None of these seemed satisfying as a language to use, until Simon suggested safety.
Read more here.
A new book has been published: “Kanban and Scrum – making the most of both”
The purpose of this book is to clear up the fog, so you can figure out how Kanban and Scrum might be useful in your environment.
The book includes:
- Foreword by Mary Poppendieck
- Foreword by David Anderson
- Updated version of original “Kanban vs Scrum” article by Henrik Kniberg
- In-the-trenches case study by Mattias Skarin
You can read it online for free (InfoQ registration required though) or buy the printed version.
Translators: If you are interested in translating this book to your language, please get in touch with my editor Diana Plesa (diana AT c4media.com).
Merry X-mas!
Kanban looks so simple. In theory. Map your flow, set limits, draw some lines and stick stories on the wall. There you go. Is that it? Obviously, no. One of the hardest things is to change your behavior, shift from “push mindset” to “pull mindset”.
Here’s a high level introduction to Kanban: http://www.crisp.se/kanban
Kanban board
Kanban results
Nov 17
I have blogged data from two teams who have been using Kanban over the last year.
Kanban kick-start example
Nov 16
Here is a detailed example of a fairly typical 2-tier Kanban board, for teams that know the basics of Kanban and are taking their first steps towards implementing it in practice.
It is sort of like a code example. Print it out and use it as a source of ideas & inspiration when you create your own board. Or copy & evolve.
Here is a detailed example of a fairly typical 2-tier Kanban board, for teams that know the basics of Kanban and are taking their first steps towards implementing it in practice.
Translations: German
It is sort of like a code example, or a condensed Kanban patterns repository. Print it out and use it as a source of ideas & inspiration when you create your own board.
If you know Scrum but are new to Kanban you might want to read Kanban vs Scrum first.
This post summarizes a Kanban session that was presented at Agiles 2009, 2nd Latin-American conference on Agile Development Methodologies.
http://alissonvale.com/englishblog/post/Kanban-Development-and-the-Paradigm-of-Flow.aspx
