Deming to Devops

Putting the Science Back in Computer Science: From Deming

and Goldratt to Devops

@botchagalupe

Friday, September 28, 12

The History of Science Behind Devops

• The Three Ways of Devops• Deming’s 14 Points• My 7 Takeaways

itrevolution.com


The Three Ways of Devops

dev2ops.orgFriday, September 28, 12

Deming’s 14 Points

1. Create a constant purpose toward improvement.2. Adopt the new philosophy. 3. Stop depending on inspections. 4. Use a single supplier for any one item. 5. Improve constantly and forever.6. Use training on the job.7. Implement leadership.8. Eliminate fear.9. Break down barriers between departments.10. Get rid of unclear slogans.11. Eliminate management by objectives.12. Remove barriers to pride of workmanship.13. Implement education and self-improvement.14. Make "transformation" everyone's job.


My Seven Takeaways

1. Always be looking for a better truth. 2. A system is the sum of its human parts.3. Complexity is the enemy.4. Variation is the enemy.5. Make policies explicit.6. Learn two new words (Kaizen and Kata).7. Make people before making a service.


Why Are We Here?

W. Edwards Deming14 Points - #1

"Create constancy of purpose toward improvement of product and

service, with the aim to become competitive, stay in business and to

provide jobs."


Werner Karl Heisenberg (1901 – 1976)

• Father of Quantum Mechanics• Won Nobel Prize for Physics • Uncertainty Principle• Opened Pandoras Box


http://en.wikipedia.org/wiki/Nobel_Prize_for_Physics

http://en.wikipedia.org/wiki/Nobel_Prize_for_Physics

The Father of Scientific Management


http://en.wikipedia.org/wiki/Scientific_management

http://en.wikipedia.org/wiki/Scientific_management

“The Parable of a Frog”


Takeaway #1Always be looking for a better truth.

"Adopt the new philosophy. We are in a new economic age. Western management must awaken to the

challenge, must learn their responsibilities, and take on

leadership for change."



Neo Taylorism

A Japanese Commentary on Taylor

“We will win, and you will lose. You cannot do anything about it because your failure is an internal disease. Your companies are based on Taylor’s principles. Worse, your heads are Taylorized, too.”

Konosuke Matsushita Founder, Matsushita Electronics 1988


The Devops First Way: Systems Thinking


W. Edwards Deming (1900 – 1993)

• Father of Quality• Understanding of the system• Understanding human behavior• Understanding variation • WWII success credited to his quality approach• Taught Japan after WWII and transformed quality• In 1980 Transformed American quality revolution• The Foundations of Six Sigma


System of Profound Knowledge


Taiichi Ohno (1912 – 1990)

• Father of Lean • Toyota Production System (TPS) • Just in Time (JIT) & Pull• Inventor of Kanban• Eliminate Waste• 5 Whys method as "the basis of Toyota's scientific approach


Takeaway #2 A system is the sum of its human parts

"Break down barriers between departments. People in research,

design, sales, and production must work as a team, in order to foresee problems of production and usage that may be encountered with the

product or service."W. Edwards Deming14 Points - #9


Eliyahu M. Goldratt (1947 – 2011)

• Father of Theory of Constraints• Published the Goal in 1984• Drum-Buffer-Rope• Like Deming he was a Physicist • Five Focusing Steps for Managing• Global vs Local Optimization • Inherent Simplicity • Current & Future Reality Tree


Inherent Simplicity


Current Reality Tree


Takeaway #3Complexity is the Enemy

"Cease dependence on inspection to achieve quality. Eliminate the need for massive inspection by

building quality into the product in the first place."



The Devops Second Way: Feedback Loops


Walter A. Shewhart (1891 – 1967)

• Father of statistical quality control• Creator of Control Chart/Shewhart chart• Creator of PDSA/PDCA• Chance and Assignable Variation • Another Physics guy• Worked for Bell Labs• “Statistical Method from the Viewpoint of Quality Control”- 1939


http://en.wikipedia.org/wiki/Statistical_quality_control

http://en.wikipedia.org/wiki/Statistical_quality_control

Control Chart


Takeaway #4Variation is the Enemy

"Improve constantly and forever the system of production and service,

to improve quality and productivity, and thus constantly decrease

costs."



Shigeo Shingo (1909 – 1990)

• Co-father of Lean • Toyota Production System (TPS) • Poka-yoke (mistake-proofing)• Jidoka• Single-Minute Exchange of Die (SMED)• Standardized work & Kaizen (Continuous improvement)• Shingo Prize that recognizes world-class, lean organizations and operational excellence.


http://en.wikipedia.org/wiki/Poka-yoke

http://en.wikipedia.org/wiki/Poka-yoke

http://en.wikipedia.org/wiki/Single-Minute_Exchange_of_Die

http://en.wikipedia.org/wiki/Single-Minute_Exchange_of_Die

http://en.wikipedia.org/wiki/Shingo_Prize

http://en.wikipedia.org/wiki/Shingo_Prize

http://en.wikipedia.org/wiki/Operational_excellence




Andon Cord


Kanban for Software


Takeaway #5Make Policies Explicit

"Institute a vigorous program of education and self-improvement."



The Devops Third Way: Continuous Learning


Kata


(TWI) - Training Within Industry

learn-by-doing


Takeaway #6Learn two new words (Kaizen and Kata)

"Use training on the job. "



33

Customer Development Model

Lean Startup Thread


Tora! Tora! Tora!


Final Takeaway #7Make People Before Making Services

"The aim of supervision should be to help people and machines and

gadgets do a better job. "



Don’t Be a Frog Dude

1. Read Deming’s2. Read Goldratt’s3. Read Kim 4. Join the Tribe - ITRevolution.com


Documents

Deming to Devops