Mike Orzen joined with the DevOps Agile Skills Association to present his expertise on the value of Lean IT and DevOps when combined. Learn more about DASA DevOps here: http://www.godasa.org
1. DASA
Is an independent and open association supporting the development of
high-performance IT Professionals and Teams through agile DevOps
initiatives.
DASA offers thought leadership as well as practical guidance for
competence development for professionals and organizations.
3. About the DevOps Agile Skills Association (DASA)
DASA is an independent and open,
members driven association supporting the
development of DevOps training and
certification to the global market.
Advocating the development of high-
Performance IT Professionals and Teams
through agile DevOps initiatives.
5. Poll #1: How would you Describe the Status of
your Lean IT/DevOps Journey?
A. Considering it
B. Actively planning
C. Have started
D. 2 years or more into it
E. 5 years or more into it
6. Poll #2: Are you Actively Blending Lean IT
Practices with your DevOps Transformation?
A. Yes, but not intentionally
B. Yes, intentionally
C. No, but not intentionally
D. No, intentionally
7. Poll #3: How Long Have you Been on your
Lean It and/or DevOps Journey?
A. Not started
B. Less than a year
C. 1-3 years
D. 4-7 years
E. 8 years or longer
11. Applying Lean in IT Is Relatively New
1900 2000
Henry
Ford
Conveyor
Line/
Process
Flow
Taylor,
Gilbreth
Scientific
Management
Deming
Visits
Japan
Taiichi
Ohno
-‐
Birth
of
Toyota
Production
System
Shewart
at
Bell
Labs
Statistical
Analysis/
Process
Control
Total
Quality
Management
Six
Sigma
Motorola,
Allied
Signal,
GE
“The
Machine
That
Changed
the
World”
published
“Lean
Thinking”
published
Lean
Six
Sigma
Theory
of
Constraints
Training
Within
Industry
Juran
Visits
Japan
Feigenbaum
publishes
“Quality
Control
Principles” Shingo
Prize
created
Age
of
Scientific
Management
Age
of
Engagement
Age
of
Integration
Lean
Office,
Supply
Chain,
Health
Care,
Service
Industries
and
beyond
“Reengineering
the
Corporation”
published
1950
Agile
Manifesto
mid-‐1500s
,
continuous
flow
production
of
warships
–
Venice
1793,
interchangeable
parts
to
cotton
gin
-‐
Eli
Whitney
Agile
Manifesto
“Lean IT”
published
Lean Mfg.
DevOps
12. Lean IT
3 essential components to IMPROVE FLOW:
– Engaging People
– Improving Processes
•Eliminating Waste: Non-value Added Work,
Variation & Overburden
•Applying Methodical Problem Solving
– Leveraging Technology
13. Lean IT
Ø Understand customer-defined value to know quality and waste
Ø Make structured problem solving the foundation of your
transformation
Ø Front-load the development process to test options early
Ø Create a level process flow
Ø Standardize to reduce variation and drive predictable outcomes
16. Agile
Ø Run the business and IT as one team (value streams)
Ø Self-organizing autonomous teams (respect for people)
Ø Breakdown the work iteratively for rapid feedback and course
correction (check/adjust)
Ø Break the work into smaller pieces (flow)
Ø Apply kanban (pull)
Ø Test code as part of development process (quality at the source)
20. DevOps
Ø Create a culture of trust, respect, and accountability (respect
for people)
Ø Take customer-centric action (voice of the customer)
Ø End-to-End responsibility DevSecOps (value streams)
Ø Automate everything you can (accelerate flow)
Ø Amplify feedback Loops (check/adjust)
Ø Continuous integration and deployment (flow)