Is DevOps = Agile++?

This is probably the most frequently asked question that I have received.

In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:

– We are already agile. all this sounds just like agile. how is it different and why do we need DevOps

The simple answer is Yes and No.

First the Yes part – similarities:

Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.

Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.

Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!

Now, for the No part:

DevOps is more of an organizational agility approach.

DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.

In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.

Techniques and standards such as Scrum, Kanban [or a combination – Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.

A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.

When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.

The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.

Taking a DevOps approach will influence many current systems and practices – including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.

To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.

Leadership, Communication; Culture
What do you think?

4 Responses

  1. Hi Shiv, I can relate to this, it is a real different world.
    I was invited a few times to address students appearing for CET exams as an industry person and found it challenging to connect with them. I was able to connect somewhat as one of their concern was what if they do not get into a good college, which I was able to address by sharing real life examples.

    1. Thanks Vasu. College “brand” no doubt helps early on in work life – corporate doors open more easily. But down the line, it is people’s motivation and track record that helps build careers. I am sure we have all seen examples affirming this. I have stressed with the mentees that I work with. An aside, the mentorship program I am involved in spans 4-5 months and so, I have had time to work on the “connect”! Yes – takes time and effort.

  2. Hi Shiv – very well written – thanks for the write-up.
    Many years ago I was a volunteer mentor for a couple of youth as part of Dream A Dream’s life skills mentoring program. This was in person mentoring where the mentee and I would meet periodically (usually on a weekend) and discuss general topics. There was no prescribed structure though all mentors did go thru a few hours of in person training. Based on that experience I can corroborate that it takes time for the mentee to open up, especially in that case given their lack of confidence in expressing in English which was the recommended language for communication. Switching to Tamil (in one case where the mentee was from Tamil Nadu) helped.
    Can also relate well to your point on swings in mood and engagement level of the mentee and the need for mentor to shift gears accordingly.

    I am sure the mentees are benefiting a lot from your vast and varied experience – hope you will come back to mentor more such students after you complete the current mentorships and possibly take a break!

Leave a Reply

What to read next