DevOps: Why Should We Care?
Download as PPTX, PDF0 likes321 views
The document discusses the importance of DevOps in improving collaboration between developers, IT operations, and quality assurance to enhance code delivery and quality. It emphasizes implementing a culture of hypothesis-driven development, monitoring technical debt, and making evidence-based decisions to continuously deliver value to customers. It highlights the need for automation, agile practices, and leadership support to successfully adopt DevOps principles.
DevOps: Why Should We Care?
- 1. DevOps Why Should We Care? Kasun Kodagoda Technical Lead | 99X Technology
- 3. Different People Want Different Things It’s About People
- 4. How do I get my code out to production? How do I build my code? What kind of a branching strategy should I use? How do I ensure the quality of my code? How do I spin up resource as quickly as possible? How do I ensure the reliability of my site? How do I know my infrastructure is up and running? How do I scale my resources? How do I make sure the quality of the product? How can I make sure all the functionality is tested? How to I reduce the bugs that goes in to production? Developers IT Operations Quality Assurance
- 5. DevOps Caters to All These People
- 7. Team Autonomy and Organizational Alignment Take Tasks from a Common Backlog Small Teams Working Autonomously Aligned with Organizational Goals 6 Month Planning Cycle/Roadmap Know What They Need To Do To Move the Organization Forward
- 8. Rigorous Management of Technical Debt Technical Debt WILL Creep Up On You Constantly Monitor Your Code and Development Process Not Adding New Technical Debt Working on Removing Existing Technical Debt Have Policies Around Managing Technical Debt
- 9. Focus on Flow of Customer Value Measure the Value You Add to the Customer Have Telemetry Coming In Constantly Observe What Gets Used? What Doesn’t? Engage with High Usage Customers If Possible Customers Feedback is the Most Important Factor
- 10. Hypothesis Driven Development A Backlog That is Groomed with Learning Not Only What Product Owner Likes/Wants Think About What Would Improve the Product Think as Hypothesis, Turn them in to Experiments Evaluate and Continue Build, Measure and Learn
- 11. Evidence Gathered in Production Data Coming From Production to Validate Your Hypothesis Have Instrumentation on Everything Build up or Throw Away Hypothesis Based on Evidence Evidence Based Decision Making
- 12. Production First Culture Get Your Code to Production Frequently Solve Production Incident As Soon As Possible Perform Root Cause Analysis on Live Site Incidents Root Cause Actions comes in to the Backlog Actions Should be Taken within 1-2 Sprints Analyze, Learn & Harden
- 13. Manage Infrastructure as a Flexible Resource Fully Automate Resource Deployments Have the Ability to Scale On-Demand Spin-up Environment as Needed Ability to Swap Out Troublesome Resources
- 15. Configuration Management Release Management Continuous Integration Continuous Deployment Test Automation Application Performance Monitoring Infrastructure as Code
- 16. Where to Begin? You MUST be Agile Start from CI/CD Pipeline Automate, Automate, Automate Everything Move away from “Big Bang” Releases
- 17. People > Process > Tools
- 18. How to Get People In? Leadership is Critical Have Proper Practices in Place Start by Doing Assign Time for Non-Customer Facing Engineering
- 19. But, you need the entire team to win All It Takes is One Person
- 20. Start with finding solutions for what is hurting you. You Don’t Need Everything Above
- 21. - Donovan Brown Microsoft DevOps is the Union of People, Process & Products to Enable Continuous Delivery of Value to the End Users.
- 22. It’s a Journey You Start, That Never Ends… Remember,
- 23. Thank You Start Your DevOps Journey Today, Good Luck :)