why pipelines matter

36
Why Pipelines Matter Michael Ducy Chef Software

Upload: michael-ducy

Post on 21-Jan-2018

365 views

Category:

Technology


0 download

TRANSCRIPT

Page 1: Why Pipelines Matter

Why Pipelines MatterMichael Ducy

Chef Software

Page 2: Why Pipelines Matter

Some Foundations of DevOps

Page 3: Why Pipelines Matter

Three Ways

• Systems Thinking

• Amplify Feedback Loops

• Continuous Learning and Improvement

Page 4: Why Pipelines Matter

Systems Thinking

• Avoid Local Optimization

• Understand Impact to up or downstream actors

Page 5: Why Pipelines Matter

Amplify Feedback

• Required for • Improvement

• Quality Control

• Removal of Waste

Page 6: Why Pipelines Matter

Continuous Learning & Improvement

• Improvement is never “Done”

• Practices and Processes Improve

• Improvement in one area requires improvement elsewhere

Page 7: Why Pipelines Matter

Flow

Page 8: Why Pipelines Matter

Flow

Page 9: Why Pipelines Matter

Flow

Page 10: Why Pipelines Matter

Flow

Page 11: Why Pipelines Matter

Flow

Page 12: Why Pipelines Matter

Flow

Page 13: Why Pipelines Matter

Flow

Page 14: Why Pipelines Matter

Flow

Page 15: Why Pipelines Matter

Flow

Page 16: Why Pipelines Matter

FlowBusiness

RequirementsCustomerDelivery

Page 17: Why Pipelines Matter

Flow

Business Requirements

CustomerDelivery

Page 18: Why Pipelines Matter

Lean IT

Page 19: Why Pipelines Matter

Removal of Waste

Page 20: Why Pipelines Matter

Lean

“If you were to release everyday, how much of your time would be spent on process?”

- Adrian Cockcroft

Page 21: Why Pipelines Matter

Lean - Muda1. 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

Page 22: Why Pipelines Matter

Visualization of Work

•Kanban – Visualize work to be done

•Value Streams – Visualize work as it is done

Page 23: Why Pipelines Matter

Kanban

http://leankit.com/blog/wp-content/uploads/2015/02/Screen-Shot-2015-06-17-at-4.13.00-PM-1024x510.png

Page 24: Why Pipelines Matter

Value Streams

Page 25: Why Pipelines Matter

Value Streams

OS App DB Security

Page 26: Why Pipelines Matter

Continuous Integration

Page 27: Why Pipelines Matter

Continuous Delivery

Page 28: Why Pipelines Matter

Built on Pipelines

Page 29: Why Pipelines Matter

Pipelines

•Systems Thinking

•Amplify Feedback

Page 30: Why Pipelines Matter

Optimizing a Pipeline

•Find Areas of waste

•Find Areas missing feedback loops

Page 31: Why Pipelines Matter

Value Stream Maps

Page 32: Why Pipelines Matter

Pipelines:

• Help us visualize our work

• Continuously Improve and Experiment

• Encourage Systems Thinking

• Amplifies Feedback

Page 33: Why Pipelines Matter

Everything is an Artifact

Page 34: Why Pipelines Matter

Everything can be a Pipeline

Page 35: Why Pipelines Matter

Everything gets the benefits

• Help us visualize our work

• Continuously Improve and Experiment

• Encourage Systems Thinking

• Amplifies Feedback

Page 36: Why Pipelines Matter

Everything is a Value Stream