Scaling DevOps in Large Enterprises – A Pragmatic Approach

Bosphorus - I

As we are seeing an increase in enterprise agile transformation across domains around the world, the need for scaling technical practices is rising higher. And there is very little that an organization can achieve without DevOps practices. A recent study by Coleman Parkes Research shows that:

Advanced agile adopters can respond to new opportunities 40% faster
Advanced DevOps adopters can deliver new capabilities to market 42% faster
88% of advanced agile adopters and 87% of advanced DevOps adopters achieve tangible improvements in customer experience
Agile plus DevOps improves new business growth by 63% more than agile alone
Agile plus DevOps improves operational efficiency by 41% more than agile alone

Which simply goes to show that the organization can leverage DevOps for making their agile approach more successful.

And research items like these have helped organizations realize the value of implementing DevOps along with their agile transformation journey.

This paper focuses on multiple large agile transformation from my journey as an enterprise coach has been part of and what worked and what failed us in “how to DevOps”. It will predominantly focus on following items:

1. Centralized vs de-centralized devops models – While an organization used a centralized approach in implementing their devops strategy with only scope for execution innovation, other organizations used de-centralized approach allowing teams to experiment on various techniques and tools and cross-pollinate the best practices to other teams. While both approaches are correct, each comes with its own challenges.
2. Challenges for scaling devops – culture, legacy systems, systems thinking, collective ownership, right metrics for measuring success were the top 5 challenges across the organizations.
3. Best practices – standardizing common practices (without focusing on compliance), emergent model, automation, leveraging cloud and optimization were some of the best practices we learnt in our journey
4. There is role for everyone – understanding our organization structure and culture and playing on your org’s strengths and inclusive culture makes the devops journey fun and successful
5. Innovation – no organization has ever achieved anything significant without risks and failures and trying out new things. Including innovation as part of the journey and not as a line item brings different energy into the devops transformation

Learning Outcome:

1. Understanding centralized, de-centralized and blended models for “how to devops”
2. Common challenges and solutions for these challenges
3. Some best practices which can be low-hanging fruits in your journey
4. Innovation accounting and its role in devops transformation

Session plan:

It will be a 30 or 45 minutes ppt based session with the following agenda:

1. Introduction
2. Our models
3. Challenges
4. Best Practices
5. Where are we now?