mafe
.NET Software Architect
Key areas of interest: ALM, .NET C#, PowerShell, Azure, Dynamics 365 Tooling
Robert started in the area of ASP.NET projects and has now more than 7 years of experience in the international Dynamics Enterprise business.
He works mainly as an principal software architect at Kupp and as a external consultant for Microsoft.
mafe
.NET Software Architect
Deployment effort & price savings
Manuel Vs. Automated Deployment
Posted: 11.2019 | Category: Automated Deployment
Intro
Introduction:
Many companies run their deployment process manually, which has the problem that many errors are made and a lot of work is done to fix these errors. In addition, setting up and maintaining a lot of time and this also incurred high costs. There are always similar mistakes or the same installation / support measures, unnecessary time and cost effort should be avoided.
In the following text you will read more about the advantages of automated Deployment and the comparison to the manuel Deployment.
Overview:
With the calculation below based on experience for the first two years of a project with 192 Deployments per year for an Enterprise project with 1000 user the result in the first year with tool inserted is not even 1/6 compared to the effort without a tool. In the second year the difference is even greater with about 1/7 as much effort with tool compared to the effort without tool. (see grafic)
Calculating basic for Enterprise project (1000 user)
Duration: 2 years
|
System |
Deployments/month |
Deployments/year |
|
DEV |
10 |
120 |
|
INT |
4 |
48 |
|
PrePROD |
1 |
12 |
|
PROD |
1 |
12 |
|
|
16 |
192 |
*2 hours for one deployment calculated
Result:
1st year:
Automated Deployment effort only 1/6 across Manuel Deployment effort
2nd year:
Automated Deployment effort only 1/7 across Manuel Deployment effort
Total -> 5/6 Deployment effort saving!
Deployment activities without Tooling Vs. KDTooling
In this grafic you can see the activities distribution with and without Tooling in relation to the effort in hours.
Manuel Deployment (without Tooling):
- Initial Config
- Many errors (typos) are made -> lots of work to fix them
- Big customizing effort for environment specific
- Many actions before and after deployment
Automated Deployment (KDTooling)
- Initial Config -> only one time
- No error analysis
- No effort for environment specific customizing
- Little action -> only to use the tool
Problem
Problem with manual deployment: often simple errors, such as typos can lead to long troubleshooting and their correction.
Self-written scripts often lead to confusion and are often very difficult for others to read and they are difficult to use.
Every time the manual deployment occurs, certain values have to be adapted to the specific environment before or after the deployment process and this leads to considerable additional effort.
Solution
The solution to these problems is to introduce a tool for an automated deployment process. After a single setup, the process runs automatically and with almost no errors. (except user error) Only one effort exists to use the tool, but it works very easily.
Price difference without Tooling Vs. KDTooling
In this grafic you can see the price difference without Tooling and with KDTooling n Euros.
Result:
1st year:
Automated Deployment price savings about 45% across Manuel Deployment
2nd year:
Automated Deployment price savings about 80% across Manuel Deployment
Total price savings over 50% !
Conclusio
With the tool used, the price savings in the first year are just under 45% and in the second year even over 80%. So you get for the first two years on a total saving of over 50% of the cost. (see grafic)
Tags: