1. Sirius DevOps Assessment Accelerating Concept to Cash Rolf W. Reitzig Business Agility Senior Practice Manager

2. 2 Opportunity

3. Business Drivers Software and IT organizations are under pressure to develop & deploy more software, yet many companies are losing precious time-to-market due to manual processes and disparate, non- integrated development tools & IT Infrastructure Manual Processes VS

4. Why Is This Important? Sources: Hammond, Jeffrey S. (7 Feb. 2011) “Five Ways to Streamline Release Management”. Forrester Research Inc., ZeroTurnaround, 2011. Java EE Productivity Report 2011. Retrieved from: http://zeroturnaround.com/wp- content/uploads/2010/11/Java_EE_Productivity_Report_2011_finalv2.pdfhttp://zeroturnaround.com/wp- content/uploads/2010/11/Java_EE_Productivity_Report_2011_finalv2.pdf 83%!! Cost to Productivity = 5.3 work weeks/developer/year

5. What If? You could deploy features/capabilities to your customers/users 30 times more frequently? 1 Spend 37% less time handling support cases? 1 Reduce deployment times by 95% from 3 days to 15 minutes? 2 Improve pre-release defect removal rate to 95%? 3 Reduce testing time by 52% 4 Reduce IT labor costs by 12? 5 Increase error-free configuration changes by 40%? 5 Improve software quality by 50%? 6 Release software in hours versus days? 7 Increase product releases from 40 to 300 per year? 8 (1)2014 State of DevOps Report (2)Amica Insurance Company Case Study (3)Soft Bank Mobile Case Study (4)Delta Airlines Case Study (5)Kellogg’s Case Study (6)Nationwide Case Study (7)Fidelity Case Study (8)Cars.com Case Study

6. 6 Challenges

7. Technical/Organizational Complexity and Rates of Change Drive Difficulty Modern application systems are extremely complex and beyond the capacity of one person to understand / manage – Technology components (UI, middleware, database, integrations, APIs, etc.) – Scale in the sheer number of server instances and configurations Complexity is multiplied by many factors – Pipeline of Dev, Test, and Prod mean there are actually several important instances of an application system – Changes are at different stages within the pipeline – Early stage instances receive changes very frequently – Changes can originate from many points

8. Traditional Software Delivery Environments Limit Productive Collaboration: Islands of People, Process and Information  Tool fruit salads Little to no true project visibility Poor process, workflow, and data integration High maintenance and administration costs Persistent functional, geographic and organizational silos

9. 9 What is DevOps?

10. What is DevOps? In a nutshell, a System for Changing Systems to get new features to users faster! Accelerate the time to value of your new business ideas React to market opportunities more quickly Beat competitors to market with new capabilities Remove friction and air gaps from your software delivery cycles Eliminate organizational silos that slow business down Accelerate the time to value of your new business ideas React to market opportunities more quickly Beat competitors to market with new capabilities Remove friction and air gaps from your software delivery cycles Eliminate organizational silos that slow business down Adopting DevOps practices & tools reduces build/deploy/release cycles from days/weeks to minutes/hours and frees up 5.3 work weeks/developer/year!

11. DEVELOPMENT Creative Behavior OPERATIONS Procedural Rigor Creativity Conventional Stovepiped Processes & Tools

12. Procedural Rigor Creativity Conventional Stovepiped Tools DEVELOPMENT and OPERATIONS Continuous Delivery Collaborative Automation Platform DEVELOPMENT Creative Behavior OPERATIONS Procedural Rigor Creativity BUILD RELEASE CHANGE TEST PROJECT MGT.

13. DevOps: A System for Changing Systems Standardized & integrated, tooling No data airgaps Advanced automation & orchestration Fully defined deployment environments Third-party products Product B Product C Product A Open Source Solutions Product D Standardized Platform Services Process Workflow HTTP/REST Real-time, transparent access to project data, risks and progress

14. 14 How To Get Started

15. Realities of Building a “System for Changing Systems” Most current tools and discipline areas are not naturally connected – There will be manual bridges for longer than you would like – Early efforts will be as much about learning as improvement Such a system is never “done” – “Continuous Improvement” necessary to remove friction – Holistic approach means not over-optimizing any one area There will be a lot to learn – Previously unknown truths about the process or application system – New instrumentation techniques for the system Breaking capabilities down will allow an Agile approach – Same benefits of small batch size apply – Prioritize using risk / value decision points

16. Holistic Flow – Bottleneck Hunting The throughput of the whole system is the throughput of the SLOWEST step

17. Sirius DevOps Assessment The easiest way to start is through an Sirius DevOps Assessment that: – Is a quick and efficient way to determine the throughput of a project team’s work – Identifies and quantifies bottlenecks and delays – Finds tool air-gaps that are impeding software quality and productivity Outputs include: – Value Stream Mapping of one software development project’s end-to- end Concept to Cash lifecycle – An assessment of the project’s maturity against Sirius’ proprietary DevOps Reference Maturity Model – Actionable recommendations for high-value areas for improvement