Kanban method in four easy steps. Enjoy kanban.
Kanban in 4 easy steps is one of the most popular Kanban presentations. Learn how to successfully implement Kanban in your business process or life. Get to know basic Kanban principles and to see how easily you can improve your productivity using Kanban boards.
Kanban is the simplest approach which is currently used in software development. Since Kanban prescribes close to nothing there are often a lot of basic questions about the method.
The presentation depicts what Kanban is generally using Scrum as a reference point. Then it presents a series of situations to answer basic questions about working with Kanban
In this presentation, Roni explains the basics of Kanban and the principles governing the application of Kanban for process improvement. We also look at a comparison between Scrum and Kanban and visit the basic differences between them.
It includes pointers telling what’s wrong with the current system, history of Kanban, introduction to Kanban, benefits of using Kanban, practices used in Kanban, principles of Kanban, how is Scrum different from Kanban. The tutorial begins with details about the current system and what’s wrong with it. It includes pointers like burnout, low throughput, unidentified bottlenecks, too much work which tell what’s wrong with the current system.
Followed by is a section about the history of Kanban which includes points like how the name originated, who discovered it, design, visual signals, based on which system. Resulting in an introduction section which talks about Kanban, what method it uses, scheduling system, what it consists of, amount of work, identification etc. Next comes the benefits section which includes the benefits of using Kanban like helps in visualizing the system, allows to evaluate, identify bottlenecks, establish trust in process etc.
Afterwards there is a section about Kanban practices. It includes practices used in Kanban like visualize, limit WIP in each phase of development, managing flow by keeping it under monitor, make policies explicit, improve collaboratively through the use of scientific models and some terms like lead time, cycle time, throughput etc. Moreover, it also includes the board for easy visualization, story card for keeping track, charts for measurement, control charts to measure average time taken for each task, cumulative flow diagrams showing relative amount of work.
Then comes the principles of Kanban. It includes principles which should be used in Kanban like agree to pursue incremental, evolutionary change, optimize what already exists, respect the current process, roles, responsibilities, leadership at all levels to empower the workforce to bring about change. The last section of this tutorial is Scrum vs Kanban. It explains how scrum is different from Kanban by giving pointers like Scrum prescribes roles, time boxed iterations, backlog items must fit, limit WIP in a different way. It also includes pointers giving reason why it shouldn’t matter because emphasis should be on the goal and not the tool.
Updated version at https://www.slideshare.net/GiulioRoggero/kanban-board-82363781
Do you have a team that works on both project and maintenance? Do you need to organize your team activities? Do you have a lot of activities in parallel and the time to market it's a problem? With a Kanban board and an Agile approach you can solve your problems!
Take a look of the animation of the slides to discover how it works.
Presentation jag höll på DevLin 2011 om hur det är att gå över från att utveckla objekt- (klass)orienterat till att utveckla i funktionella språk exemplifierat med erlang.
Kanban method in four easy steps. Enjoy kanban.
Kanban in 4 easy steps is one of the most popular Kanban presentations. Learn how to successfully implement Kanban in your business process or life. Get to know basic Kanban principles and to see how easily you can improve your productivity using Kanban boards.
Kanban is the simplest approach which is currently used in software development. Since Kanban prescribes close to nothing there are often a lot of basic questions about the method.
The presentation depicts what Kanban is generally using Scrum as a reference point. Then it presents a series of situations to answer basic questions about working with Kanban
In this presentation, Roni explains the basics of Kanban and the principles governing the application of Kanban for process improvement. We also look at a comparison between Scrum and Kanban and visit the basic differences between them.
It includes pointers telling what’s wrong with the current system, history of Kanban, introduction to Kanban, benefits of using Kanban, practices used in Kanban, principles of Kanban, how is Scrum different from Kanban. The tutorial begins with details about the current system and what’s wrong with it. It includes pointers like burnout, low throughput, unidentified bottlenecks, too much work which tell what’s wrong with the current system.
Followed by is a section about the history of Kanban which includes points like how the name originated, who discovered it, design, visual signals, based on which system. Resulting in an introduction section which talks about Kanban, what method it uses, scheduling system, what it consists of, amount of work, identification etc. Next comes the benefits section which includes the benefits of using Kanban like helps in visualizing the system, allows to evaluate, identify bottlenecks, establish trust in process etc.
Afterwards there is a section about Kanban practices. It includes practices used in Kanban like visualize, limit WIP in each phase of development, managing flow by keeping it under monitor, make policies explicit, improve collaboratively through the use of scientific models and some terms like lead time, cycle time, throughput etc. Moreover, it also includes the board for easy visualization, story card for keeping track, charts for measurement, control charts to measure average time taken for each task, cumulative flow diagrams showing relative amount of work.
Then comes the principles of Kanban. It includes principles which should be used in Kanban like agree to pursue incremental, evolutionary change, optimize what already exists, respect the current process, roles, responsibilities, leadership at all levels to empower the workforce to bring about change. The last section of this tutorial is Scrum vs Kanban. It explains how scrum is different from Kanban by giving pointers like Scrum prescribes roles, time boxed iterations, backlog items must fit, limit WIP in a different way. It also includes pointers giving reason why it shouldn’t matter because emphasis should be on the goal and not the tool.
Updated version at https://www.slideshare.net/GiulioRoggero/kanban-board-82363781
Do you have a team that works on both project and maintenance? Do you need to organize your team activities? Do you have a lot of activities in parallel and the time to market it's a problem? With a Kanban board and an Agile approach you can solve your problems!
Take a look of the animation of the slides to discover how it works.
Presentation jag höll på DevLin 2011 om hur det är att gå över från att utveckla objekt- (klass)orienterat till att utveckla i funktionella språk exemplifierat med erlang.
3. Ett litet supportteam… 10 system ger många oplanerade utryckningar SLA som kräver snabb hantering.
4.
5.
6.
7.
8.
9.
Editor's Notes
En beskrivning av hur vi började med Scrum men kompleterade med Kanban för att hantera strömmen av produktionsärenden. Vi kör båda två parallellt, för samma team. Hur vi gjort och vad som funkat och inte funkat.