Download as PDF, PPTX
Uploaded byDyaneshwaran Periyasamy
Daredevil DevOps
The document discusses the concepts of "Daredevil DevOps" and the journey from continuous integration to continuous deployment and monitoring. It begins with an introduction to the speaker and an overview of topics to be covered, including defining DevOps and why it is called "Daredevil". The document then covers the historical development of approaches like waterfall, iterative development, agile and lean methodologies. It discusses how continuous integration, delivery and deployment works and the benefits of collaboration between development and operations teams. The key is automating processes, measuring metrics like deployment frequency, and aligning IT capabilities with business needs.
More Related Content
Daredevil DevOps
- 1.
- 2. About the speaker DyaneshwaranPeriyasamy Agile Consultant, Trainer & Coach 11+ years of IT experience 9+ years in the area of Lean and Agile methodologies Handled Lean & Agile transformation across large organizations Trained ~1000 participants in the area of Lean, Agile and DevOps Speaker in “India Agile Week 2013” and “Lean India Summit 2013 (c) Copyright 2015 Dyaneshwaran Periyasamy
- 3. I am goingto talk about… Introduction of the term "Daredevil DevOps" Why I call DevOps a "Daredevil"? Market hype around DevOps Why the hype was created? Journey from Continuous Integration to Continuous Delivery Why it is not enough to stop here? Journey from Continuous Delivery to Continuous Deployment & Monitoring Why it is required? For whom? DevOps - a end goal and not a model/framework How IT can help the Business win? (c) Copyright 2015 Dyaneshwaran Periyasamy
- 4. Why I callDevOps a "Daredevil"? (c) Copyright 2015 Dyaneshwaran Periyasamy
- 5. CIO CFO COOCEO PMO Development Operations (c) Copyright 2015Dyaneshwaran Periyasamy
- 6. Journey from ContinuousIntegration to Continuous Delivery (c) Copyright 2015 Dyaneshwaran Periyasamy
- 7. SDLC Requirements Analysis DesignCoding Testing Deployment Maintenance (c) Copyright 2015 Dyaneshwaran Periyasamy
- 8.
- 9.
- 10. Agile (c) Copyright 2015Dyaneshwaran Periyasamy
- 11. Comparison of methods WaterfallIterative Agile Strengths • Easy to understand • Supports creation of detailed plan • Deliver business value • Responsive to change • Faster time-to-market • Constant feedback • Highest business value delivered early Weaknesses • Brittle if requirements change • Wasteful if business strategy changes • Big Up Front Planning / Design • Requires mind shift • Increased uncertainty for “far” iterations • Fixed feature / price contracts • Dependency on people and their interactions creates cultural resistance to change • Hazardous if not ALL parties embrace the Agile Manifesto Project Suitability • Legacy environment • Stable team with significant domain / technology experience • Minimal change • Fluid requirements • New / untried technology • Cohesive teams, even if geographically dispersed • Evolving requirements • Niche technologies / few legacy dependencies • Dependent on end user feedback (c) Copyright 2015 Dyaneshwaran Periyasamy
- 12. Developers Vs Testers Howcan I make it? How can I break it? (c) Copyright 2015 Dyaneshwaran Periyasamy
- 13. Developers + Testers! (c)Copyright 2015 Dyaneshwaran Periyasamy
- 14. Agile Milestone Continuous Integration Continuous Delivery (c)Copyright 2015 Dyaneshwaran Periyasamy
- 15. Journey from ContinuousDelivery to Continuous Deployment & Monitoring (c) Copyright 2015 Dyaneshwaran Periyasamy
- 16. Cont. Delivery toCont. Deployment (c) Copyright 2015 Dyaneshwaran Periyasamy
- 17. Development Vs Operations Bemore agile – deliver faster Change is evil (c) Copyright 2015 Dyaneshwaran Periyasamy
- 18. What is DevOps? Collaborationbetween Dev and Ops Continuous Deployment / Monitoring Team of developers and operation staff Culture movement Process or Framework Philosophy, movement, a way of thinking Culture Shift and set of principles and methods (based on Agile & Lean) for better Dev & Ops collaboration to build software that meets business needs faster, cheaper & more reliably. (c) Copyright 2015 Dyaneshwaran Periyasamy
- 19. Why DevOps? Mainframe Client/Server Internet Mobile, Social, Cloud& Big Data Every 60 seconds 98,000 tweets 23,148 apps downloaded 400,710 ad requests 2,000 lyrics played on Tunewiki 1,500 pings sent on PingMe 34,597 people are using Zinio 208,333 minutes Angry Birds played (c) Copyright 2015 Dyaneshwaran Periyasamy
- 20. Challenges in reactingto change Source: Forrester Research Inc., “Five Ways To Streamline Release Management”, February 2011 Release process is too long Source: Gartner., “Catalysts Signal the Growth of DevOps”, February 2011 Relation between application development and IT operations? (c) Copyright 2015 Dyaneshwaran Periyasamy
- 21. State of DevOpsReport (2012) Deploy Frequency Deploy Lead Time Amazon 23,000 per day minutes Google 5,500 per day minutes Netflix 500 per day minutes Facebook 1 per day hours Twitter 3 per week hours Agility Metrics • 30x more frequent code deployments • 8000x faster code deployment lead time Reliability Metrics • 2x the change success rate • 12x faster Mean Time To Recover (MTTR) (c) Copyright 2015 Dyaneshwaran Periyasamy
- 22. Next Revolution Continuous Delivery ContinuousDeployment & Monitoring (c) Copyright 2015 Dyaneshwaran Periyasamy
- 23. How DevOps canhelp the business win (c) Copyright 2015 Dyaneshwaran Periyasamy
- 24. DevOps Objectives Automation QualityCollaboration Governance Monitoring (c) Copyright 2015 Dyaneshwaran Periyasamy
- 25. Prerequisites for DevOpsSuccess On board Executive Sponsors / Stakeholders Create organization’s ‘value’ stream Restructure Development and Operations team Change performance incentives for Dev and Ops teams Standardize processes which can be repeated Leverage automation Infrastructure as code Continuous Integration / Delivery / Deployment / Monitoring Capture key metrics Change Frequency Change Lead Time Change Failure Rate MTTR (c) Copyright 2015 Dyaneshwaran Periyasamy
- 26. Alignment with thebusiness needs Don’t Automate What You Don’t Understand! (c) Copyright 2015 Dyaneshwaran Periyasamy
- 27. The Three Waysto DevOps… (c) Copyright 2015 Dyaneshwaran Periyasamy
- 28. Several DevOps Patterns (c)Copyright 2015 Dyaneshwaran Periyasamy
- 29. Thank You! (c) Copyright2015 Dyaneshwaran Periyasamy