Everything is a Freaking DNS problem - done http://127.0.0.1:8080/blog/taxonomy/term/1502/0 en What done REALLY looks like in devops http://127.0.0.1:8080/blog/what-done-really-looks-devops <p>Steve Ropa blogged about <a href="http://blogs.versionone.com/agile_management/2015/04/30/what-done-looks-like-in-devops/">What done looks like in devops</a> , I must say I respecfullly , but fully disagree with Steve here.</p> <p>For those of you that remember I gave an Ignite about my views on the use of the Definition of Done back ad #deovpsdays 2013 in Amsterdam.</p> <p>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. </p> <p>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.</p> <p>But lets 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.</p> <p>A security patch on an appliction stack means that both the ops and the developers need to figure out the required changes together.</p> <p>Building and delivering value to your end users is something that never ends, we are never actually done. </p> <p>So let me repeat ,</p> <p>"Done is when your last enduser is in his grave"<br /> In other words, when the application is decomissioned.</p> <p>And that is the shared responsability mindset devops really brings, everybody is caring 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...</p> <p>BTW. Here's my original slides for that #devopsdays Amsterdam talk.</p> <p><iframe src="//www.slideshare.net/slideshow/embed_code/key/JhgnyP2eJbulns" width="425" height="355" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" style="border:1px solid #CCC; border-width:1px; margin-bottom:5px; max-width: 100%;" allowfullscreen> </iframe><br /> <div style="margin-bottom:5px"> <strong> <a href="//www.slideshare.net/KrisBuytaert/do-disnot-done" title="Dod is not done" target="_blank">Dod is not done</a> </strong> from <strong><a href="//www.slideshare.net/KrisBuytaert" target="_blank">Kris Buytaert</a></strong> </div> </p> http://127.0.0.1:8080/blog/what-done-really-looks-devops#comments devops done Sun, 03 May 2015 17:05:29 +0000 Kris Buytaert 1102 at http://127.0.0.1:8080/blog Done Ignite http://127.0.0.1:8080/blog/done-ignite <p>Last month I gave an 5 minute Ignite talk at #devopsdays Amsterdam.</p> <p>To summarize .. it was a rant against people that think that the end of a sprint their work is done, an idea they might have gotten from a broken definition of done.</p> <p>Both the video recording and the slides are embedded below.</p> <p><iframe width="560" height="315" src="//www.youtube.com/embed/io8FCbKvZuU" frameborder="0" allowfullscreen></iframe></p> <p><iframe src="http://www.slideshare.net/slideshow/embed_code/23035308" width="427" height="356" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" style="border:1px solid #CCC;border-width:1px 1px 0;margin-bottom:5px" allowfullscreen webkitallowfullscreen mozallowfullscreen> </iframe><br /> <div style="margin-bottom:5px"> <strong> <a href="http://www.slideshare.net/KrisBuytaert/do-disnot-done" title="Dod is not done" target="_blank">Dod is not done</a> </strong> from <strong><a href="http://www.slideshare.net/KrisBuytaert" target="_blank">Kris Buytaert</a></strong> </div> </p> http://127.0.0.1:8080/blog/done-ignite#comments agile amsterdam definition of done devops devopsdays done Tue, 02 Jul 2013 22:05:49 +0000 Kris Buytaert 1082 at http://127.0.0.1:8080/blog