Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Ship it boise

402 views

Published on

The DevOps movement provides guidance on better ways to deliver working software to production in a fast, safe and automated manner. Is releasing new features every few weeks still a good approach? How quickly can you get a critical bug fix into production? Are you continually learning and improving? This talked is based on books such as The DevOps Handbook, Release It, and from real world experience delivering "mission critical" microservices in high volume production environments. Come learn how to increase profitability, improve culture, and exceed productivity goals through DevOps practices. We've all messed up releases. Learn from it. Embrace. Improve!

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Ship it boise

  1. 1. @shaunabram | shaunabram.com | shaun@abram.com Ship It! Get code into production. Smoothly, quickly, safely. March 18th, 2017
  2. 2. What is DevOps? build test release automate learn improve 2
  3. 3. 3
  4. 4. 4 THE LEAN MOVEMENT CONTINUOUS DELIVERY TOYOTA KATATHE AGILE MANIFESTO DevOps a convergence of many philosophical and management movements
  5. 5. 5 The 3 ways 1 Flow 2 3 Feedback Learning
  6. 6. 6 The Principles of Flow The First Way fast and smooth flow of work from Dev to Ops to deliver value to customers quickly
  7. 7. 7 The Principles of Flow The First Way  Limit WIP  Reduce Batch Sizes  Reduce the number of handoffs  Continually elevate constraints
  8. 8. 8 The First Way: The Technical Practices of Flow
  9. 9. 9 Build a fast, reliable pyramid of tests Test first; automate always Integrate non-functional requirements into tests Pull the andon cord! Automated Testing The First Way: The Technical Practices of Flow
  10. 10. 10 Create a deployment pipeline Create a deployment pipeline Small batch development Short lived feature branches Trunk-based development The First Way: The Technical Practices of Flow
  11. 11. 11 Standardize Environments Create a single repo of truth On-demand creation of envs Rebuild, not repair Done = running in prod-like env The First Way: The Technical Practices of Flow
  12. 12. 12
  13. 13. 13 The First Way: The Technical Practices of Flow
  14. 14. 14 Low-Risk Releases The First Way: The Technical Practices of Flow Automated, self-service deployments Decouple deployments from releases Blue-Green Deployment Pattern Canary release pattern
  15. 15. 15 The First Way: The Technical Practices of Flow Limit WIP, make it visible Reduce Batch Sizes & handoffs
  16. 16. 16 The Principles of Feedback The Second Way fast feedback from right to left create safety & resiliency in complex systems
  17. 17. 17 Use telemetry Use peer reviews and inspections Get feedback from deployments The Second Way: The Principles of Feedback fast and continuous feedback from Operations to Development
  18. 18. 18 Use telemetry Use peer reviews and inspections Get feedback from deployments The Second Way: The Principles of Feedback fast and continuous feedback from Operations to Development • See problems as they occur • Log useful metrics • Overlay other relevant information e.g. releases • Analyze: Means, SDs
  19. 19. 19 Use telemetry Use peer reviews and inspections Get feedback from deployments The Second Way: The Principles of Feedback fast and continuous feedback from Operations to Development For deployment and releases: • Actively monitoring feature metrics • Have devs initially self-manage prod releases • Then dev and ops should share pager duty
  20. 20. 20 Use telemetry Use peer reviews and inspections Get feedback from deployments The Second Way: The Principles of Feedback fast and continuous feedback from Operations to Development • Avoid formal approval processes, manual testing • Get feedback closer to the source • Favor peer reviews and inspections e.g,. GitHub PR, pair programming • Fearlessly cut bureaucratic processes
  21. 21. 21 Continual Learning & Experimentation The Third Way high-performing teams require and actively promote learning If you're not improving, you are getting worse!
  22. 22. Enable organizational learning 22 Errors Happen! Blameless post-mortems local -> global learnings How does your org respond? Pathological, bureaucratic or generative? - blame - fear + honesty & learning share RCAs, code, best practices
  23. 23. CONTINUOUS LEARNING 23 SwarmReserve Learning Time Share
  24. 24. 24 Relentlessly experiment Introduce tension to elevate performance Game Days of Failure Break Production! PUSH THE LIMITS
  25. 25. 25 The 3 ways 1 Flow 2 3 Feedback Learning Questions?

×