Continuous Delivery
![Image](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjQ_-WTyMwDEwv90HW8OclTSYdEvFZ1vSrifhUdmbTBkqBhU8w-UJBgQoBsEoWZF0fToZd3wW1UUik-v_VIqVfVe0LZyIE6viJrevNJmGYze5HQ9xIE4YAXSUIOXsrqwyleorYi6M4wYhY/s1600/quality_gates.jpg)
Setting up a continuous delivery process can be quite a momentous task, especially when retrofitting to an existing product, however, I'm quite lucky with a current project in that we're at the very start of the project so there are no existing processes in place. Once you've read this, I'd love feedback on my solution and ideas for improvements if you have any. When I joined the project the developers had already put continuous integration and deployment processes into place using Team Foundation Server (TFS) and Octopus. So the challenge placed before me was to extend this process out to a full continuous delivery plan complete with testing, reporting, full end to end life cycle overview, and of course, happy project, change and release managers. This is taking a bit of thinking. I can easily do the geek thing and get down into the nitty gritty of setting all of this up but the business needs to see how it works at a higher level, and they also need to be give