DevOps Enablement Roadmap Considerations for Enablement Teams

DevOps Enablement Roadmap Considerations for Enablement Teams

1. Enablement Teams

2. Enablement Roadmap What are the steps? Baseline Assessment 1 Standup Enablement Team 2 Build Skills and Toolkit 3 Delivery Team Enablement 4 Delivery Team Assessment 5 The Enablement Journey …

3. Considerations for Enablement Teams

4. Sample Presentation from DevOps Enablement Team

5. What is DevOps? Business Developers IT Ops Agile : How do I develop the “ right ” software? ALM : How do I develop software with quality ? DevOps : How do I deliver software faster ? “DevOps is the next step in the evolution of Agile and ALM”

6. What does DevOps Look like? OLD WORLD Focus on planning Compete , not collaborate Static hierarchies Individual productivity Efficiency of process Assumptions , not data Estimating performance NEW WORLD Focus on delivering Collaborate to win Fluent and flexible teams Collective value creation Effectiveness of outcomes Experiment, learn and respond Measuring performance The shift to DevOps

7. What does DevOps look like? Production Development Requirements Collaboration Unified Backlog Operational Deliverables Application-driven Infrastructure Feedback Loops Delivery Teams Production Experimentation & Monitoring

8. What does DevOps Look like? What does it mean for me? Business Teams Tech Debt Matters Learn from Customers Software is never done Developers You build it, you run it Code for operations Testing is for everyone Testers Automation is a must Test quality not just quantity Test data must be part of the strategy Operations Apps drive infrastructure Scripting is tool of choice We own customer experience too

9. What does DevOps look like? Author Code Author Infra Author Tests Unit tests Code Coverage Code Analytics Code Metrics Artifact Repo Build Code Profiling Environment Tests Automated Tests Load Tests Pen Tests Exploratory Tests Test Data Feedback Test Provision Infra Deploy App Deploy Tests Backlog Version Control Check-In Staging Prod Bugs Diagnostics App Monitoring Infra Monitoring Usage Analytics A/B Testing Canary Rollback Software Delivery Pipeline Business Innovation Business Agility

10. What does DevOps look like? Lead Time Cycle Time Availability & Performance User Activity Deployment Frequency Work in Progress (WIP) Wait Time & Change Volume Successful Deployments MTTR Production Auto Testing, Provisioning, Staging Builds & Deployments Development & Testing Requirements / Bugs Feature Requests Small Batch Size (single piece flow)

11. How do we get there? Client Example: Insurance services provider Large mainframe investment Small pockets of Agile 10 delivery teams What they asked for? DevOps Roadmap Modern architecture Visibility into DevOps Journey

12. How do we get there? What are the steps? DevOps Assessment 1 Organizational & Team Backlogs 2 DevOps Enablement Team 3 Delivery Team Rollout 4 Re- Assessment 5 The DevOps Journey…

13. How do we get there? Team Assessment Aligned to 7 habits Integrated Delivery team focused End to end delivery of software

14. How do we get there? Team Backlog Actionable Work Items Measureable Progress Work into current sprints

15. How do we get there? Organizational Backlog Common challenges Team roadblocks Unified solution

16. How do we get there? DevOps Enablement Team (temporary) Automated Builds Automated Tests Infrastructure as Code Automated Release Team A Team B Team C Business Teams Development Testing Operations Siloed Teams Delivery Teams

17. How do we get there? Organizational Rollout Timeline

18. How do we get there? Every 3 to 6 month reassessments Validate team growth Next capabilities Share learnings Did we improve?