Downloaded 81 times
![©2016CloudBees,Inc.AllRightsReserved
16
How Do You Deliver Better Software Faster?
16
“DevOps is a software
development method that stresses
communication, collaboration and
integration between software
developers and information
technology (IT) professionals.”[1]
[1] http://en.wikipedia.org/wiki/DevOps
DevOps](https://image.slidesharecdn.com/sddevops-cloudbees-devopsquadrants-160317192944/85/SD-DevOps-Meet-up-Exploring-Quadrants-of-DevOps-Maturity-16-320.jpg)
![©2016CloudBees,Inc.AllRightsReserved
17
How Do You Deliver Better Software Faster?
17
“DevOps is a software
development method that stresses
communication, collaboration and
integration between software
developers and information
technology (IT) professionals.”[1]
[1] http://en.wikipedia.org/wiki/DevOps
DevOps
But You Can’t “Do” DevOps. DevOps an outcome.](https://image.slidesharecdn.com/sddevops-cloudbees-devopsquadrants-160317192944/85/SD-DevOps-Meet-up-Exploring-Quadrants-of-DevOps-Maturity-17-320.jpg)
Uploaded byBrian Dawson
SD DevOps Meet-up - Exploring Quadrants of DevOps Maturity
The document discusses the four quadrants of DevOps maturity, highlighting the stages from team-level Agile to enterprise-level DevOps. It emphasizes the importance of communication, collaboration, and continuous delivery practices in improving software delivery. Additionally, it outlines strategies, tools, and technologies that facilitate the transition through these maturity levels while promoting a culture of learning and innovation.
More Related Content
Similar to SD DevOps Meet-up - Exploring Quadrants of DevOps Maturity
SD DevOps Meet-up - Exploring Quadrants of DevOps Maturity
- 1. ©2016CloudBees,Inc.AllRightsReserved 1 ©2016CloudBees,Inc.AllRightsReserved DevOps Connect Four Exploringthe 4 Quadrants of DevOps Maturity Brian Dawson, CloudBees Inc @brianvdawson brianvdawson@cloudbees.com
- 2. ©2016CloudBees,Inc.AllRightsReserved 2 • How bigis your Development/IT organization? a) 1 – 50 ppl b) 50 – 200 ppl c) 200 – 500 ppl d) Other or ”Do you know anybody hiring?" • What is your role? a) Developer b) Operations c) QA d) All of the above e) Other Poll (1/2) 2
- 3. ©2016CloudBees,Inc.AllRightsReserved 3 • By showof hands do you practice? a) Continuous Integration b) Continuous Delivery c) DevOps d) None of the above or GDD (Get ‘er Done Development) • Do you use Jenkins? a) Yes, heavily b) Starting to or have in the past c) What is Jenkins? d) Using something else Poll (2/2) 3
- 4. ©2016CloudBees,Inc.AllRightsReserved 4 Hints & Tips Simplify DevOps message, communicate widely& frequently Define where you are, identify where you are going…Go! Be pragmatic, not dogmatic Leverage enabling tools & technology to connect people & process across boundaries (organizational, technical, etc.) Respect the trinity, people, process, tools (& technology) Continuously measure & report Incremental transformation
- 5. ©2016CloudBees,Inc.AllRightsReserved 5 Mission • Prologue: ApproachingDevOps • Level Map: Simplified framing of an organization’s DevOps maturity • Strategy Guide: Adoption patterns and cycles • Power Ups: Enabling tools and technology • Leave with new ideas and inspired
- 6. ©2016CloudBees,Inc.AllRightsReserved 6 Player Background: • QA,Development, Development Management Player Strengths: • Software development optimization – 1990s o Graphics pipeline optimization o Tools and middleware – Early 2000’s o OSS practices – Late 2000’s o Process consulting o CI, CD, and DevOps transformation practice • Knowledge redistribution Character Guide: About Me
- 7. ©2016CloudBees,Inc.AllRightsReserved 7 SECOPSMICROSERVICES GIT JENKINS GITLAB SCRUM DEVOPS CONTINUOUS IMPROVEMENT MICROSERVICES SC GIT PERFORCE CIRCLECI SCRUM SCRUM XP LEAN CONTINUOUSDELIVERY CONTINUOUSDELIVERY CONTINUOUS DEPLOYMENT VM TESTAUTOMATION BLAZE METER NEW RELIC STOP THE LINE DevOps Word Soup
- 8. ©2016CloudBees,Inc.AllRightsReserved 8 DEVOPS SECOPS CONTINUOUS IMPROVEMENT CONTINOUS INTEGRATION CONTINUOUSDELIVERY CONTINUOUSDELIVERY CONTINUOUSDEPLOYMENT MICROSERVICES MICROSERVICES VM SCM TEST AUTOMATION GIT GIT PERFORCE JENKINS CIRCLECI GITLAB BLAZE METER NEW RELIC SCRUM SCRUM SCRUM XP LEAN STOP THE LINE DevOps Word Soup
- 9. ©2016CloudBees,Inc.AllRightsReserved 9 SIMPLE CAN BEHARDER THAN COMPLEX: YOU HAVE TO WORK HARD TO GET YOUR THINKING CLEAN TO MAKE IT SIMPLE. BUT IT’S WORTH IT IN THE END BECAUSE ONCE YOU GET THERE, YOU CAN MOVE MOUNTAINS. -Steve Jobs
- 10. ©2016CloudBees,Inc.AllRightsReserved 10 WHERE ARE WE? WHERE ARE WEGOING? HOW DO WE GET THERE? SIMPLIFY
- 11. ©2016CloudBees,Inc.AllRightsReserved 11 WHERE ARE WE? WHERE ARE WEGOING? HOW DO WE GET THERE? DevOps
- 12. ©2016CloudBees,Inc.AllRightsReserved 12 WHERE ARE WE? WHERE ARE WEGOING? HOW DO WE GET THERE? DevOps(according to me ;^)
- 13. ©2016CloudBees,Inc.AllRightsReserved 13 13© 2015 SOASTAInc.- All rights reserved. Fundamentally we are talking about... 13 Delivering Better Software Faster Concept-to-Customer High Quality • Performance • Feature • Function Rapidly Eliminating Waste Market Innovation High Value
- 14. ©2016CloudBees,Inc.AllRightsReserved 14 How Do YouDeliver Better Software Faster? 14 ProdDev Rapidly Repeatedly Reliably ProdDev
- 15. ©2016CloudBees,Inc.AllRightsReserved 15 How Do YouDeliver Better Software Faster? 15 Rapidly Repeatedly Reliably ProdDev
- 16. ©2016CloudBees,Inc.AllRightsReserved 16 How Do YouDeliver Better Software Faster? 16 “DevOps is a software development method that stresses communication, collaboration and integration between software developers and information technology (IT) professionals.”[1] [1] http://en.wikipedia.org/wiki/DevOps DevOps
- 17. ©2016CloudBees,Inc.AllRightsReserved 17 How Do YouDeliver Better Software Faster? 17 “DevOps is a software development method that stresses communication, collaboration and integration between software developers and information technology (IT) professionals.”[1] [1] http://en.wikipedia.org/wiki/DevOps DevOps But You Can’t “Do” DevOps. DevOps an outcome.
- 18. ©2016CloudBees,Inc.AllRightsReserved 18 Continuous delivery (CD)is… 18 • …the practice of automatically and continuously building, testing and deploying software to ensure it CAN be released at any time. • …an extension of continuous integration (CI) and enables DevOps • …NOT Continuous Deployment
- 19.
- 20. ©2016CloudBees,Inc.AllRightsReserved 20 X-Axis: SDLC Phases Source:February 5, 2014, “How Can You Scale Your Agile Adoption?” Forrester report Agile Upstream 33% Agile Downstream 13% Define Plan Code Build Integrate Test Release Deploy Operate
- 21. ©2016CloudBees,Inc.AllRightsReserved 21 Y-Axis: Levels ofadoption Source: February 5, 2014, “How Can You Scale Your Agile Adoption?” Forrester report Agile Upstream 33% Agile Downstream 13% Enterprise Agile Upstream 22% Enterprise DevOps 10% TeamWorkgroupEnterprise Define Plan Code Build Integrate Test Release Deploy Operate
- 22. ©2016CloudBees,Inc.AllRightsReserved 22 Y-Axis: Levels ofadoption Source: February 5, 2014, “How Can You Scale Your Agile Adoption?” Forrester report Agile Upstream 33% Agile Downstream 13% Enterprise Agile Upstream 22% Enterprise DevOps TeamWorkgroupEnterprise Define Plan Code Build Integrate Test Release Deploy Operate • Gain competitive advantage • Innovate faster • Respond to market • Increased productivity • Employee satisfaction and retention $$
- 23. ©2016CloudBees,Inc.AllRightsReserved 23 The Chasms Source: February5, 2014, “How Can You Scale Your Agile Adoption?” Forrester report Agile Upstream Agile Downstream Enterprise Agile Upstream Enterprise DevOps TeamWorkgroupEnterprise Define Plan Code Build Integrate Test Release Deploy Operate Enterprise DevOps
- 24. ©2016CloudBees,Inc.AllRightsReserved 24 The Quadrants Quadrant 1: Team-level Agile Quadrant2: Team-level CD Quadrant 3: Enterprise Agile Quadrant 4: Enterprise DevOps TeamWorkgroupEnterprise Define Plan Code Build Integrate Test Release Deploy Operate Enterprise DevOps
- 25. ©2016CloudBees,Inc.AllRightsReserved 25 The Characteristics Enterprise DevOps TeamWorkgroupEnterprise DefinePlan Code Build Integrate Test Release Deploy Operate • Enterprise support for cloud with standard tools and process for automated test, dynamically provisioned environments, immutable infrastructure, IaC… • Business and customers aligned with iterative agile definition and delivery • Tools integration to common platform supporting reporting and metrics, security, governance and traceability • Culture of learning and innovation • Standard enterprise-wide iterative/agile development practices • Business aligned with agile specification • Common PM and dev process • Team-level tools and delivery process • Specific applications supported by automated test, dynamically provision environments, immutable infrastructure or IaC… • Team CI extended to CD • Team-level tools integration w/delivery tools • Ops alignment with PM and dev process as team specific “one-offs” • Team(s) adopt iterative/agile development practices • Development team(s) independently leverage CI • Team-level tools integration • Team specific PM and dev process • Water-Scrum-fall approach
- 26. ©2016CloudBees,Inc.AllRightsReserved 26 Quadrant 1: Team-LevelAgile Enterprise DevOps TeamWorkgroupEnterprise Define Plan Code Build Integrate Test Release Deploy Operate • Enterprise support for “cloud” with standard tools and process for automated test, dynamically provisioned environments, immutable infrastructure, IaC… • Business and customers aligned with iterative agile definition and delivery • Tools integration to common platform supporting reporting and metrics, security, governance, and traceability • Culture of learning and innovation • Standard enterprise-wide iterative/Agile development practices • Business aligned with agile specification • Common PM and Dev process • Team-level tools and delivery process • Specific applications supported by automated test, dynamically provision environments, immutable infrastructure or IaC… • Team CI extended to CD • Team-level tools integration w/Delivery tools • Ops alignment with PM and Dev process as team specific “one-off” • Team(s) adopt iterative/Agile development practices • Development team(s) independently leverage CI • Team-level tools integration • Team specific PM and Dev process • Water-scrum-fall approach Team(s) adopt iterative/agile development practices Development team(s) independently leverage CI Team-level tools integration Team specific PM and dev processes Water-Scrum-fall approach + - + - -
- 27. ©2016CloudBees,Inc.AllRightsReserved 27 Quadrant 2: Team-LevelCD Enterprise DevOps TeamWorkgroupEnterprise Define Plan Code Build Integrate Test Release Deploy Operate • Enterprise support for “cloud” with standard tools and process for automated test, dynamically provisioned environments, immutable infrastructure, IaC… • Business and customers aligned with iterative agile definition and delivery • Tools integration to common platform supporting reporting and metrics, security, governance, and traceability • Culture of learning and innovation • Standard enterprise-wide iterative/Agile development practices • Business aligned with agile specification • Common PM and Dev process • Team-level tools and delivery process • Specific applications supported by automated test, dynamically provision environments, immutable infrastructure or IaC… • Team CI extended to CD • Team-level tools integration w/Delivery tools • Ops alignment with PM and Dev process as team specific “one-off” • Team(s) adopt iterative/Agile development practices • Development team(s) independently leverage CI • Team-level tools integration • Team specific PM and Dev process • Water-scrum-fall approach Specific applications supported by automated test, dynamically provision environments, immutable infrastructure or IaC… Team CI extended to CD Team-level tools integration w/delivery tools Ops alignment with PM and dev process as team specific “one-offs” + + - +
- 28. ©2016CloudBees,Inc.AllRightsReserved 28 Quadrant 3: EnterpriseAgile CD Enterprise DevOps TeamWorkgroupEnterprise Define Plan Code Build Integrate Test Release Deploy Operate • Enterprise support for “cloud” with standard tools and process for automated test, dynamically provisioned environments, immutable infrastructure, IaC… • Business and customers aligned with iterative agile definition and delivery • Tools integration to common platform supporting reporting and metrics, security, governance, and traceability • Culture of learning and innovation • Standard enterprise-wide iterative/Agile development practices • Business aligned with agile specification • Common PM and Dev process • Team-level tools and delivery process • Specific applications supported by automated test, dynamically provision environments, immutable infrastructure or IaC… • Team CI extended to CD • Team-level tools integration w/Delivery tools • Ops alignment with PM and Dev process as team specific “one-off” • Team(s) adopt iterative/Agile development practices • Development team(s) independently leverage CI • Team-level tools integration • Team specific PM and Dev process • Water-scrum-fall approach Standard enterprise-wide iterative/agile development practices Business aligned with agile specification Common PM and dev process Team-level tools delivery process Team-level tools integration + + - + -
- 29. ©2016CloudBees,Inc.AllRightsReserved 29 Quadrant 4: EnterpriseDevOps Enterprise DevOps TeamWorkgroupEnterprise Define Plan Code Build Integrate Test Release Deploy Operate • Enterprise support for “cloud” with standard tools and process for automated test, dynamically provisioned environments, immutable infrastructure, IaC… • Business and customers aligned with iterative agile definition and delivery • Tools integration to common platform supporting reporting and metrics, security, governance, and traceability • Culture of learning and innovation • Standard enterprise-wide iterative/Agile development practices • Business aligned with agile specification • Common PM and Dev process • Team-level tools and delivery process • Specific applications supported by automated test, dynamically provision environments, immutable infrastructure or IaC… • Team CI extended to CD • Team-level tools integration w/Delivery tools • Ops alignment with PM and Dev process as team specific “one-off” • Team(s) adopt iterative/Agile development practices • Development team(s) independently leverage CI • Team-level tools integration • Team specific PM and Dev process • Water-scrum-fall approach Enterprise support for cloud with standard tools and process for automated test, dynamically provisioned environments, immutable infrastructure, IaC… Business and customers aligned with iterative agile definition and delivery Tools integration to common platform supporting reporting and metrics, security, governance and traceability Culture of learning and innovation + + + +
- 30. ©2016CloudBees,Inc.AllRightsReserved 30 CI-> Agile ->Ent. Agile -> Ent. DevOps 1. Team(s) start with CI 2. Team(s) adopt Scrum/agile planning and project management 3. Organization implements Scrum/agile definition planning and project management 4. Organization aligns on DevOps strategy with teams using common CI/CD process and tools Adoption Pattern #1: TeamWorkgroupEnterprise Define Plan Code Build/CI Test Release/Deploy Operate Enterprise DevOps 2 3 4 1
- 31. ©2016CloudBees,Inc.AllRightsReserved 31 Adoption Pattern #2 TeamAgile -> Ent. Agile -> Ent. DevOps 1. Team(s) adopt Scrum/agile planning and project management 2. Organization implements Scrum/agile definition, planning and project management 3. Organization aligns on DevOps strategy with teams using common CI/CD process and tools TeamWorkgroupEnterprise Enterprise DevOps 1 2 3 Define Plan Code Build/CI Test Release/Deploy Operate
- 32. ©2016CloudBees,Inc.AllRightsReserved 32 Adoption Pattern #3 TeamAgile -> Team CD -> Ent. Agile -> DevOps 1. Team(s) adopt Scrum/agile project planning and management 2. Team(s) extend CI to Continuous Delivery 3. Organization implements Scrum/agile 4. Organization aligns on DevOps strategy with teams using common CI/CD process and tools TeamWorkgroupEnterprise Enterprise DevOps 1 3 4 2 Define Plan Code Build/CI Test Release/Deploy Operate
- 33.
- 34. ©2016CloudBees,Inc.AllRightsReserved 34 Adoption Cycles: Top-DownTeamWorkgroupExecutive Time Visibility Adoption Executive Initiative Team Successes Workgroup Success ScaleAcross Workgroups 1 2 6 4 3 Workgroup Initiative
- 35. ©2016CloudBees,Inc.AllRightsReserved 35 Tools & Technologiesenable “crossing the chasm” Normalized Language and practice agnostic Not Dev or Ops specific Distributed Rich Integration Support Tools as microservices Modular Automated Repeatability Reportability Flexibility Increase Confidence In Downstream Deliverables Support supply- chain Traceability Immutability Measure and report Scale To Enterprise Cross-domain visibility metrics Security and governance Supported 35
- 36. ©2016CloudBees,Inc.AllRightsReserved 36 Click to addtitleTeamWorkgroupExecutive CloudBees Jenkins OSS Rally Jira Misc Point Solutions Chef Puppet HP OO SVN Git NolioMiscellaneous ALM Solutions HP ALI TestLink Helpdesk Selenium PPM XL Release Nexus Chat LDAP APM Docker Define Plan Code Build Integrate Test Release Deploy Operate
- 37. ©2016CloudBees,Inc.AllRightsReserved 37 TeamWorkgroupExecutive Define Plan CodeBuild Integrate Test Release Deploy Operate MiscPoint Solutions Jira, TeamForge.. Eclipse, IntelliJ,SVN, Git Jenkins, Make, Maven.. Jenkins,CI Solutions Selenium, TestLink… XLRelease, HPOO… XLRelease, HPOO… Chat, Logging, Monitoring LDAP, SAML Product Portfolio Application Performance Mgt Service Desk Click to add title
- 38. ©2016CloudBees,Inc.AllRightsReserved 38 TeamWorkgroupExecutive Define Plan CodeBuild Integrate Test Release Deploy Operate MiscPoint Solutions JIRA, TeamForge.. Eclipse, IntelliJ,SVN, Git Jenkins, Make, Maven.. Jenkins,CI Solutions Selenium, TestLink… XLRelease, HPOO… XLRelease, HPOO… Chat, Logging, Monitoring Click to add title Integrate and Automate Security and Access Controls Reporting and Analytics Supply Chain Managment Shared Infrastructure – Containers or IaC Enterprise DevOps