DevOps Culture: Connecting the Dots

- MAHESH SUBRAMANIAN

2

A technocrat with rich experience in the field of Project & Program Management, Presales/ Technical Sales

Management, Technical/Service Management, Product Management and People/Resource Management.

Over 20 years in IT, with 17 years in ALM and DevOps.

Currently the Global Head of Engineering Ops – Processes and Tools and Cultural Transformation Agent

and Catalyst at Misys

Mahesh Subramanian Global Head – Engineering

Operations, Processes & Tools

3

Abstract

DevOps is a reality. However, this needs more than just automation

A combination of man, machine and methods

With involvement of man, needs a shift in thinking and operations

Should we respect the system or break the rules

Definition of Done

Coded

Checked-in

Reviewed

Built

Tested

Demoed

Source: scrum.com: Improving the Profession of Software Development

Definition of Done

Our highest priority is to satisfy the customer

through early and continuous delivery of valuable software.

Agile Manifesto

Done === Released / Deployed

Characteristics

Build

Deploy

Measure

Data

Learn/

Feedback

Ideas

Speed with quality

Characteristics

Speed with quality

Minimum viable product (not full product but minimum shippable – avoid product creep)

Smaller, focused teams – collaborative (cont. delivery)

Loosely coupled architecture (like componentization)

Minimizing handoffs (Rugby vs Relay approach)

Delivering in smaller batches

Deliver and feedback loops

Transparency (E-2-E)

Shift Left

Lesser number of meeting

Enabling Self service to dev (shift left) – dev have better context

Trust

Automating Testing

Break the Wall

I want change I want stability Ops does not understand

Dev does not understand

9

Questions?

10

11

Thank You