1. © 2013 CA. All rights reserved. ScrumOps – Scaling Scrum Environment for DevOps Serajul Arfeen Naveen Arora July 2014

2. Introduction Knowing DevOps Amalgamation of Scrum and DevOps Conceptualizing ScrumOps ScrumOps Practices Q&A

3. “To what extent does the following statement describe your firm’s IT organization’s processes and capabilities – ‘Has the ability to regularly deliver projects on time and on budget’?”* less than 40% of business decision-makers believe IT can deliver new services on time and on budget Base: North American and European business decision-makers in firms with 1,000+ employees *Source: Forrester Research, Inc., Forrsights: Business Execs Increase Direct IT Spend to Support Systems of Engagement, May 16, 2012 3Copyright © 2014 CA. All rights reserved.

4. Top five IT management priorities - Enterprises* - “Which of the following initiatives are likely to be your organization’s top management priorities over the next 12 months?” Base: 1,531 IT decision-makers *Percent of respondents indicating this was a high or critical priority Source: Forrester Research, Inc., “2012 IT Budget Planning Guide For CIOs, October 27, 2011 most decision-makers want IT to improve efficiency, streamline process, increase capacity for innovation 4Copyright © 2014 CA. All rights reserved.

5. No one definition of “DevOps” – but good starting points 1.Forrester Research, Inc., Improving The Ops In DevOps, July 21, 2011 2.Gartner, DevOps: Born in the Cloud and Coming to the Enterprise, Cameron Haight, Refreshed May 3, 2012; First Published October 27, 2010 3.451 Research, DevOps Mixing Dev, Ops, Agile, Cloud, Open Source and Business, Jay Lyman, March 3, 2010DevOps Mixing Dev, Ops, Agile, Cloud, Open Source and Business “A set of processes, methods, and systems for communication, collaboration, and integration among the IT functions responsible for application development, infrastructure and operations, and quality assurance; with the functions working together to produce fit-for-purpose and timely software products and services.” – Forrester 1 “DevOps is a concept originating largely from the cloud service industry, focusing on improving the effectiveness through collaboration of development and operations teams in response to tremendous online volume growth.” – Gartner 2 “An emerging set of principles, methods and practices for communication, collaboration and integration between software development (application/ software engineering) and IT operations (systems administration/ infrastructure) professionals.” - Wikipedia, April 2012 “A software development method that stresses communication, collaboration and integration between software developers and Information Technology (IT) professionals.” - Wikipedia, July 2012 “DevOps is the blending of tasks performed by a company's application development and systems operations teams.” – TechTarget “The blending roles and benefits of an integrated approach when it comes to the ‘development’ of an application through testing and QA to production and ‘operations.’” – The 451 Group 3 5Copyright © 2014 CA. All rights reserved.

6. But What Does DevOps Actually Mean? “DevOps is the blending of tasks performed by a company's application development and systems operations teams.” – TechTarget “A software development method that stresses communication, collaboration and integration between software developers and Information Technology (IT) professionals.” - Wikipedia, July 2012 “DevOps, a portmanteau of = development and operations, means to close gaps [between development and operations] by aligning incentives and sharing approaches for processes and tools” – DevOps for Developers, By Michael Hüttermann - Apress, Sep 12, 2012. “An emerging set of principles, methods and practices for communication, collaboration and integration between software development (application/ software engineering) and IT operations (systems administration/ infrastructure) professionals.” - Wikipedia, April 2012 methods communication integration collaboration development operations Copyright © 2014 CA. All rights reserved.6

7. But What Does DevOps Actually Mean? for improving methods, communication, and integration between collaboration and development operations Copyright © 2014 CA. All rights reserved.7

8. Fundamental Conflict Between Dev and Ops Copyright © 2014 CA. All rights reserved.8

9. Scrum and DevOps Plus …  Change in Culture  Continuous Delivery and Automation  Frequent feedback mechanism  Ultimately deliver faster and safer Philosophy 1 Communication 2 Integration 3 Collaboration 4 Development 5 Operations 6 Copyright © 2014 CA. All rights reserved.9

10. ScrumOps Copyright © 2014 CA. All rights reserved. Scrum Teams and DevOps practices at one level on a single platform Theme Unification of Application Delivery from Scrum teams and Operations Feature As a business executive for application service delivery, I would like to have a end-to-end view of planning, execution, development, and deployment of applications from scrum and operations teams in one view, so that our customers realize business value without pain and interruption. Story Adoption of best practices and improving the processes by continually inspect and adapt Tasks 10

11. ScrumOps: Best Practices Copyright © 2014 CA. All rights reserved. Unified Planning for Application Development and Deployment Agile Planning Service Virtualization and Integrated Automation Virtualization and Automation Shared understanding between Scrum teams and Operations Common Language and Vocabulary Theme of DevOps in the scrum teams Done criteria Doneness and Acceptance 11

12. ScrumOps: Agile Planning Review the backlog with Operations Architecture and Design in consideration of DevOps Story writing with shared understanding Unified Release Plan Early identification of dependencies and hand overs Copyright © 2014 CA. All rights reserved.12

13. ScrumOps: Virtualization and Automation Virtualization Removes constraints Virtualization Increases Velocity Virtualization can Create Realistic Test Environment Automation Increase Test Coverage Functional and Non-functional Testing within Sprint Copyright © 2014 CA. All rights reserved.13

14. ScrumOps: Vocabulary and Semantics Communication and Collaboration Visibility of Operation’s tools, process, and methods Visibility of scrum team’s engineering practices Copyright © 2014 CA. All rights reserved.14

15. ScrumOps: Scaling Scrum Practices System Admin/Infrastructure Engineer part of the scrum team Done criteria includes deployment on customer alike environment Break down tasks to include DevOps practices Integrate Engineering Practices of Operations into Scrum Invest and Improve on Process and Tools Copyright © 2014 CA. All rights reserved.15

16. 16 ScrumOps: Organization Culture and Team Behavior Copyright © 2014 CA. All rights reserved. Transparency in role behavior and transparency in process and tools. Building trust over individual insecurities Emphasizing on solution mindset over argument on difficult use case Thinking beyond each other’s role and responsibility – It’s all about taking ownership

17. The Humane ScrumOps Breaking down silos between Scrum Teams and IT Operations Collaboration at all levels – CIO to CDO and Scrum Team Member to Infrastructure Engineer Unified Planning and Execution for Scrum and Operations Transparency across processes and tools on each side Trust – in each other, in technology, in process Copyright © 2014 CA. All rights reserved.17

18. 18 Acknowledgement/References: Copyright © 2013 CA. All rights reserved. CA Technologies Corporate Communications http://www.ca.com/us/lpg/devops-portfolio.aspx The Scrum Primer

19. Thank You! Q&A 19