Copyright © 2017. Tech Mahindra. All rights reserved.

1
Copyright © 2017. Tech Mahindra. All rights reserved. 2
 What Is DevOps?

Why DevOps?

Business Perspective

Solution for the conflict

DevOps Principles Objectives

along with Philosophy

Benefits

Technical stack

TechM Offerings
Copyright © 2017. Tech Mahindra. All rights reserved. 3
Copyright © 2017. Tech Mahindra. All rights reserved. 4
What is DevOps
 DevOps is an Approach based on Lean and Agile principles in which Business
Owners and The Development, Operations and Quality Assurance
departments collaborate to deliver software in a continuous manner that
enables the business to more quickly seize market opportunities and reduce
the time to include customer feedback.

Copyright © 2017. Tech Mahindra. All rights reserved. 5

 Few More definitions of “DevOps”
 Devops is a cultural movement that changes how individuals think about
their work, values the diversity of work done, supports intentional
processes that accelerate the rate by which businesses realize value, and
measures the effect of social and technical change.

 It is a way of thinking and a way of working that enables individuals and

organizations to develop and maintain sustainable work practices.

 It is a cultural framework for sharing stories and developing empathy,

enabling people and teams to practice their crafts in effective and lasting
ways.

 The heart of devops starts with people working not only as groups but as teams
with a desire for mutual understanding

Copyright © 2017. Tech Mahindra. All rights reserved. 6

DevOps is not New!
 Traditionally when software was being made in-house, DevOps was already in
practice

 Mostly team of developers employed in-house were collecting requirements

from users from same organisation and develop a software

 They were also providing Application Support

Copyright © 2017. Tech Mahindra. All rights reserved. 7

THE CONVERGENCE OF DEVOPS The Rugged Computing
Movement

The Lean startup and UX 2011

Movement

The Toyota Kata 2011

Movement

2009
The Continuous Delivery
Movement
The Velocity Conference
Movement
2009
The Agile Movement 2008-09
The Lean
Movement 2001
1980

2013-14
Copyright © 2017. Tech Mahindra. All rights reserved. 8
Copyright © 2017. Tech Mahindra. All rights reserved. 9
Why DevOps?
 DevOps is a response to the growing awareness that there is a
disconnect between what is traditionally considered development activity
and what is traditionally considered operations activity

 DevOps adoption is also being helped by factors such as:

– Wide availability of virtualized and cloud infrastructure

– Increased availability of data center automation and configuration

management tools

– Increased use of agile processes in software development

Copyright © 2017. Tech Mahindra. All rights reserved. 10

 Conflict Between Dev and Ops

Goal Reality
• Communication of Knowledge and • Distracted by day-to-day delivery
Integration of People pressures – 78%
• Better Process • Tools don’t integrate properly – 62%
• Reality-based Measurements • Lack necessary internal expertise – 56%

Copyright © 2017. Tech Mahindra. All rights reserved. 11

Why the disconnect?
 A combination of conflicting motivations, processes and tooling…
– Development teams are often incentivized on creating as much change
as possible in response to changing business needs while Operations
teams are measured according to the stability of the systems they
manage

– Full production readiness of software is usually not assessed until it is

too late as development teams have no access to production
environments due to Operations tight control over the build and release
of physical servers

– Business receives little real feedback on whether what is being built is

useful, is valuable until the first release, which may be many months
after project approval

– Development and operations usually have different funding models,

which creates challenges in measuring the cost of any system over its
lifecycle
Copyright © 2017. Tech Mahindra. All rights reserved. 12
 How and why was the “wall built”
 Typically Development was handled as part of new investment by IT
departments. It was budgeted out of Capital Expenses (Capex)

 Support on other hand was handled as part of sustenance and hence it was
coming from Operational Expenses. (Opex)

 Generally these 2 were handled by 2 different teams from customer end. It was
source of gap.

 Type of skills required for development were higher and hence expensive. On
other hand Support was a game of economy, hence there was thrust of cost
reduction.

 Development was handing over things in form of "Check Sheet" to operations.

 This resulted into a wall between Development and Operations.

Copyright © 2017. Tech Mahindra. All rights reserved. 13

 Where is the disconnect?

Development Operations

