Embed Size (px)
DESCRIPTION
An introduction to Kanban I presented with Flavius Stef at the Bucharest Agile Meetup Group in February 2014. See the event details on http://www.meetup.com/The-Bucharest-Agile-Software-Meetup-Group/events/146222892/. See http://mozaicworks.com for articles and events about Kanban and agile
Citation preview
Intro
Kanban
Evolutionary change through visualization,flow management and collaboration
Agenda
19:00 – Welcome & Talk: Intro to Kanban19:50 – Open Space Intro + market place20:00 – First Open Space slot20:30 – Second Open Space slot21:00 – Closing
Let's get to know each other
Us
Tokio Imperial Palace – East Garden
5 Business needs for Kanban
● Better organize work● Reduce release cycles● Reduce management overhead
(self-organization)● Complement and/or replace Scrum (eg. for
maintenance)● Improve quality
What is Kanban?
Change management tool with six properties– Visualize your workflow– Limit work in progress– Measure and manage flow– Make policies explicit– Implement feedback loops– Improve collaboratively, evolve experimentally
How to adopt Kanban?
What are your value streams?
Need ??? Cashing the €€€
Your value
stream(s)
Understand how you work(Value Stream Mapping)
Brainstormidea
Detailidea
Sketch UI Code Test Deploy
Visualize work to coordinate
Ideas Features UI design Code Test Deploy
Limit WIP to improve flow
Ideas Features (5) UI design (4) Code (2) Test (1) Deploy (5)
Focus on flow
Add support for Romanian
Started on: 20 JanFinished: 24 Jan 1 2 3 4 5 6 7 8 9 10 11
Cycle Time
Explicit policies
Ideas Features (5) UI design (4) Code (2) Test (1) Deploy (5)
RefactoredCode Review
Prioritize work
Ideas Features (5) UI design (4) Code (2) Test (1) Deploy (5)
Most important
Deliver often
Sep 2008 – Jan 2013
Meetings
● Daily Meeting● Release Planning● Queue Replenishment● Retrospectives● Demos
How to use Kanban for change?
Read the Board and Act
Read the Board and Act: Column Full
Ideas Features (5) UI design (4) Code (2) Test (3) Deploy (5)
√
Use Theory of Constraints (ToC) to deal with bottlenecks
Bottleneck
√
Read the Board and Act: Failure demand
Ideas Features (5) UI design (4) Code (2) Test (3) Deploy (5)
Improve quality: add/change practices, update explicit policies
Read the Board and Act: Useless Work
Ideas Features (5) UI design (4) Code (2) Test (3) Deploy (5)
Retrospective using VSM & change process accordingly
Other work
Doing DoneTo Do
Read charts and act: High Cycle time
Add support for Romanian
Started on: 20 JanFinished: 24 Jan 1 2 3 4 5 6 7 8 9 10 11
Cycle Time
Change process to improve flow
Why did this happen?
Periodic Retrospectives
● Pick an area to focus on● Tell the story of the last 1-2 weeks● Everyone writes on post-its what went well● Everyone writes on post-its what could be
improved● Discuss issues● Define actions until next retrospective● Plan them, add them on the board
Why Kanban?
● Minimally invasive – Start with what you have● Balance demand with capacity● Foster collaboration● Focus on improvements● Get stuff done sooner● Proven successful elsewhere
Picture credits
● http://www.flickr.com/photos/jaimeperez/2753098339/in/photostream/
● http://thenounproject.com/noun/scroll/#icon-No1629
● http://thenounproject.com/noun/scroll/#icon-No485
