Answers: <p>Instead of Continuous Integration and Continuous Delivery, I would define the definition of done as "<em>Active Continuous Improvement at all levels of the organisation</em>".</p>
  
  <p>The other topics like automated builds, CI/CD, etc... these are just milestones and most definitely not the ultimate goal for the organisation in its DevOps efforts.</p>
  
  <p>It does look like it might be "finished all DevOps" once you have an automated system with continuous integration. But in fact, even should you reach this stage, you will find plenty more to do.</p>
  
  <p>Getting to a state where most people in the organization are constantly looking to continuously improve is extremely hard. Inertia often gets in the way, both existing inertia, and new inertia once some improvements were accomplished.</p>
  
  <p>There is a lot to learn from Lean and from Theory of Constraints in this aspect. Both bodies of knowledge focus on the process of continuous/ongoing improvement and how to establish this process in an organization.</p>
  
Answers: CC BY-SA 3.0
Answers: 2017-08-11T17:46:28.770Z
Answers: I like this definition! DevOps is never actually "done", it is a continuous and active process. Thanks!
Answers: alecxe
Answers: CC BY-SA 3.0
Answers: 2017-08-12T04:45:30.963Z
Answers: Asking when DevOps is done is like asking when a man is done with thinking. The answer is the same. When it's all over.
Answers: Jiri Klouda
Answers: CC BY-SA 3.0
Answers: 2017-08-11T17:43:19.273Z
Answers: 2017-08-11T17:49:42.093Z
Answers: 2017-08-11T17:49:42.093Z
Answers: Evgeny Zislis
Answers: <p>Prior to DevOps, an Agile team's definition of "done" typically meant is was "done" for the sprint (and accepted by the product-owner at or before  the end of the sprint). In reality, there might be subsequent levels of testing/delivery/release-engineering before it was actually released &amp; deployed.</p>
  
  <p>From a DevOps perspective, the common saying is "Done means <em>deployed</em>" - the corresponding story or feature wouldn't go to the "done" column of the board until it was deployed to production environment.</p>
  
Answers: CC BY-SA 4.0
Answers: 2018-07-05T17:05:31.343Z
Answers: 2018-07-05T17:05:31.343Z
Answers: Brad Appleton
Answers: <p>DevOps is a continuous improvement in delivery cycles and meeting customer needs with top quality , less time and security without compromise on cost and performance. And of-course repeat the cycles with feedback from customers.</p>
  <p>Ideally there is <strong>NO</strong> getting it all <strong>&quot;Done&quot;</strong> on DevOps. This question is rather a tricky one because its similar to asking</p>
  <blockquote>
  <p>When are you done with development or sales of a software in  a Software
  company?</p>
  <p>Ans: Obviously once the company shuts down or you get kicked out !</p>
  </blockquote>
  <p>Similarly there is no <strong>Done</strong> for DevOps culture. Of course there are deliverable and mile stones which one needs to complete like automating mundane repeated tasks , CICD pipelines etc</p>
  <p>A very good explanation for DevOps given by IBM DevOps head.</p>
  <p><a href="https://www.youtube.com/watch?v=EIvOZA1HgHU" rel="nofollow noreferrer">https://www.youtube.com/watch?v=EIvOZA1HgHU</a></p>
  
Answers: CC BY-SA 3.0
Answers: 2017-08-12T03:17:29.730Z
Answers: 2017-08-12T03:17:29.730Z
Answers: 2020-06-18T08:28:10.803Z
Answers: Ameen Ibrahim Raffic - 'AIR'
Body: <p>I've being recently interviewed for a DevOps position. One of the questions I was asked was:</p>
  
  <blockquote>
    <p>What is your definition of "done" in the DevOps context?</p>
  </blockquote>
  
  <p>The question is rather broad, but, as I understand, the answer has to cover Automated builds &amp; tests as well as Continuous Integration &amp; Deployment &amp; Delivery. I am looking for general principles and ideas that can be used to define "Done".</p>
  
Tags: <continuous-integration><terminology><continuous-delivery>
Title: Definition of "Done" for DevOps
UserDisplayName: alecxe
ThreadText: # Definition of "Done" for DevOps
  
  (Asked by: username_0 on 2017-08-11)
  
  I've being recently interviewed for a DevOps position. One of the questions I was asked was:
  
  > What is your definition of "done" in the DevOps context?
  
  The question is rather broad, but, as I understand, the answer has to cover Automated builds & tests as well as Continuous Integration & Deployment & Delivery. I am looking for general principles and ideas that can be used to define "Done".
  
  **Tags:** continuous-integration, terminology, continuous-delivery
  
  
  ---
  
  ## 3 answers
  
  ### Answer by username_1 on 2017-08-11. Score: 12 | Accepted answer
  
  Instead of Continuous Integration and Continuous Delivery, I would define the definition of done as "*Active Continuous Improvement at all levels of the organisation*".
  
  The other topics like automated builds, CI/CD, etc... these are just milestones and most definitely not the ultimate goal for the organisation in its DevOps efforts.
  
  It does look like it might be "finished all DevOps" once you have an automated system with continuous integration. But in fact, even should you reach this stage, you will find plenty more to do.
  
  Getting to a state where most people in the organization are constantly looking to continuously improve is extremely hard. Inertia often gets in the way, both existing inertia, and new inertia once some improvements were accomplished.
  
  There is a lot to learn from Lean and from Theory of Constraints in this aspect. Both bodies of knowledge focus on the process of continuous/ongoing improvement and how to establish this process in an organization.
  
  > **Comments:**
  > **username_0**: I like this definition! DevOps is never actually "done", it is a continuous and active process. Thanks!  
  > **username_2**: Asking when DevOps is done is like asking when a man is done with thinking. The answer is the same. When it's all over.  
  
  ---
  
  ### Answer by username_3 on 2018-07-05. Score: 3
  
  Prior to DevOps, an Agile team's definition of "done" typically meant is was "done" for the sprint (and accepted by the product-owner at or before the end of the sprint). In reality, there might be subsequent levels of testing/delivery/release-engineering before it was actually released & deployed.
  
  From a DevOps perspective, the common saying is "Done means *deployed*" - the corresponding story or feature wouldn't go to the "done" column of the board until it was deployed to production environment.
  
  
  ---
  
  ### Answer by username_4 on 2017-08-12. Score: 2
  
  DevOps is a continuous improvement in delivery cycles and meeting customer needs with top quality , less time and security without compromise on cost and performance. And of-course repeat the cycles with feedback from customers.
  
  Ideally there is **NO** getting it all **"Done"** on DevOps. This question is rather a tricky one because its similar to asking
  
  > When are you done with development or sales of a software in a Software
  > company?
  >
  > Ans: Obviously once the company shuts down or you get kicked out !
  
  Similarly there is no **Done** for DevOps culture. Of course there are deliverable and mile stones which one needs to complete like automating mundane repeated tasks , CICD pipelines etc
  
  A very good explanation for DevOps given by IBM DevOps head.
  
  <https://www.youtube.com/watch?v=EIvOZA1HgHU>
  
  
  ---
  
  