![Outline ,[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Empfohlen
Weitere ähnliche Inhalte
Andere mochten auch
Andere mochten auch (12)
Ähnlich wie Kanban At Roots 2011
Ähnlich wie Kanban At Roots 2011 (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Kanban At Roots 2011
- 1. Roots Conference Bergen Wednesday 25.05.2011 Arild Strømhylden – Ketil Jensen Kanban Game
- 3. About us @stromhylden @ketilj
- 4. Show of Hands - How many have heard about Kanban? - How many uses it or have used it?
- 6. The “Father” of TPS and Kanban
- 7. Kanban in Software Development 2004…..2006….2007….2008….2009….2010 David Anderson introduced Kanban at XIT Microsoft Kanban introduced at Corbis for team with +50 people Several sessions about Kanban at Agile 2008
- 8. Kan Ban – Visual Card
- 9. Visualizing the Workflow And Limiting WIP Creates a Pull System For Just In Time Work
- 10. Kanban is About Flow and Sustainable Pace
- 13. 3. Tracking
- 14. Cumulative Flow Diagram http://open.bekk.no/2009/11/03/cumulative-flow-diagrams-with-google-spreadsheets
- 15. Control chart
- 16. Let’s play the getKanban game!
- 22. Cost of Delay for Classes of Service
- 24. Go Live Often
- 27. Little’s law Wq is the average time in the queue for a standard job Lq is the average number of things in the queue to be processed The denominator (Lambda) is the average processing rate for jobs in the queue http://scalingsoftwareagility.wordpress.com/2009/12/14
- 28. Little’s law for a sub system http://scalingsoftwareagility.wordpress.com/2009/12/14 Backlog = 100 stories Iteration length = 2 weeks Velocity = 8 stories per sprint = 12.5 iterations or 25 weeks to get into the sprint + 2 weeks to finsish = 27 weeks
- 29. Little’s law for a system http://scalingsoftwareagility.wordpress.com/2009/12/14 Number of projects = 50 Velocity = 10 projects per year 50 projects / 10 projects per year = 5 years per project (in average)
- 30. Process Control Chart David J. Anderson – Kanban Traning Class material
- 32. References - David J. Anderson – Kanban Traning Class material - Aslak Hellsøy - http://open.bekk.no/2009/11/03/cumulative-flow-diagrams-with-google-spreadsheets - http://scalingsoftwareagility.wordpress.com/2009/12/14 - Silver Stripe Blog – http//toolsforagile/blog/archives/647
- 33. Thank you!
Hinweis der Redaktion
- Hi, My name is Ketil Jensen and I work as a consultant for a company called Miles. I’m primarily a developer but have a really strong interest in processes and methodologies I’m here today to share some of the experiences we’ve had since we started using Kanban in the autumn 2009 at one of our clients NetCom, which is the second largest Telecom operator in Norway. The experiences is seasoned with some of my own opinions about how a good software development process should look like.
- “ The goal isn’t to continue working, the goal is to continue flowing”
- A means to classify work to provide acceptable levels of customer satisfaction
- But remember: Be patient. Apply changes in small steps Because………(pause) First and foremost: Kanban is a tool for change management. Do a change Let the system stabilize Observe the result And repeat
- But remember: Be patient. Apply changes in small steps Because………(pause) First and foremost: Kanban is a tool for change management. Do a change Let the system stabilize Observe the result And repeat
- But remember: Be patient. Apply changes in small steps Because………(pause) First and foremost: Kanban is a tool for change management. Do a change Let the system stabilize Observe the result And repeat
- But remember: Be patient. Apply changes in small steps Because………(pause) First and foremost: Kanban is a tool for change management. Do a change Let the system stabilize Observe the result And repeat
- But remember: Be patient. Apply changes in small steps Because………(pause) First and foremost: Kanban is a tool for change management. Do a change Let the system stabilize Observe the result And repeat
- But remember: Be patient. Apply changes in small steps Because………(pause) First and foremost: Kanban is a tool for change management. Do a change Let the system stabilize Observe the result And repeat
- But remember: Be patient. Apply changes in small steps Because………(pause) First and foremost: Kanban is a tool for change management. Do a change Let the system stabilize Observe the result And repeat
- But remember: Be patient. Apply changes in small steps Because………(pause) First and foremost: Kanban is a tool for change management. Do a change Let the system stabilize Observe the result And repeat
- But remember: Be patient. Apply changes in small steps Because………(pause) First and foremost: Kanban is a tool for change management. Do a change Let the system stabilize Observe the result And repeat
- But remember: Be patient. Apply changes in small steps Because………(pause) First and foremost: Kanban is a tool for change management. Do a change Let the system stabilize Observe the result And repeat
- But remember: Be patient. Apply changes in small steps Because………(pause) First and foremost: Kanban is a tool for change management. Do a change Let the system stabilize Observe the result And repeat
- But remember: Be patient. Apply changes in small steps Because………(pause) First and foremost: Kanban is a tool for change management. Do a change Let the system stabilize Observe the result And repeat
- But remember: Be patient. Apply changes in small steps Because………(pause) First and foremost: Kanban is a tool for change management. Do a change Let the system stabilize Observe the result And repeat
- But remember: Be patient. Apply changes in small steps Because………(pause) First and foremost: Kanban is a tool for change management. Do a change Let the system stabilize Observe the result And repeat