<p>Agile Software Development is not <em>required</em> to do DevOps, but I believe the argument can be made that the value proposition for DevOps is often a lot lower without Agile.</p>

<p>DevOps is a lot of things, but <em>automation</em> is a central theme.  The value of automation increases in direct proportion to the frequency with which Development creates new releases.  Frequent deployment has a positive impact on certain types of products, specifically consumer applications.  High velocity all the way through the software delivery lifecycle returns value for each iteration (anyone seen the CA ad where the zombies want new features in their apps?)</p>

<p>Without Agile, high-frequency releases are extremely difficult, if not impossible.  If the Development team is releasing software once a quarter, or twice a year, DevOps can still automate the process, but then what is the point?  The investment in time, training, and resources to adopt DevOps may be partly returned in quality, however, the best value is in maintaining high velocity throughout the delivery lifecycle.</p>

<p>One could also argue that if you're going to adopt DevOps, why <em>wouldn't</em> you also adopt Agile?  The principles that make them both work, work well together.  Practicing DevOps by itself, without Agile, could create an imbalance between Ops and Dev, in which Ops is outperforming Dev for service delivery.</p>

CC BY-SA 3.0
2017-03-05T11:57:53.200Z
2017-03-05T11:57:53.200Z
Dave Swersky
<h1>NO</h1>

<p>I would argue that <em>Mature</em> DevOps operation, does require a <em>Mature</em> Agile process. You are unlikely to be able to get the full confidence to continuously deploy or allow your developers to initiate the deployment process without a <em>mature</em> Agile process in place.</p>

<p>However, I believe it is very important to make it clear that an organisation does NOT need to adopt their agile process before building up their DevOps culture and infrastructure. In fact, I would argue that it is actually easier to adopt Agile once you have some basic DevOps working in your company. Rather than Agile being a prerequisite for DevOps, I would suggest that DevOps be used to help advance your agile implementation.</p>

CC BY-SA 3.0
2017-03-05T11:54:23.650Z
2017-03-05T11:54:23.650Z
avi
<p>At the Agile 2008 conference, Andrew Clay Shafer and Patrick Debois <a href="https://en.wikipedia.org/wiki/DevOps#Etymology" rel="nofollow noreferrer">discussed</a> "Agile Infrastructure". This was the start of the DevOps movement.</p>

<p>But while DevOps has it's roots in Agile Manifesto, the fact is that it is not strictly required for the development teams to be Agile. Most of the <a href="https://en.wikipedia.org/wiki/Agile_software_development#Agile_principles" rel="nofollow noreferrer">Agile Principles</a> are indeed important to follow, but no specific <a href="https://www.versionone.com/agile-101/agile-methodologies/" rel="nofollow noreferrer">Agile Methodology</a> is prescribed and if the development team can come up with their own way of working, while keeping more or less to the Agile Principles, you can realize the benefits.</p>

CC BY-SA 3.0
2017-03-05T08:20:27.673Z
2017-03-05T08:20:27.673Z
Jiri Klouda
<p>Not necessarily; as the other answers have stated, Agile methodologies and DevOps mentality can build off of each other, but to me, DevOps is broader than either agile or lean development efforts.  Companies that adopt DevOps look at the entire value stream, including operations, development, product design, marketing, security etc... the movement can originate within any silo with the intent of dismantling barriers.</p>

CC BY-SA 3.0
2017-09-27T18:21:45.687Z
2017-09-27T18:21:45.687Z
Stuart Ainsworth
<p>IMHO it doesn't <em>need</em> to.</p>

<p>From <a href="https://en.wikipedia.org/wiki/DevOps" rel="nofollow noreferrer">DevOps</a> (emphasis mine):</p>

