Big or Small, Enterprise Architecture Is a Key Part of a Successful Software Deployment Strategy
A good software deployment strategy could be the difference between multiple and costly false starts and a smooth implementation. Considering the rate at which emerging technologies are introduced, it’s becoming more important than ever for organizations to have a software deployment strategy in place.
But what does it involve?
Not all software deployments and investments are equal. Large-scale, big-money investments like ERP require a lot of resources and planning. Small-scale investments, like website technology, on the other hand, can be purchased, expensed and deployed with few people knowing. And of course, there are thousands of software decisions made that fall somewhere in between.
Software purchase decisions and deployments represent an opportunity to leverage the experience and knowledge of your enterprise architecture (EA) team so you can make smarter, better investments. The key here is the EA team’s complete view of your IT landscape, which can help eliminate redundant purchases, identify issues of integration and more.
Small Projects Can Create Big Headaches
Here’s an example of how a small-scale software investment can wreak havoc on an organization.
There is an intense focus today on customer experience (CX). Ensuring that your website visitors have access to the information they want, and they can find it quickly and easily, is just part of your overall CX. This makes your customer-facing technologies – the ones that power your website or mobile app – critical investments, even though they may not carry the price tag of an ERP system.
Even the smallest investments need to be vetted to make sure they work with existing infrastructure and processes. One small piece of website tech that ends up degrading your online CX can cost your organization millions in a very short amount of time. There’s simply too many choices just a click away today if something isn’t working properly. Differentiating technologies are also more likely to be customized than an application like ERP, which can often use a number of out-of-the-box processes.
These are areas where a software deployment strategy involving your EA team can help guide the software purchase and deployment process. But even in a world where software deployments increasingly mean logging into a cloud-based SaaS application, a software deployment strategy is still beneficial.
Don’t Be Resigned to Failure
Many SaaS vendors like to talk about how easy it is to get up and running with their products, especially when the infrastructure elements are in the cloud. But the reality is that the network that connects to the SaaS application, the security, the integrations with existing (often on-premise) applications, the SLAs and licensing, can all benefit from a review by the EA team.
Failed software deployments are, in fact, a significant problem for many organizations. Such failures can often be attributed to a lack of planning and foresight.
Considering the costs associated with some software – including its purchase, implementation and consultancy fees/training required to get started – a good software deployment strategy could save millions … literally.
A Gartner study found that nearly half (46 percent) of respondents said their most expensive, time-intensive software deployments were not delivering. When Gartner broke the software purchases in question into deal sizes of over and under $1 million, the firm got similar results.
When your EA team has the visibility to see across your IT landscape and understand the business processes built on your technology, it can help provide a better idea of the real costs behind your software deployments and you can better estimate your time to value. When it comes to software investments, you don’t be resigned to failure.
erwin EA gives organizations a full-featured, versatile platform for enterprise architecture in its broadest sense to ensure the success of projects – regardless of their size or scope.