DevOps Demystified: Why It’s More Than Just Tools and How to Embrace Its True Value

Published on
3 minute read

When I think about DevOps, I often find myself reflecting on the misconceptions that surround it. As someone who has been a Microsoft MVP in Azure DevOps for 14 years, I’ve seen firsthand how the term “DevOps” can be misinterpreted. Many people, when they mention DevOps in my presence, are actually referring to Azure DevOps—the tools that come with it. But let me be clear: the tool is not the value. The tool is merely a means to surface or leverage the value that comes from the underlying idea of DevOps.

Understanding DevOps: More Than Just Tools

So, what is it that people think they know about DevOps but really don’t? The first thing to grasp is that DevOps is not a tool, a process, or even a practice. It’s an idea—a concept that originated in the realm of software engineering.

  • DevOps as an Idea: At its core, DevOps is about understanding how we can improve our engineering systems. It’s about asking critical questions:
    • How does our approach to Agile impact the way we create our products?
    • What changes can we make to shorten feedback loops?
    • How do we design our products with agility in mind?

These questions are essential for anyone looking to embrace the true spirit of DevOps.

The Relationship Between Agile and DevOps

While Agile focuses on the people and processes involved in software development, DevOps delves into the nebulous aspects of how we can enhance those processes through collaboration and integration. It’s not just about the tools we use; it’s about how we think about our work and the systems we create.

I remember having enlightening conversations with Sam Guggenheimer, one of the original minds behind Team Foundation Server (TFS) and later Azure DevOps. His vision was always forward-thinking, focusing on what we needed to support the idea of DevOps.

  • Tools as Support: TFS and Azure DevOps are products of that vision, not the driving force behind it. The tools are there to support the idea of DevOps, not to define it. This is a crucial distinction that many people overlook.

Shifting the Focus

The challenge lies in shifting our focus from the tools to the ideas they support. When we default to thinking about tools, we miss the bigger picture.

  • Embrace the Idea: Instead of asking, “What tool should I use for DevOps?” we should be asking, “How can I leverage the principles of DevOps to improve my team’s performance and product quality?”

This mindset shift is vital for anyone looking to truly understand and implement DevOps effectively.

Final Thoughts

In conclusion, DevOps is a powerful idea that can transform the way we approach software development. It’s about fostering a culture of collaboration, continuous improvement, and responsiveness to change.

If you’re interested in diving deeper into this topic or discussing Agile, Scrum, or DevOps further, I invite you to book a coffee chat with me through Naked Agility. I always enjoy engaging with others who are passionate about these concepts.

Thank you for taking the time to read my thoughts on DevOps. If you found this post helpful, please like, follow, and subscribe for more insights. I look forward to hearing your comments and continuing the conversation!

Why shouldn’t this? What do people know about DevOps but really don’t?

I, well, the first thing, especially for… I have been a Microsoft MVP in Azure DevOps for 14 years. So lots of people, when they say DevOps around me, they mean Azure DevOps. They mean the tooling, and that’s quite often the case with a lot of these… when they talk about the work, what they mean is Jira, right? The tool is not the value. The tool is just there to help you surface the value or leverage the value that comes with that idea.

So the thing that people know about DevOps but really don’t is that it’s not a tool. It’s not a process. It’s not a practice. It’s an idea, right? And it’s really that idea born very specifically in software engineering, right? I mean, that’s really where DevOps focuses.

Um, around how do we… if we’re talking about Agile and we’re talking about getting faster at doing stuff, what’s the impact of that on our engineering systems? What’s the impact of that on the way we create our product, the way we approach our product, the way we design our product? What is the impact that enables us to shorten those feedback loops?

Um, beyond just talking about it, right? Because Agile is the people and process part, and DevOps is the… wow, the nebulous part of the… not just the tools, man, that’s hard to describe, right?

Um, DevOps is just an idea, just like Agile’s just an idea. So tools may help you, but figuring out how you’re going to use those tools or how those tools work… I had some great conversations with a gentleman who was the almost the source of Team Foundation Server originally, Visual Studio Team Services, as it was called the first time round, and the ideas behind it, which is a gentleman called Sam Guggenheimer.

There’s a great Twitter account which is “What Would Sam Say?” which is his people that worked with him created because he would see all sorts of, I don’t know, clever and interesting and funny for the rest of us stuff.

Um, but Sam had this laser focus looking forward into the future. What do we need going forward, looking out into the future in order to support this idea of DevOps?

And TFS and his journey into Azure DevOps, right, is the result of that thinking, not the cause of that thinking, right? The tools are not the cause; the idea is the cause, and the tools are there to support it.

And that’s, I think, what people understand about DevOps but really, really don’t, because they always default to the tool, the tool, the tool. No, it’s default to the idea, and the tool supports that idea.

Um, and that’s where you want to be.

Thanks for watching the video. If you enjoyed it, please like, follow, and subscribe. I always reply to comments, and if you want to have a chat about this or anything else Agile, Scrum, or DevOps, then please book a coffee with me through Naked Agility.

Software Development Software Developers People and Process Pragmatic Thinking

Connect with Martin Hinshelwood

If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.

Our Happy Clients​

We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.​

Epic Games Logo
Lean SA Logo
Schlumberger Logo
Bistech Logo
Brandes Investment Partners L.P. Logo
Capita Secure Information Solutions Ltd Logo
Emerson Process Management Logo
Hubtel Ghana Logo
Qualco Logo
Jack Links Logo
Sage Logo
YearUp.org Logo
Lockheed Martin Logo
Philips Logo
Slaughter and May Logo
Slicedbread Logo
Workday Logo
Akaditi Logo
Royal Air Force Logo
Washington Department of Enterprise Services Logo
Washington Department of Transport Logo
Nottingham County Council Logo
Ghana Police Service Logo
Department of Work and Pensions (UK) Logo
Kongsberg Maritime Logo
Schlumberger Logo
MacDonald Humfrey (Automation) Ltd. Logo
Ericson Logo
Workday Logo
SuperControl Logo