<blockquote>
  <p>DevOps (a clipped compound of "software DEVelopment" and "information
  technology OPerationS") is a term used to refer to a set of practices
  that emphasize the collaboration and communication of both software
  developers and information technology (IT) professionals while
  automating the process of software delivery and infrastructure
  changes.<a href="https://en.wikipedia.org/wiki/DevOps" rel="nofollow noreferrer">1</a>[2] It aims at establishing a culture and environment where
  building, testing, and releasing software <strong>can happen</strong> rapidly,
  frequently, and more reliably.</p>
</blockquote>

<p>I highlighted <code>can happen</code> as it is not <code>must happen</code>.</p>

<p>Nothing in the above description actually <strong>requires</strong> an agile development methodology. </p>

<p>But I suspect often transitions towards DevOps often incorporate insertion of agile methodologies in the development process as they really fit well together.</p>

CC BY-SA 3.0
2017-03-05T07:59:02.013Z
2017-03-05T07:59:02.013Z
Dan Cornilescu
<p>The concept of the devops has arisen precisely because of the proliferation of agile, so it is appropriate to use the devops approaches in a agile.
For example, with agile, continuous integration is used (which is part of the devops approach), orchestration of services and containers for testing and rolling out new releases for test and prod environments.</p>

CC BY-SA 3.0
2017-08-18T09:16:40.820Z
2017-08-18T09:16:40.820Z
Quarind
<p><a href="https://en.wikipedia.org/wiki/Agile_software_development" rel="nofollow noreferrer">Agile software development</a> is the methodology of choice for software shops today. But there are still organisations which are not practicing Agile in their software development, who might be interested in adopting DevOps.</p>

<p>When I say Agile Software Development, I mean any offspring that came out of the <a href="http://agilemanifesto.org/" rel="nofollow noreferrer">Manifesto for Agile Software Development</a>. Such as <a href="https://en.wikipedia.org/wiki/Extreme_programming" rel="nofollow noreferrer">Extreme Programming</a>, <a href="https://en.wikipedia.org/wiki/Scrum_(software_development)" rel="nofollow noreferrer">Scrum</a>, <a href="https://en.wikipedia.org/wiki/Lean_software_development" rel="nofollow noreferrer">Lean Software Development</a> and others.</p>

<p>Is Agile software development a mandatory prerequisite of adopting DevOps on an organisation level?</p>

CC BY-SA 3.0
2017-10-10T19:13:56.337Z
Very relevant article on why Agile doesn't work and how DevOps fits into the picture was posted at https://hackernoon.com/why-isnt-agile-working-d7127af1c552
Evgeny Zislis
CC BY-SA 3.0
2017-03-05T07:38:26.450Z
This question was created as http://devops.stackexchange.com/questions/73/how-is-devops-related-to-agile was downvoted as too broad.
Evgeny Zislis
CC BY-SA 3.0
2017-03-05T14:36:56.933Z
This is a very good and very valid question
Alexandre
<culture><agile>
Does my organization need adopt Agile Soft. Dev. before adopting DevOps?
Evgeny Zislis
# Does my organization need adopt Agile Soft. Dev. before adopting DevOps?

(Asked by: username_0 on 2017-03-05)

[Agile software development](https://en.wikipedia.org/wiki/Agile_software_development) is the methodology of choice for software shops today. But there are still organisations which are not practicing Agile in their software development, who might be interested in adopting DevOps.

When I say Agile Software Development, I mean any offspring that came out of the [Manifesto for Agile Software Development](http://agilemanifesto.org/). Such as [Extreme Programming](https://en.wikipedia.org/wiki/Extreme_programming), [Scrum](https://en.wikipedia.org/wiki/Scrum_(software_development)), [Lean Software Development](https://en.wikipedia.org/wiki/Lean_software_development) and others.

Is Agile software development a mandatory prerequisite of adopting DevOps on an organisation level?

**Tags:** culture, agile

> **Comments:**
> **username_0**: This question was created as http://devops.stackexchange.com/questions/73/how-is-devops-related-to-agile was downvoted as too broad.  
> **username_1**: This is a very good and very valid question  
> **username_0**: Very relevant article on why Agile doesn't work and how DevOps fits into the picture was posted at https://hackernoon.com/why-isnt-agile-working-d7127af1c552  

---

## 6 answers

### Answer by username_2 on 2017-03-05. Score: 8

Agile Software Development is not *required* to do DevOps, but I believe the argument can be made that the value proposition for DevOps is often a lot lower without Agile.

DevOps is a lot of things, but *automation* is a central theme. The value of automation increases in direct proportion to the frequency with which Development creates new releases. Frequent deployment has a positive impact on certain types of products, specifically consumer applications. High velocity all the way through the software delivery lifecycle returns value for each iteration (anyone seen the CA ad where the zombies want new features in their apps?)

Without Agile, high-frequency releases are extremely difficult, if not impossible. If the Development team is releasing software once a quarter, or twice a year, DevOps can still automate the process, but then what is the point? The investment in time, training, and resources to adopt DevOps may be partly returned in quality, however, the best value is in maintaining high velocity throughout the delivery lifecycle.

One could also argue that if you're going to adopt DevOps, why *wouldn't* you also adopt Agile? The principles that make them both work, work well together. Practicing DevOps by itself, without Agile, could create an imbalance between Ops and Dev, in which Ops is outperforming Dev for service delivery.


---

### Answer by username_3 on 2017-03-05. Score: 4

# NO

I would argue that *Mature* DevOps operation, does require a *Mature* Agile process. You are unlikely to be able to get the full confidence to continuously deploy or allow your developers to initiate the deployment process without a *mature* Agile process in place.

However, I believe it is very important to make it clear that an organisation does NOT need to adopt their agile process before building up their DevOps culture and infrastructure. In fact, I would argue that it is actually easier to adopt Agile once you have some basic DevOps working in your company. Rather than Agile being a prerequisite for DevOps, I would suggest that DevOps be used to help advance your agile implementation.


---

### Answer by username_4 on 2017-03-05. Score: 2

At the Agile 2008 conference, Andrew Clay Shafer and Patrick Debois [discussed](https://en.wikipedia.org/wiki/DevOps#Etymology) "Agile Infrastructure". This was the start of the DevOps movement.

But while DevOps has it's roots in Agile Manifesto, the fact is that it is not strictly required for the development teams to be Agile. Most of the [Agile Principles](https://en.wikipedia.org/wiki/Agile_software_development#Agile_principles) are indeed important to follow, but no specific [Agile Methodology](https://www.versionone.com/agile-101/agile-methodologies/) is prescribed and if the development team can come up with their own way of working, while keeping more or less to the Agile Principles, you can realize the benefits.


---

### Answer by username_5 on 2017-09-27. Score: 2

Not necessarily; as the other answers have stated, Agile methodologies and DevOps mentality can build off of each other, but to me, DevOps is broader than either agile or lean development efforts. Companies that adopt DevOps look at the entire value stream, including operations, development, product design, marketing, security etc... the movement can originate within any silo with the intent of dismantling barriers.


---

### Answer by username_6 on 2017-03-05. Score: 1

IMHO it doesn't *need* to.

From [DevOps](https://en.wikipedia.org/wiki/DevOps) (emphasis mine):

> DevOps (a clipped compound of "software DEVelopment" and "information
> technology OPerationS") is a term used to refer to a set of practices
> that emphasize the collaboration and communication of both software
> developers and information technology (IT) professionals while
> automating the process of software delivery and infrastructure
> changes.[1](https://en.wikipedia.org/wiki/DevOps)[2] It aims at establishing a culture and environment where
> building, testing, and releasing software **can happen** rapidly,
> frequently, and more reliably.

I highlighted `can happen` as it is not `must happen`.

Nothing in the above description actually **requires** an agile development methodology.

But I suspect often transitions towards DevOps often incorporate insertion of agile methodologies in the development process as they really fit well together.


---

### Answer by username_7 on 2017-08-18. Score: 1

The concept of the devops has arisen precisely because of the proliferation of agile, so it is appropriate to use the devops approaches in a agile.
For example, with agile, continuous integration is used (which is part of the devops approach), orchestration of services and containers for testing and rolling out new releases for test and prod environments.


---

