Devops Kaizen

1. Devops Kaizen
John Willis
@botchagalupe

2. https://github.com/botchagalupe/my-presentations

3. •Devops Capabilities Assessment
• Culture and Technology (Scorecard)
•Devops Retrospective
• Value Stream Map, Current Sate
• Devops Coach
• Improvement Kata,Target State
•Dojo Experimental Learning
• Continious Learning
Devops Kaizen Roadmap

4. Devops Capabilities
Assessment

5. •Benchmark Capabilities
• Identify Capabilities to Drive Improvement
•Drive Key Outcomes
• Track and Benchmark Outcomes
•Identify Capability Priorities
• Capabilities With Highest Impact
Devops Capabilities Assessment

6. •Technical practices
•Culture
•Feedback loops
•Management practices
Capabilities Categories

7. •Lead Time
•Deployment Frequency
•MTTR
•Change Succes Rate
•Overall IT Performance
•Deployment Pain
Sample Tracking Key Outcomes

8. Devops Retrospective

9. DevOps Retrospectives follows a repeatable process
Map end-to-end process1
Identify wastes, inefficiencies,
bottlenecks
2
Identify countermeasures3

10. Graphical Storytelling (with VSM notation)

11. Apply Lean Waste Analysis
Structured Waste
Identification
Free-form waste identification

12. Start with Structured Waste Classification
Inspired by Mary Poppendieck (original) and Jeff Anderson (adaptation)

13. Countermeasures
Countermeasures should
be:
● Actionable
● Preferably backlog
ready
● Preferably small
batches of work

14. Use the VSM to design Kanban Board. Use Kanban to track/manage daily work.

15. Devops Retrospective Flow
1.Key Outcomes
2.Countermeasures
3.Storyboard
4.Kanban Board
5.Post Retrospective
1
2
3
4
5

16. Devops Coach
(Kata)

17. I fear not the man who has
practiced 10,000 kicks
once, but I fear the man
who has practiced one
kick 10,000 times
- Bruce Lee

18. Toyota is not a story about
techniques. It’s an organization
defined primarily by the unique
behavior routines it continually
teaches to all it’s members.
Mike Rother (Page 262-263)

19. Devops Practices and Patterns
• Continuous Delivery
• Everything in version control
• Small batch principle
• Trunk based deployments
• Manage flow (WIP)
• Automate everything
• Culture
• Everyone is responsible
• Done means released
• Stop the line when it breaks
• Remove silos19
itrevolution.com/devops-handbook

20. 30x 200x
more frequent
deployments
faster lead
times
60x 168x
the change
success rate
faster mean time to
recover (MTTR)
2x 50%
more likely to
exceed profitability,
market share &
productivity goals
higher market
capitalization growth
over 3 years*
High performers compared to their peers…
Data from 2014/2015 State of DevOps Report - https://puppetlabs.com/2015-devops-report
Recent IT Performance Data is Compelling

21. Fast
CheapGood
“Pick Two!”
Conventional Wisdom

22. Generative Behavior
ResilienceSpeed
“Must Have All
Three!”
New Triangle

23. Devops Automated Deployment Pipeline
23
Source: Wikipedia - Continuous Delivery

25. 25
Devops Results
Google
• Over 15,000 engineers in over 40 offices
• 4,000+ projects under active development
• 5500+ code submissions per day (20+ p/m)
• Over 75M test cases run daily
• 50% of code changes monthly
• Single source tree
• Over 75M test cases run daily
2016
150 Million automated
tests run daily…

26. 26
Unicorns and Horses (Enterprises)
Unicorns
Enterprise
Shamelessly stolen and repurposed from: Pete Cheslock

27. 27
Devops Results
Enterprise Organizations
• Ticketmaster - 98% reduction in MTTR
• Nordstrom - 20% shorter Lead Time
• Target - Full Stack Deploy 3 months to minutes
• USAA - Release from 28 days to 7 days
• ING - 500 applications teams doing devops
• CSG - From 200 incidents per release to 18

28. DevSecOps as Supply Chain?
28
Source: Wikipedia - Continuous Delivery

29. DevSecOps
29

30. DevSecOps
30

31. DevSecOps - Kill Chain Lab
31

32. Devops Kaizen

33. The Value Stream
3

34. The Value Stream
3

35. Devops Kata
▪ Toyota Kata
▪ Improvement
▪ Coaching
3
Source: Mike Rother - Toyota Kata

36. Devops Kata
▪ Toyota Kata
▪ Improvement
▪ Coaching
3
Source: Mike Rother - Toyota Kata

37. Dojo
Experimental Learning

38. •Experiential learning about DevOps tools and
techniques.
•Team transform their projects to use the
recommended DevOps principles and tools.
•Adaptive training to empower teams to be
DevOps successes.
•It is also a vector by which best practices are
communicated and new behaviors are role-
modeled and practiced.
•The training evolves over time as the
organization’s needs and maturity changes.
Transformation Immersion Center

39. •One Day Workshops
•Multiple Day Bootcamps
•Five Day Flashbuilds
•30 Day Challenges
Dojo

40. •Devops Workshop
•DevSecOps Workshop
•Devops Retrospective Workshop