Comprehensive software reviews to make better IT decisions
Rationalize Your Apps in 60 Seconds
Too good to be true doesn’t mean there’s no good to be had.
A common folly (or marketing ploy) seen with application rationalization is the idea that it can be accomplished in x number of weeks. Orbus iServer, is one vendor that makes such a claim, suggesting rationalization can be done in four weeks.
In addressing these kinds of statements, I always start with simplifying what is application rationalization.
Application rationalization is a decision-making framework using cost, value, or other indictors to help determine the strategic direction of your applications.
When you put it that way, it seems quite easy and doesn’t sound overly time consuming. All you need is applications, a few inputs, and a toolset or framework, and you get your output in the form of an action item for an application.
In reality, this gets convoluted and you need to ask:
- Do you have a list of or even know all your applications?
- Does everyone agree on what an “application” is?
- Do you know where and how they overlap or which are redundant?
- Do you have the right data points or are the right data points even attainable?
- Do you know what your goals are for rationalization and how they should impact the algorithm to ensure you’re getting meaningful results?
- Do you have a process in place to capture and communicate the results?
- Do you have a process in place to further refine these results into business cases or project proposals and inject those results into your software delivery lifecycle?
These are the kinds of things that take your optimistic four weeks and turn it into a head-scratching, never-ending data collection initiative. Your existing maturity in terms of application portfolio management and similar competencies like enterprise architecture, project portfolio management, or product management will greatly impact how quickly you can achieve success with application rationalization.
Where iServer does get it right is acknowledging that there are correct steps to and a correct order. Its “application rationalization in four weeks”does emphasize a methodical approach and sequence that ensure goals are defined and necessary inputs are captured. I would just prefer to call this application rationalization in four … well … five steps.
iServer’ s methodology:
- Artifacts linking application to business capabilities, technologies, and related concepts
- Lists of application owners, vendors, locations, and metadata
- Scoring questionnaires and worksheets
- Establish goals and centralize data
- Assess and augment data
- Visualize and analyze your portfolio
- Consider rationalization results and present roadmap
What’s important here is the emphasis on centralizing, assessing, and augmenting data. They don’t sugar coat the necessity of getting the right information and using it in the right way. Moreover, the process doesn’t end with generating a disposition for your apps. There is clearly a bigger end game here of producing a roadmap, which is that quintessential artifact of a good application portfolio management practice. Being able to communicate and validate the direction of your portfolio to your stakeholders is a substantial factor in increasing the business satisfaction from the application delivery.
Lastly, rationalization should not be looked at as a one-and-done initiative. Rationalization is about continuously governing your portfolio and keeping the business up to date on the best possible recommendations for their applications. To suggest four weeks and you’re done implies you won’t continue to reap the benefits from being that strategic partner and innovator in your organization.
- I’ve been too harsh on iServer. Four weeks is technically possible, just under the best possible circumstances. The biggest variable here is data quality and the tool can only do so much in that regard. Your processes need to be mature enough to make the most of a tool like this.
- The value should not be strictly limited by how long something takes. Emphasize the value of the practice you’re trying to grow and the ongoing returns of becoming a business partner.
- More often than not, you need to get the prerequisites down first. Info-Tech’s approach for application portfolio management and business architecture can help you get the get the foundational information needed for a tool like iServer.
- Build in the structure to not only make rationalization tailored to your specific goals, but also to build in the ongoing governance of APM and continue to maintain your roadmap going forward.
Want to Know More?
These are the trends we predict will be most important is it relates to Enterprise Architecture in 2021.
Lean IX and Apptio have partnered to produce an integrated solution that better informs the strategic decision-making process with improved visibility into an application’s total cost of ownership and alignment to business capabilities.
From the business architecture perspective, agility is the ability to quickly change structurally and operationally to react to external changes or to create new business value. Enterprise architecture comprises business and service/application architecture – therefore, it needs to provide an environment for harmonized agility at each level.
This note outlines some of the fundamental KPIs that you should measure to show the success of the enterprise architecture team. It also discusses how you measure them and visualize the result.
The application portfolio management (APM) tool space can be a confusing one, as many software vendors offer their own take of what APM is. Enterprise architecture, application management and project portfolio management tools offer an APM use case, but these are often quite skewed the primary function of the tool.
Application rationalization fails when the chosen framework does not match your scenario or the goals for your application portfolio. This note looks at how to apply application rationalization during an M&A.
Often people misidentify the purpose of application rationalization, leading to misuse and unsatisfactory results. We try to break application rationalization down to its simplest form to understand how to make the most of this critical IT function. tr
Measuring technical debt is important, but more important is communicating the implications of this problem in terms of risk to business capabilities. Cast Highlight tools are used for application portfolio management (APM), specializing in applying code analytics to business decisions regarding your organization’s applications.
Many application rationalization tools and frameworks miss the true benefits of this practice, as they only assess the individual application without consideration for its redundancies. Infusing an enterprise architecture perspective, as seen with LeanIX, will generate the bigger savings you are looking for.