book-continuous-delivery#frequent-releases More frequent releases lead to lower risk in putting out any particular release. This is true because the amount of change between releases goes down. So, if you release every change, the amount of risk is limited just to the risk inherent in that one change. Continuous deployment is a great way to reduce the risk of any particular release. book-continuous-delivery#frequent-releases
book-continuous-delivery#force-you-to-do-right-thing Perhaps most importantly, continuous deployment forces you to do the right thing (as Fitz points out in his blog post). You can't do it without automating your entire build, deploy, test, and release process. You can't do it without a comprehensive, reliable set of automated tests. You can't do it without writing system tests that run against a production-like environment. book-continuous-delivery#force-you-to-do-right-thing
book-continuous-delivery#shift-in-way-of-doing-things Continuous deployment takes this approach to its logical conclusion. It should be taken seriously, because it represents a paradigm shift in the way software is delivered. book-continuous-delivery#shift-in-way-of-doing-things