Steve Ropa blogged about What done looks like in DevOps. I must say I respectfully, but fully disagree with Steve here.
For those of you that remember I gave an Ignite talk about my views on the use of the Definition of Done back ad #deovpsdays 2013 in Amsterdam.
In the early days we talked about the #devops movement partly being a reaction against the late Friday night deployments where the ops people got a tarball with some minimalistic notes and were supposed to put stuff in production. The work of the development team was Done, but the operations team work just started.
Things have improved... like Steve mentions for a lot of teams, done now means that that their software is deployable, that we have metrics from them, that we can monitor the application.
But let's face it... even if all of that is in place there is still going to be maintenance, security fixes, major stack upgrades, minor application changes, we all still need to keep the delivery pipelines running.
A security patch on an appliction stack means that both the ops and the developers need to figure out the required changes together.
Building and delivering value to your end users is something that never ends, we are never actually done.
So let me repeat:
"Done is when your last enduser is in his grave"
In other words, when the application is decommissioned.
And that is the shared responsibility mindset DevOps really brings, everybody cares about the value they are bringing to their customers, both developers and operations people, thinking about keeping the application running. And not assuming that because a list of requirements have been validated at the end of a sprint we are done. Because we never are...
BTW. Here's my original slides for that #devopsdays Amsterdam talk.