tech·nic·al·ly agile

Deployment documentation

Outlines steps to document and improve deployment for a complex business app, focusing on automation, rollback, vendor updates, and multi-environment management.

Published on
2 minute read
Image
https://nkdagility.com/resources/154BNVcnbaU

Over the past week I have been working on creating and documenting a deployment process for our new main business application. This application is very complicated and requires twenty servers per four environments. We need to track and control deployment to UAT, pre-production, production and C&R (disaster recovery site), but my company as a larger organization only requires control of production.

Now at the moment all the deployments are done by the vendor and is done by updating Assemblies on various servers, then running a custom tool that updates the config files based on the version of the assembly that has been updated. All database updates are currently done manually, and I rather doubt that there is any pre scripted rollback for the schema changes.

I have been tasked with coming up with a solution that allows us and not the vendor to easily update and rollback any deployments necessary. Now, this project has been one of those “Of-The-Shelf” products that has required eight months of “configuration” (I can configure any system with Visual Studio too) and is not yet stable.

The application is made up of over twenty components that exist on multiple servers over multiple environments and soon over multiple instances.

Once it is stable however, I would like to see the vendor providing their updates the same way that any major application is delivered:

If it works :) then we will be able to do deploy any number of instances of the solution and be able to replicate any version of the solution.

I want the vendor to provide MSI or EXE’s for all releases of each of the components, but the rollback function must be implemented religiously. This will reduce the risk in any deployment as it currently takes two to three days to do a clean build of the application. It should also force the vendor to invest in the quality of their application, because if any of the installations or rollbacks go wrong in the Dev environment then we will “return to sender” for a recheck or rebuild.

Has anyone ever tried to get their vendor to do this?

Has anyone been successfully?

Technorati Tags: .NET 

Product Delivery
Comments

Related blog posts

No related videos found.

Connect with Martin Hinshelwood

If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.

Our Happy Clients​

We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.​

Workday Logo
Epic Games Logo
Microsoft Logo
Teleplan Logo
Freadom Logo
Deliotte Logo
Boeing Logo

NIT A/S

Boxit Document Solutions Logo
Philips Logo
Milliman Logo
Xceptor - Process and Data Automation Logo
SuperControl Logo
Sage Logo
Cognizant Microsoft Business Group (MBG) Logo
DFDS Logo
Slaughter and May Logo
Akaditi Logo
Washington Department of Transport Logo
New Hampshire Supreme Court Logo
Department of Work and Pensions (UK) Logo
Royal Air Force Logo
Washington Department of Enterprise Services Logo
Ghana Police Service Logo
Akaditi Logo
New Signature Logo
Lockheed Martin Logo
Genus Breeding Ltd Logo
Epic Games Logo
Freadom Logo