In context of their respective roles and KRA’s, both believe that they are doing
the right thing for the business… and in isolation they are both correct!

Copyright © 2017. Tech Mahindra. All rights reserved. 14

Copyright © 2017. Tech Mahindra. All rights reserved. 15
 Shorter time
to market

Faster value
realization

Copyright © 2017. Tech Mahindra. All rights reserved.

Cheaper
solutions

Simplified
processes

Repeatable
procedures

Copyright © 2013 CA. All rights reserved.

Elimination
of non
valued
Customer Expectations

tasks

One team
experience

Automation
17
 Current Delivery Challenges
Support
 Code working on development environment does not work in Production
 Ineffective handovers and knowledge transfer
 Many release failures
 Spurt in incident count after releases
 No time for RCA
 Complex manual processes, lack repeatability and speed

Infra
 High switch over time
 Unable to offer on demand capacity
 Inconsistent Development, Test and production environments

Overall
 A production defects leads to finger pointing between teams.
 Business loss due to blame games between different teams
 High cycle time (from request raised until deployed successfully)
 Teams work in silos requires to improve the collaboration across teams
 Poor visibility into dependencies across releases, versions
 Low morale
Copyright © 2017. Tech Mahindra. All rights reserved. 20
 Need of the hour
 Product focus (Adaptive)
 One team culture (Collaborative)
 Reduce waste (Lean mind set)
 Build In Quality (Quality focused)

 (Continuous) Incremental Delivery for faster value realization

Development

Operations - Operations –
Applications Infrastructure

Copyright © 2017. Tech Mahindra. All rights reserved. 21

Evolution of Agile
 Was Agile an Invention

 Was that evolved due to necessity

 Or was that natural next step?

Copyright © 2017. Tech Mahindra. All rights reserved. 22

Issue after Agile
 Blockage at Handshake with Operations.
 Dissociation of the application lifecycle. Development works at one pace
and Operations works at another.

 Back to Square One. [Though Agile still Waterfall]

Copyright © 2017. Tech Mahindra. All rights reserved. 23

 Why Wall lost the relevance
 The development is no more pure development

 It is more of assembly products and deliver business requirement

 Hence lot of development is like configuration
 Application Support has 2 parts
– Configuration Changes
– Handle Software Bug

 This reduces the gap between Dev and Ops

 Agile brought thrust on bringing functionality to users fast.

Copyright © 2017. Tech Mahindra. All rights reserved. 24

Copyright © 2017. Tech Mahindra. All rights reserved. 25
DevOps is all about breaking the wall
 It was going to happen!

 Movement of Bespoke solutions to System Integrations

 Movement from Waterfall to Agile

 The next step is DevOps

Development

Operations - Operations –
Applications Infrastructure

Copyright © 2017. Tech Mahindra. All rights reserved. 26

Copyright © 2017. Tech Mahindra. All rights reserved. 28
Principles of DevOps
 Collaboration

 Breakdown Barriers

 Work as one team end to end

 Treat Infrastructure as a code

 Support Business and IT Agility

 Automate Everything
 Test Everything

 Measure and Monitor Everything

Copyright © 2017. Tech Mahindra. All rights reserved. 29

Goals of DevOps
 React and make changes more rapidly
 Speeding up time to deliver value
 Build quality in
 Test frequently against production like systems
 Reduce waste and rework
 Reducing cycle time from RFC to feature availability

 Get quick feedback

 Frequent monitoring
 Release as per business demand

Copyright © 2017. Tech Mahindra. All rights reserved. 30

DevOps Philosophy
DevOps is a philosophy with focus on

 Product-centric approach

 Continuous Incremental delivery for faster value realization

 Build Quality In

 One team culture

 Lean mindset

Copyright © 2017. Tech Mahindra. All rights reserved. 31

Product Centric Approach
 Own the Product
 Product Vision & Roadmap

 Minimum Viable Product

 Minimum Viable Experience
 Minimum Marketable Product
 Incrementally adding features

PRODUCT CENTRIC

Copyright © 2017. Tech Mahindra. All rights reserved. 32

Incremental Delivery
 Iterative
 Incremental

 Fast value realization

 Build in slices
 Openness for Changes

