Characteristics of Releasable Software

March 28, 2012

#8 in the Continuous Delivery webinar series

How you actually build your software will affect your delivery effectiveness. Ensuring that your software is built with Continuous Delivery in mind will smooth downstream processes like Automated Acceptance Tests, Adhoc Environment creation, and Production releases (because Production is just another environment). In this talk Scott Muc describes his dream Release Management DSL and discusses its effects on how a team will build software. From what developers need to do, to how managers can read the warning signs on software that’s difficult to release.

About the speaker

Scott Muc is a DevOps consultant at ThoughtWorks who is passionate about seeing code being checked into source control get to production continuously. He developed this focus on DevOps as a developer on a small team where responsibilities of deployment were shared.

Scott Muc hails from Calgary, Canada and has worked in IT since the popping of the bubble in 2001. From build and deploy automation, server administration, and software development; you can find him problem solving every step of the way. You can find him online on Twitter or on his blog. The material for this discussion has come from observations on the ground working on several build and release projects.