DevOpsDays Portland 2013 talk. This is a different talk to the one I gave at PuppetConf - less tool focused and with more focus on the fundamentals of CD and its applicability to your area of IT.

1. Just What Is This Continuous
Delivery Thing, Anyway?
Eric Shamow
Methodologies Lead | Puppet Labs
@eshamow
Monday, November 4, 13

2. DevOps is about facilitating
the business through IT
Monday, November 4, 13

3. It’s about the flow of value
through your company
Monday, November 4, 13

4. IT is bursty
Monday, November 4, 13

5. Factories are Bursty
Monday, November 4, 13

6. Factories are Bursty
...but they’ve solved a lot of this
Monday, November 4, 13

7. Code is Value
Monday, November 4, 13

8. Code is Value
“How long would it take your organization to
deploy a change that involves just one single
line of code? Do you do this on a repeatable,
reliable basis?”
- Mary and Tom Poppendieck, Implementing Lean Software
Development
Monday, November 4, 13

9. Flow
Business
Dev
Monday, November 4, 13
Customer
Ops

10. How do we speed up flow?
Laying a foundation - Gene Kim’s Three Ways
Monday, November 4, 13

11. Developing Systems Thinking
Theory of Constraints
Monday, November 4, 13
The Three Ways

12. The First Way (Automate)
Systems Thinking / Flow
Business
Customer
Dev
Ops
Monday, November 4, 13

13. The First Way (Automate)
• Never pass a defect downstream
• Never allow local optimization to create
global degradation
• Always look to increase flow
• Always seek understanding of the system
Monday, November 4, 13

14. Something’s Missing Here!
Monday, November 4, 13

15. The Second Way (Collaborate)
Amplify Feedback Loops
Business
Dev
Monday, November 4, 13
Customer
Ops

16. The Second Way (Collaborate)
• Cross-team info sharing
• Customer feedback
• Fix bugs faster, fewer regressions
• Decrease delivery time
• Decrease unplanned work
Monday, November 4, 13

17. The Third Way (Ship)
Culture - Continual Experimentation and Learning
Business
Dev
Monday, November 4, 13
Customer
Ops

18. The Third Way (Ship)
•
Continual experimentation
•
Acceptance of risk and learning from failure
•
Do difficult things more often
•
Deliberately inject faults
•
Test business hypotheses in real time
•
Add system stress to decrease cycle time
Monday, November 4, 13

19. How do I improve?
Look to decrease cycle times
Reduce the amount changed per
cycle
Monday, November 4, 13

20. Don’t Optimize for Maximum
Utilization
• We don’t expect our systems to operate
successfully at 100% capacity
• We expect activity to burst
• If people are scheduled for 100% utilization
they aren’t free for bursty activity
Monday, November 4, 13

21. THAT SOUNDS SO EASY!
Where do we look?
Monday, November 4, 13

22. This is What Success Looks Like
• You haven’t read it yet
• You still haven’t read it
• Why are you still here?
• GO. READ IT NOW.
Monday, November 4, 13

23. Traditional Release Process
Monolithic
plan
MVP
code
Budgeted time
Monday, November 4, 13
QA/Test
Delivery
Delays

24. Deployment Pipeline
Shamelessly stolen from Jez Humble
Monday, November 4, 13

25. This is What Success Looks Like
•
Each step in this pipeline gets deployed using the
CM tools and techniques
•
Each landscape is as close to prod as you can get
•
Each deployment looks like a production
deployment
•
Each deployment tests the rollout again
•
By the time you release to prod, this build has
been deployed A LOT
Monday, November 4, 13

26. This is What Success Looks Like
•
Frequent, automated releases
•
Every check-in is a potential release
•
Every change triggers feedback
•
Feedback must be received as soon as possible
•
Automate almost everything
•
Build quality in
- Chris Hilton, Beyond Continuous Delivery
Monday, November 4, 13

27. Building a Pipeline
Don’t Get Into Tooling Food Fights
Monday, November 4, 13

28. How Do We Get Buy-In?
Target internal customer needs
Monday, November 4, 13

29. Why I Want CD (if I’m the Business)
• Innovate Faster
• Respond to Market Demands
• Fix Screw-Ups
• Lean/Agile
Monday, November 4, 13

30. Why I Want CD? (If I’m Dev)
• I can’t test against prod unless my
environment looks like prod
• Finding out root cause is really hard
• Merge windows are really hard
• I need QA/Test feedback quickly
Monday, November 4, 13

31. Why I Want CD? (If I’m Ops)
•
Ensure I get real handoff from Dev
•
Infrastructure changes tested along with apps
•
Small changes that don’t blow up prod on
deploy day
•
Ensure changes are thoroughly tested before
deploy
•
Self-service
Monday, November 4, 13

32. Fear Is the Mind Killer
You can still release as slowly as you
want.
You just have the option to go faster
Monday, November 4, 13

33. It’s a Culture Shift
•
Tool choice is not as important as tool sharing
•
People and culture can work around bad tools
•
Everybody owns the pipeline
•
If the build is broken, it’s everybody’s problem
•
We’re on the same team
Monday, November 4, 13

34. Thank You
Eric Shamow
Methodologies Lead | Puppet Labs
@eshamow
Monday, November 4, 13