Copyright © 2017. Tech Mahindra. All rights reserved. 33

 One Team Culture
 Succeed as a team or fail as team
 Foster innovation

 Common understanding of team vision,

mission and success criteria

 Team owns the Product

 Breakdown silos
 Empower the team

 Self Organizing team

 Accountability

 Performance measurement of the team

rather than of individuals
Copyright © 2017. Tech Mahindra. All rights reserved. 34
Lean Mindset
 Increase Customer Value

 Eliminate Waste

 Reduce Cycle Time

 Shared Learning

 Avoid Batching
 Theory of Constraints

Copyright © 2017. Tech Mahindra. All rights reserved. 35

Built-In Quality
 Test Driven Development
 Frequent integration

 Frequent testing
 Fail fast (early)
 Refactoring
 Feedback

 Early warning systems

Copyright © 2017. Tech Mahindra. All rights reserved. 36

 DevOps Eco System
Infrastructure Team, Development Teams, Testing Teams, Enterprise Architecture, Business Planners, Security Administration, Third party suppliers, External
systems, Service Desk, Prod Operations, Senior Management and Line of Business

Feedback Loop

Line of Business Develop and Test Operations

Release Operation
Project &
Business Requirement Design & control & &
Release Build & CI Testing
Planning Management Develop Change Monitorin
Planning
Management g

DevOps

Continuous Delivery
Continuous
Agile Development Deployment
Continuous Continuous
Continuous Integration
Planning Testing

Project & SCM Artifact PaaS App & Env.

Requirements Database
Release Plans Repository On-Demand configuration
Cloud

Security, Governance and Reporting

Copyright © 2017. Tech Mahindra. All rights reserved. 37
DevOps Myths
 DevOps Is Only for “Born on the Web” Shops

 DevOps Is Operations Learning How to Code

 DevOps Is Just for Development and Operations
 DevOps Isn’t for ITIL Shops

 No Cloud Means No DevOps

 DevOps Isn’t for Large, Complex Systems
 DevOps Is Only about Communication
 DevOps Means Continuous Change Deployment

Copyright © 2017. Tech Mahindra. All rights reserved. 38

Copyright © 2017. Tech Mahindra. All rights reserved. 39
Copyright © 2017. Tech Mahindra. All rights reserved. 40
Benefits of DevOps
Puppet Labs report 2018
 24x more likely to make monitoring and alerting configurable by teams.

 Highly evolved organizations are 23x more likely to reuse deployment

patterns.

 Highly evolved organizations are 44x more likely to reuse testing patterns.

 Highly evolved organizations are 44x more likely to contribute to other team’s
tooling.

 Highly evolved organizations are 27x more likely to use configuration

management tools.

Copyright © 2017. Tech Mahindra. All rights reserved. 41

DevOps Market view
DevOps is no longer a mere fad or buzzword but
an understood set of practices and cultural
Key Drivers patterns. People turn to DevOps… to improve their
organization performance, revenues, profitability
and other measurable outcomes.

Source: State of DevOps report 2016, Puppet labs

“DevOps adoption is at a tipping point.

Adopting DevOps practices improves
performance, and the longer those
practices are in place, the greater the
performance advantage. Waiting to implement
is no longer an option”

Source: 2013-state-of-devops-report, PuppetLabs

Demand for DevOps Skills is

Growing…
Job listings for "DevOps“ increased by
2046% from Jan 2012 to Sep 2016
([Link])

Copyright © 2017. Tech Mahindra. All rights reserved. 42

Copyright © 2017. Tech Mahindra. All rights reserved. 43
 DevOps Tools

Copyright © 2017. Tech Mahindra. All rights reserved. 44

Copyright © 2017. Tech Mahindra. All rights reserved. 45
 DevOps Tools
COLLABORATION TOOLS PLANNING TOOLS PRODUCTIVITY TOOLS
1. Slack 1. Asana 1. Vagrant
2. Trello 2. Clarizen 2. Docker
3. Hip Chat 3. Jira
4. Flow Dock
SOURCE CODE ISSUE TRACKING
MANAGEMENT TOOLS CD TOOLS
TOOLS 1. Go
1. Git 1. Bugzilla
2. Subversion 2. Chef Delivery
2. Jira
3. Mercurial 3. Lean testing
4. Github 4. Mantis
5. Bitbucket DEPLOYMENT TOOLS
6. Perforce 1. Go
2. XL Deploy
CONFIGURATION MANAGEMENT 3. uDeploy
TOOLS 4. JuJu
1. Chef 5. Rundeck
2. Ansible 6. AWS Code Deploy
3. Puppet
[Link]
Saltstack© 2017. Tech Mahindra. All rights reserved. 46
 DevOps Tools Contd…….
