Kanban for DevOps
•
6 likes•3,979 views
In this talk from the Triangle DevOps meetup, Cory Foy gives an overview of Kanban and how you can implement it on your team
Recommended
More Related Content
Viewers also liked
Viewers also liked (10)
Similar to Kanban for DevOps
Similar to Kanban for DevOps (20)
More from Cory Foy
More from Cory Foy (20)
Recently uploaded
Recently uploaded (20)
Kanban for DevOps
- 1. Kanban for DevOps Cory Foy |@cory_foy | foyc@coryfoy.com Wednesday, July 16, 14
- 3. Dev Ops Deliver! Keep it Stable! Wednesday, July 16, 14
- 5. What approaches have we tried? http://blog.siteground.com/siteground-staging/ Wednesday, July 16, 14
- 6. Wednesday, July 16, 14
- 7. Sprint Planning Product Backlog In Sprint? Daily Standup Do Work Sprint Demo Retrospective Done? Ship and Party! Yes No Yes No Repeat Daily Scrum Product Backlog Wednesday, July 16, 14
- 9. Wednesday, July 16, 14
- 10. Wednesday, July 16, 14
- 11. Wednesday, July 16, 14
- 12. Kanban Wednesday, July 16, 14
- 13. Card Wednesday, July 16, 14
- 14. Wednesday, July 16, 14
- 15. Lean Wednesday, July 16, 14
- 16. Lean Continuous Process Flow Use Pull Systems to Avoid Overproduction Level Out the Workflow Stop to Fix Problems Use Standardized Tasks and Processes UseVisual Controls Become a Learning Organization (hansei / kaizen) Wednesday, July 16, 14
- 17. Lean Continuous Process Flow Use Pull Systems to Avoid Overproduction Level Out the Workflow Stop to Fix Problems Use Standardized Tasks and Processes UseVisual Controls Become a Learning Organization (hansei / kaizen) - Provide customers what they want, when they want it, in the amount they want Wednesday, July 16, 14
- 18. Lean Continuous Process Flow Use Pull Systems to Avoid Overproduction Level Out the Workflow Stop to Fix Problems Use Standardized Tasks and Processes UseVisual Controls Become a Learning Organization (hansei / kaizen) - Bring Problems to the Surface - Reduce to zero the amount of time work is idle Wednesday, July 16, 14
- 19. Lean Continuous Process Flow Use Pull Systems to Avoid Overproduction Level Out the Workflow Stop to Fix Problems Use Standardized Tasks and Processes UseVisual Controls Become a Learning Organization (hansei / kaizen) - Unevenness causes waste in forecast, planning and production, so work towards smooth work Wednesday, July 16, 14
- 20. Lean Continuous Process Flow Use Pull Systems to Avoid Overproduction Level Out the Workflow Stop to Fix Problems Use Standardized Tasks and Processes UseVisual Controls Become a Learning Organization (hansei / kaizen) - Build into the system the capability of detecting problems - Control of Error Wednesday, July 16, 14
- 21. Lean Continuous Process Flow Use Pull Systems to Avoid Overproduction Level Out the Workflow Stop to Fix Problems Use Standardized Tasks and Processes UseVisual Controls Become a Learning Organization (hansei / kaizen) - Use simple visual indicators to know if in standard condition or deviation - Reports should be one page, even financial reports Wednesday, July 16, 14
- 22. Lean Continuous Process Flow Use Pull Systems to Avoid Overproduction Level Out the Workflow Stop to Fix Problems Use Standardized Tasks and Processes UseVisual Controls Become a Learning Organization (hansei / kaizen) - Use stable, repeatable methods - Capture the current method, learn from it, then capture the new method Wednesday, July 16, 14
- 23. Lean Continuous Process Flow Use Pull Systems to Avoid Overproduction Level Out the Workflow Stop to Fix Problems Use Standardized Tasks and Processes UseVisual Controls Become a Learning Organization (hansei / kaizen) - Hansei - Relentless Reflection - Kaizen - Continuous Improvement Wednesday, July 16, 14
- 24. Lean Eliminate Waste Amplify Learning Decide as Late as Possible Deliver as Fast as Possible Empower the Team Build Integrity In See the Whole Wednesday, July 16, 14
- 25. Lean Eliminate Waste Amplify Learning Decide as Late as Possible Deliver as Fast as Possible Empower the Team Build Integrity In See the Whole - Waste are things not directly tied with bringing value to a customer -Value is something someone would pay for - Queues, Delays, Rework Wednesday, July 16, 14
- 26. Lean Eliminate Waste Amplify Learning Decide as Late as Possible Deliver as Fast as Possible Empower the Team Build Integrity In See the Whole - Every solution we create is unique - Our product is about what is used, rather than how well it met the requirements - Feedback is critical Wednesday, July 16, 14
- 27. Lean Eliminate Waste Amplify Learning Decide as Late as Possible Deliver as Fast as Possible Empower the Team Build Integrity In See the Whole - We decide Schedule, Scope, Cost at the beginning of a project - Don’t make critical decisions when you know the least! Wednesday, July 16, 14
- 28. Lean Eliminate Waste Amplify Learning Decide as Late as Possible Deliver as Fast as Possible Empower the Team Build Integrity In See the Whole - The longer work is in progress, the more time it has to collect bugs - Once you’ve decided a feature is necessary, deliver it! - Unrealized features are inventory Wednesday, July 16, 14
- 29. Lean Eliminate Waste Amplify Learning Decide as Late as Possible Deliver as Fast as Possible Empower the Team Build Integrity In See the Whole - Most people want to do the best job they can - Let them help set and understand policies Wednesday, July 16, 14
- 30. Lean Eliminate Waste Amplify Learning Decide as Late as Possible Deliver as Fast as Possible Empower the Team Build Integrity In See the Whole - Perceived vs Conceptual Integrity - Focus on Quality from the beginning Wednesday, July 16, 14
- 31. Lean Eliminate Waste Amplify Learning Decide as Late as Possible Deliver as Fast as Possible Empower the Team Build Integrity In See the Whole - Root Cause Analysis - Retrospectives -Visualization Systems Thinking- Wednesday, July 16, 14
- 32. Getting Started Wednesday, July 16, 14
- 33. Determine the Types of Work Wednesday, July 16, 14
- 34. Determine the Types of Work By Priority By Type Expedite Fixed Date Standard Intangible Server Move Code Deploy Network Performance Investigation Outage Wednesday, July 16, 14
- 35. Visualize your Workflow Wednesday, July 16, 14
- 36. Wednesday, July 16, 14
- 37. Wednesday, July 16, 14
- 38. Set Explicit Policies Wednesday, July 16, 14
- 39. Wednesday, July 16, 14
- 40. Make All WorkVisible Wednesday, July 16, 14
- 41. Wednesday, July 16, 14
- 42. Measure Cycle Time Wednesday, July 16, 14
- 43. Wednesday, July 16, 14
- 44. Wednesday, July 16, 14
- 45. Limit WIP As Necessary Wednesday, July 16, 14
- 46. Wednesday, July 16, 14
- 47. Wednesday, July 16, 14
- 48. Wednesday, July 16, 14
- 49. Don’t Forget Cadences Wednesday, July 16, 14
- 50. Wednesday, July 16, 14
- 51. Use Models to Recognize Improvement Opportunities Wednesday, July 16, 14
- 52. Muda (Waste) Wednesday, July 16, 14
- 53. Comparing to Scrum Wednesday, July 16, 14
- 54. Recreating Scrum with Kanban http://blog.coryfoy.com/2011/07/recreating-scrum-using-kanban-and-explicit-policies/ 2 Week Sprint Sprint Planning Sprint Demo Retros (2 Weeks) (2 Weeks) (2 Weeks) 2 Weeks! 2 Weeks! 2 Weeks! 1 Week! On Demand! Velocity Wednesday, July 16, 14