Enterprise Dev Ops NO SILO NO SOLO NO

Enterprise Dev. Ops NO SILO… NO SOLO… NO BOZO ! * This is not the full deck but a glimpse of the presentation for ideation © © 2015 SAPIENTGLOBAL MARKETS 2015 SAPIENT GLOBAL 1

What is Dev. Ops Development team is responsible for adding new features in the software Operation team is responsible for keeping the system stable and running Dev Ops DEVOPS IS THE UNION OF PEOPLE, PROCESS AND PRODUCTS TO ENABLE CONTINUOUS DELIVERY OF VALUE TO OUR END USERS © 2015 SAPIENT GLOBAL MARKETS 2

You build it, you run it. - Werner Vogels (CTO, Amazon) © 2015 SAPIENT GLOBAL MARKETS 3

Dev. Ops DEV PLAN CODE BUILD OPS TEST RELEASE DEPLOY OPERATE Dev. Ops VALUE Continuous Delivery Continuous Integration Agile Development COLLABORATION © 2015 SAPIENT GLOBAL MARKETS 4

Dev. Ops vs. Enterprise Dev. Ops 1 -10 50 -500 5 -20 Number of Environments 100 -1000 1 -10 Years of Operation 30+ 1 -100 Size of IT Team 500 -2000 0 -1 No. of Acquisitions 25 (1/month) Ironic T-shirts, Jeans Startup Number of Apps Default Attire Business Casual Enterprise When software releases fail… What could possibly go wrong? Customers unable to purchase startup t-shirts for work. Someone has to call up your 10 customers to apologize. Banks fail. CEO has to address failure in CNBC interview. © 2015 SAPIENT GLOBAL MARKETS 5

Key Business Values Time to Market Cost Efficiency Higher Stability Frequent Releases Production Ready Code Reduced cycle times and higher deploy rates Increasing automation eliminates effort, thereby significantly reducing labor costs All changes can be tested against the entire canonical software system resulting in higher stability Deliver features more often - Automating the process removes the operational constraint Releasing software does not require additional effort, version is always ready for release © 2015 SAPIENT GLOBAL MARKETS 6

Enterprise Dev. Ops Our Model • Organization Structure • Immutable Infrastructure • Collaborate • Automated Provisioning • Tools • Monitoring & Alerting • Conway’s law • Single Responsibility Capability • Containers • Continuous Integration • Automated Testing • Automated Deployment © © 2015 SAPIENTGLOBAL MARKETS 2015 SAPIENT GLOBAL 7

Pre Dev. Ops Structures Anti-Type A Separate Silos Dev Ops Anti-Type B Separate Dev. Ops Silos Dev. Ops Anti-Type C “We don’t need Ops” Dev. Ops © 2015 SAPIENT GLOBAL MARKETS 8

Dev. Ops Team Structures Type 1 Smooth Collaboration Dev Ops Type 2 Fully Embedded Dev Ops Type 3 Temporary Dev. Ops Team Dev. Ops © 2015 SAPIENT GLOBAL MARKETS 9

Tools Landscape Continuous Integration Build & Deploy CI Server Version Control Unit Testing Code Quality Configuration Management & Environment Provisioning Automated Acceptance NFR Testing Monitoring & Alerts Binary Management Log Monitoring Collab / Community Chat Project Lifecycle Management Source Control Application & Infra Monitoring Project & Support Management Service Desk Source Control Binary Management Productivity Add On © 2015 SAPIENT GLOBAL MARKETS 10

So what makes it work? NO SILO NO SOLO NO BOZO An organization is made of separate entities for legal, professional or historical reasons. This should not lead to silo mentality. Solo behaviors are often a selfish expression. Teamwork is always superior. No one is bigger than a team. No team is bigger than the company. We want people to have fun, to enjoy working together. But this is above all a serious place to work in and to deliver against our clients’ or company’s objectives with enthusiasm, passion and laughs. . . There is no room for bozos. © 2015 SAPIENT GLOBAL MARKETS 11