Here’s a really short and simple kanban intro:
Crystal clear as usual. Like the comic style!
Kanban limit of two (2). Good to know!
Observant readers will notice that the developers increased their limit to 3 a few days later :o)
Sorry – I laughed too much. Don’t be so funny if you got such an important message
Can we see comparison (with a similar comic) “One Day in Agile Land” please?
Which part of this comic was not agile?
Is the change in dev limit from 2 to 3 intended to signify anything, other than the limits can change?
I generally think that reducing the limits is a sign of improvement as the team achieves better flow
The change from 2 to 3 was mostly to show that it can change. In this case to accomadate a higher variability.
do you mind I translate this?
I’d like to share this picture with my fellow developers
Sure, feel free to translate it.
A translation to Brazilian Portuguese:
LOL, the truth hurts.
I can’t work out if you’re for or against.
To be for or against Kanban would be as silly as being for or against staplers. It’s all about context.
Thanks for the presentation, it a great one !!! But it has left me confused on one point. I know Agile and I know scrum but Kanban is new to me. I dont understand when the presentation says Scrum team Kanban 1 and then says Kanban team 2 and kanban team 3 on slide no 10. Can some one please tell me wether scrum team are different than Kanban? Id yes whats the difference.
If Team 1 calls themselves a Kanban team and Team 2 calls themselves a Scrum team, the only thing we know for sure is that they have different names. Other than that, the teams can be very similar or very different. I suggest you read the “Kanban vs Scrum” article, it should clarify things. http://www.crisp.se/henrik.kniberg/Kanban-vs-Scrum.pdf
The slides you saw are mostly just pictures, with little or no explanation.
Have some of the slides disappeared? The Portuguese translation seems to have a few additional ones.
Oops, thanks for pointing that out! Looks I slipped on the keys when I added the link to the translations. Now the comic is complete again!
This is great stuff. You’ve explained this as lucidly as one could get. Do you mind if I share this comic with my fellow developers?
Feel free to use the comic as you like.
This really reminds me of a fast food restaurant. That’s a good thing. Deployment is king because in-progress or completed food that’s not deployed is going stale and the customers are going hungry. No point taking more orders or preparing more food if the orders aren’t being completed. The prime focus has to be deployment and staff get moved down-stream to relieve the blockage and balance the system.
Good metaphor there!
What a grap, no beef, no point, again new buzz word for obvious well known old stuff
I wish you were right. I’ll sure celebrate the day this becomes “obvious well known old stuff” :o)
Here a french translation http://www.openagile.net/2009/10/07/un-jour-au-pays-de-kanban/
With my Tux
Good work, added a link to your version above! Yours is prettier than mine :o)
Thanks for the link and your comment about my design :).
If others are interested I can give my images in SVG (inkscape) format.
German version is up, thanks Arne Roock!
While introducing kanban, I showed this to them. They got the idea very quickly and enjoyed it. Thank you for great work
(I’m one of the Korean translators of your Scrum and XP Book)
Thanks for your feedback, glad the comic was useful to you! And good work with the translation.
I have also a demonstration of Kanban coming and these I was planning to show as well. I’ve worked with Scrum and Kanban now for a year and eventually starting to get the big picture Your work has both helped and inspired me a lot and for that I salute you sir. Tack så mycket.
Great!! Innovative idea of describing Kanban.
As usual, great material
Always gets the point of Kanban across..
In a recent presentation explaining CFD I used this alongside hour-by-hour CFDs showing whats going on. Available on http://www.slideshare.net/yyeret/explaining-cumulative-flow-diagrams-cfd
Feel free to reuse!
Awesome slides! Thanks for sharing back.
Bastante bueno el comic. Gracias por ponerlo, así uno conoce más sobre Kanban.
This is great, of course, AND this is how I have always coached people to do Scrum. Work on one story at a time (max two) and the whole team work on outstanding tasks for that story until the story is complete. I can’t imagine why anyone would do otherwise. It would result in a loss of focus and a task-switching overhead.
In a Scrum sprint, would you be OK with not having a sprint plan, and instead having the PO add stories to the sprint on a just-in-time basis? That particular aspect is otherwise what I consider to be non-Scrum. Scrum, as I’ve understood it, prescribes that the team should commit to a fixed number of stories for a sprint, and not allow the PO (or anyone else) to change this during the sprint.
Appreciate it that you came up with the 2nd part of your squeezed links. I’ve seen One day in Kanban Land and its great.
Thanks a lot for sharing the article on google. That’s a awesome article. I enjoyed the article a lot while reading. Thanks for sharing such a wonderful article.
2 year on and this graphic still does the wonders. Absolutely terrific. Nothings more clear
Thanks for sharing! I’ve added a link to the Persion/Farsi version on the translations list above.
Thnaks Henrik, your comic is great to explain Kanban to others!
Just note that the link to the french translation is broken …
Thanks for notifying me! The French link is fixed now.
Very powerful!! Thanks for that!
[...] Kanban-Board | Quelle: Henrik Kniberg [...]
[...] A visual representation of Kanban in action for software projects: http://blog.crisp.se/2009/06/26/henrikkniberg/1246053060000 [...]
Can I use this comic to explain the concept elsewhere … Pls let me know
Yes, feel free to use it. Just leave a reference to the original version, thanks.
Great stuff !!!, Looking forward for more pictures.
[...] Pour découvrir simplement le Kanban, je vous conseille la lecture de la BD d’Henrik Kniberg “One day in Kanban land“. [...]
Turkish version : http://www.kodcu.com/2012/08/kanban-ile-bir-gun-nasil-gecer/
[...] blog.crisp.se via Joachim on [...]
Thank you for awesome information!
I translate Korean version: http://wp.me/p2Lc1y-3R
Thanks for translating! I added a link to your translation above.
Nice pictures to explain Kanban, thank you! If you want to show what happens to flow with various work in progress limits and the (usual reaction) effect of putting more people in one ‘step’, we build a small simulator: http://zilverline.github.com/flowmulator/public/index.html and a blog describing why we build it: blog.zilverline.com/2012/09/21/flowmulator-a-kanban-flow-simulator/
Last slide was funniest when KANBAN limit exceeds to 3… LOL!
[...] second layer of my Agile Onion is Kanban. Kanban is the prevailing change method in the Agile world. It has a wide range of use, from a [...]
[...] Pour découvrir simplement le Kanban, je vous conseille la lecture de la BD d’Henrik Kniberg »One day in Kanban land« . [...]
[...] вышеупомянутых авторов есть замечательные слайды «One day in Kanban land«. Они наглядно показывают, какие решения каждый [...]
Put some keywords dude, Its really hard to find this post trough google search engine
I’ve just published Japanese edition here. http://lean-trenches.com/one-day-in-kanban-land/
Thanks! Great job! I added a link to your translation above.
[…] Schöner Comic, der das Kanban Prinzip in der IT erklärt: http://blog.crisp.se/2009/06/26/henrikkniberg/1246053060000 […]
Should one move stickies backwards on a kanban board?
I believe you have to understand or find the answer on “why it should go back!”. Is it because of a customer requirement? is it because something blocks it? Strictly speaking if you have WIPs in place and you get a blocking card, it may create a huge…
First off, the cartoon is really meant to illustrate a high level interpretation of the Kanban objectives.
This cartoon is pretty typical of the early development effort of many teams. Though I see only minor problems, I think there is a great opportunity for deploying best practices.
1. The development team hadn’t agreed on development standards. As a result, someone broke the build.
2. Increasing the development Work-in-Process (WIP) limit from 2 t o3 (see last box)…
a. Hides problems or constraints in the process, in this case a broken build or deployment process. The Team (capital T) has the impression that work gets done since after all more stories are being developed, but no value is being delivered since that only happens when a story is deployed.
b. Adds little value early on at least because the Team (capital T) can’t even consume the first story or unit of work.
c. However, it is reasonable to increase the WIP limit once the Team (capital T) can demonstrate that it is able to consume the
3. Everyone rushing to offer help increases disruptions and puts additional pressure on the team when those involve know what needs to be done
1. Implement a Sprint 0 so that the Team (capital T) can iron out bugs in the end-to-end process.
2. Implement development standards to reduce the possibility of new checked in code breaking the build.
3. Implement ‘Continuous Integration’ to identify immediately when a unit of code breaks the build process.
4. Implement an automated ‘Smoke Testing’ or ‘Regression Testing’ process to make sure that the none of the existing functionality is broken in the latest build. After all, why deploy a new build that takes a step backward in quality and functionality delivered?
5. The Team (capital T), but usually the ScrumMaster in Agile, could have better communicated its problems and delays, in particular to the Product Owner (red figure) to better manage expectations
Wow, very useful insights and ideas, thanks for sharing!
[…] a situation arises, the priority is to clear current work-in-process, and team members will “swarm” to help those working on the activity that’s blocking […]
Your email address will not be published. Required fields are marked *
You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>