REPOSITORY TOOLS CI TOOLS BUILD TOOLS
1. Nexus 1. Jenkins 1. Ant
2. Artifactory 2. Bamboo 2. Maven
3. Archiva 3. Travis 3. Gradle
4. Package Drone 4. TeamCity 4. Rake
5. Github 5. Hudson 5. MSbuild
6. CodesShip [Link] Visual
TEST AUTOMATION TOOLS 7. Circle CI 7. Pybuilder
1. Selenium 8. Cruise Control
2. UFT 9. Shippable
3. Appium
4. Jmeter
DOCKER CLUSTERING TOOLS
5. Load runner
1. Kubernetes
MONITORING TOOLS 2. Docker Swarm
1. ELK stack 3. Mesos
2. Sensu 4. Helm – Kubernetes Package Manager
3. Nagios
4. New Relic
5. Data Dog
6. App Dynamics
7. Splunk
Copyright © 2017. Tech Mahindra. All rights reserved. 47
Copyright © 2017. Tech Mahindra. All rights reserved. 48
Copyright © 2017. Tech Mahindra. All rights reserved. 49
 Agile & DevOps Platform (ADOPT)
ADOPT Features
 focused on shortening the overall delivery cycle with focus on automation of all
possible value streams including deployment automation
 it suggests an approach of release readiness which includes ensuring quality of
the output at every stage
 it also encourages the long term view of creating just enough documentation which
will enable business continuity
 reduce risk of release because of fully automated release and frequent releases

ADOPT Benefits
 Continuous delivery as a service
 Cloud ready allowing both development and deployment over the cloud
 ADOPT platform comes with option of multiple native integrated tools and a open
architecture allowing integration with existing tools

ADOPT platform helps to improve the following business metrics

 Time to Market by ~15% to 20%
 Improve efficiency by ~10% to 15%
 Reduce cost by ~ 15% to 20%
Copyright © 2017. Tech Mahindra. All rights reserved. 50
 ADOPT Platform – Collabnet Solution

Copyright © 2017. Tech Mahindra. All rights reserved. 51

Copyright © 2017. Tech Mahindra. All rights reserved. 52
 Thank You
Visit us at [Link]

Disclaimer
Tech Mahindra Limited, herein referred to as TechM provide a wide array of presentations and reports, with the contributions of
various professionals. These presentations and reports are for informational purposes and private circulation only and do not
constitute an offer to buy or sell any securities mentioned therein. They do not purport to be a complete description of the markets
conditions or developments referred to in the material. While utmost care has been taken in preparing the above, we claim no
responsibility for their accuracy. We shall not be liable for any direct or indirect losses arising from the use thereof and the viewers are
requested to use the information contained herein at their own risk. These presentations and reports should not be reproduced, re-
circulated, published in any media, website or otherwise, in any form or manner, in part or as a whole, without the express consent in
writing of TechM or its subsidiaries. Any unauthorized use, disclosure or public dissemination of information contained herein is
prohibited. Unless specifically noted, TechM is not responsible for the content of these presentations and/or the opinions of the
presenters. Individual situations and local practices and standards may vary, so viewers and others utilizing information contained
within a presentation are free to adopt differing standards and approaches as they see fit. You may not repackage or sell the
presentation. Products and names mentioned in materials or presentations are the property of their respective owners and the
mention of them does not constitute an endorsement by TechM. Information contained in a presentation hosted or promoted by
TechM is provided “as is” without warranty of any kind, either expressed or implied, including any warranty of merchantability or
fitness for a particular purpose. TechM assumes no liability or responsibility for the contents of a presentation or the opinions
expressed by the presenters. All expressions of opinion are subject to change without notice.

Copyright © 2017. Tech Mahindra. All rights reserved. 53

Copyright © 2017. Tech Mahindra. All rights reserved. 54