Why Pipelines Matter
of 36
/36
-
Author
michael-ducy -
Category
Technology
-
view
350 -
download
0
Embed Size (px)
Transcript of Why Pipelines Matter
- 1. Why Pipelines Matter Michael Ducy Chef Software
- 2. Some Foundations of DevOps
- 3. Three Ways Systems Thinking Amplify Feedback Loops Continuous Learning and Improvement
- 4. Systems Thinking Avoid Local Optimization Understand Impact to up or downstream actors
- 5. Amplify Feedback Required for Improvement Quality Control Removal of Waste
- 6. Continuous Learning & Improvement Improvement is never Done Practices and Processes Improve Improvement in one area requires improvement elsewhere
- 7. Flow
- 8. Flow
- 9. Flow
- 10. Flow
- 11. Flow
- 12. Flow
- 13. Flow
- 14. Flow
- 15. Flow
- 16. Flow Business Requirements Customer Delivery
- 17. Flow Business Requirements Customer Delivery
- 18. Lean IT
- 19. Removal of Waste
- 20. Lean If you were to release everyday, how much of your time would be spent on process? - Adrian Cockcroft
- 21. Lean - Muda 1. Defects (Bad builds) 2. Overproduction of things not demanded by actual customers 3. Inventories awaiting further processing or consumption 4. Unnecessary over-processing (for example, relying on inspections rather than designing the process to eliminate problems) 5. Unnecessary motion of employees (meetings) 6. Unnecessary transport and handling of goods (Approvals) 7. Waiting for an upstream process to deliver, or for a machine to finish processing, or for a supporting function to be completed, or for an interrupted worker to get back to work... Muda - 7 types of waste - http://www.systems2win.com/LK/lean/7wastes.htm
- 22. Visualization of Work Kanban Visualize work to be done Value Streams Visualize work as it is done
- 23. Kanban http://leankit.com/blog/wp-content/uploads/2015/02/Screen-Shot-2015-06-17-at-4.13.00-PM-1024x510.png
- 24. Value Streams
- 25. Value Streams OS App DB Security
- 26. Continuous Integration
- 27. Continuous Delivery
- 28. Built on Pipelines
- 29. Pipelines Systems Thinking Amplify Feedback
- 30. Optimizing a Pipeline Find Areas of waste Find Areas missing feedback loops
- 31. Value Stream Maps
- 32. Pipelines: Help us visualize our work Continuously Improve and Experiment Encourage Systems Thinking Amplifies Feedback
- 33. Everything is an Artifact
- 34. Everything can be a Pipeline
- 35. Everything gets the benefits Help us visualize our work Continuously Improve and Experiment Encourage Systems Thinking Amplifies Feedback
- 36. Everything is a Value Stream