An Agile Introduction to DevOps, Part I: What Is DevOps, Anyway?
This series is about DevOps and how it fits into the Agile world. In this post, we make an introduction and try to define what DevOps actually means.
Join the DZone community and get the full member experience.Join For Free
this series is about devops and how it fits into the agile world. i’ve given this as a workshop at lean agile scotland ( slides here ).
let’s start with what devops is. i went to the source of all knowledge, wikipedia, and the definition goes like this:
“a culture, movement, or practice that emphasizes the collaboration and communication of both software developers and other information-technology professionals while automating the process of software delivery and infrastructure changes.”
well, isn’t that vague?
also, it’s not really helpful. the dev is in there, sure, but ops is translated to it. developers have always needed and worked with it, so what happened on the way to paradise?
to the time machine!
in 2001, there was this little thing called the agile manifesto . it talked about working software, the result of team collaboration. if we apply this to the devops definition, we’ll notice a couple of things:
“a culture, movement or practice that emphasizes the collaboration and communication of both software developers and other information-technology professionals while automating the process of software delivery and infrastructure changes.”
obviously, the collaboration part is there. it evolves the original team aspect from the agile manifesto. you see, at the time of the manifesto (and the half decade before it, when the agile methodologies developed), the “team” definition was already expanding.
scrum defined the team as anyone who needs to be there to make sure that software is delivered. that meant developers, testers, and product owners (ok, that’s a separate role, but without pos, nothing meaningful gets delivered). today, we need more skills on the team. automation, deployment, preparing testing environments – this is a short list of examples that are required to make sure software works.
devops is really an extension of the “team” definition. we can think of it as new roles, but we shouldn’t.
we like role playing so much that we confuse skills with roles and come up with new (and somewhat dysfunctional) ideas for how work should be handed over rather than how it’s done.
we think of devops as a role or a team doing their work separately from what the developers and testers do. we think that devops is only about automation, and therefore try to hire, train, and upgrade people within these roles.
this is wrong. after so much work to create a true multi-disciplinary team, we’re putting up the walls again. the truth is, we need the skills in the team, not outside it.
so repeat after me: “separate devops teams are not agile”.
devops is not a role. it’s a set of…
99 skills but devops ain’t one
man, that devops skillset is huge. we are now handling a whole new set of complex problems that were either not there or were just beginning to rear their ugly head in the nineties. no wonder scrum didn’t define it.
we no longer put our software on 34 disks and ship them (thank god). we got cloud services, clusters, and orchestrations that we need to optimize for business operations. the accumulated knowledge (some of it only a couple of years young) is required in order to deploy and assure working software in production.
we need to set up environments in-house so we can develop and test even before we deploy it to the outside world. and those environments are not as complex as they are out there, so we need to simulate those external conditions in order to test properly. granted, we have better tools to manage those things. but we still need to keep up on the technologies and tools, implement them and upgrade them.
and if that wasn’t all, the risk implication of messing things in production have gone up. we can no longer shut down servers for the weekend to deploy our software without interruption. things need to keep running before, during, and after we flip the switch. on the other hand, the policy of it (or ops) drawing a line in the sand and telling the developers “you can’t touch our production servers” no longer works. we need better approaches to keep the business going.
working software is hard.
riddle me this
we need skills and knowledge to run things smoothly. they hold answers to questions and needs we have, but now we have questions we thought were answered:
- what is a software version?
- what defines a feature in versioning terms?
- what is the feature “ready for release”?
- what defines an environment? how is a testing environment different from a staging environment and how what risks and mitigation go with that?
- what is a rollback? to what version do we roll back when people are committing code to production every few seconds?
and that’s just the short list.
as the agile manifesto says, “we are uncovering better ways to develop software.” we are still early in the process of defining what devops really is, but we already know of the skills and knowledge we need now.
next time, we’ll see how agile principles and devops practices align towards the goal of working software.
Published at DZone with permission of Gil Zilberfeld, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.