By: David Norfolk, Practice Leader - Development, Bloor Research
Published: 21st May 2013
Copyright Bloor Research © 2013
If there is one thing that drives agile delivery of automated business outcomes, it's continuous deployment. Automation of error-prone manual procedures reduces errors and increases efficiency - as long as you build on configuration management best practices. Note that this doesn't demand 'high ceremony' process and a focus on perfection - 'just enough' process ensures that the automated business outcome is 'good enough' to get the job done - that is, it's fit for purpose - and continuous deployment implies that the scope of impact of any particular change is limited (so any risk is manageable).
This topic is, IMO, one of the sexiest topics at the up-coming BCS-CMSG conference (4 June 2013, at the BCS Office in central London). Martin van Vliet, of XebiaLabs, is talking about taking continuous integration to the enterprise level and extending it to Continuous Delivery. To get there, he says, teams need enterprise-grade automated testing, Continuous Integration and automated deployments - and he'll highlight some simple steps for getting started.
We have not received any comments against this entry. Why not be the first?
We automatically stop accepting comments 180 days after a post is published. If you would like to know more about this subject, please contact us and we'll try to help.
Published by: IT Analysis Communications Ltd.
T: +44 (0)190 888 0760 | F: +44 (0)190 888 0761