0
Your development team has completed weeks of work, delivering their masterpiece-an application-to IT for deployment, but it doesn’t work.
See, the developers made use of a different port, that now needs to be opened on the firewall so end users can communicate with the software. IT changed the firewall rule, but didn’t tell development, so they never even knew it was an issue. Later, they create another application with the same issue, except this time, it will be deployed in a different environment.
No procedure or policy was created to capture all of the changes necessary to successfully deploy the app, so the same thing happens again. It’s a vicious cycle.
IT departments struggle to manage thousands of configurations and hundreds of applications with everyone working in silos. Teams who develop the apps frequently are not on the teams that use them. Meanwhile, operations teams deploy apps they didn’t write and have to convey to the development team when changes need to be made in order for them to work in this new and foreign-to-development thing called "a production environment".
Sound familiar?
Today’s IT environments are extremely complex. In the past, applications and hardware were closely connected. Apps came from Continue reading