Application Rationalization Key Initiative Overview: Analysis
Application Rationalization Key Initiative Overview: Analysis
Application Rationalization Key Initiative Overview: Analysis
ARCHIVED This research is provided for historical perspective; portions may not reflect current
conditions.
By Analysts Bill Swanton
This overview provides a high-level description of the Application Rationalization Key Initiative.
IT leaders can use this guide to understand how to develop an application strategy that
rationalizes their legacy portfolio and prepares it for fast-emerging business requirements.
Analysis
Figure 1. Application Rationalization Key Initiative Overview
■ Identify business-sponsored and business-funded initiatives that require portfolio and process
changes.
■ Identify vendors, methodologies and platforms for reliable, serviceable and highly available
applications.
■ Prepare the legacy application portfolio for fast-emerging business requirements brought on by
market changes such as cloud, big data, social and mobile.
■ Strategize and lead in governance: Develop a multiyear application strategy that willenhance
business agility. Establish a governance council to help guide portfolio decisions. Ensure that
policies balance competing interests and align with business strategy.
■ Obtain peer buy-in: Articulate the benefits of executing the application rationalization, as well as
the costs and risks to the business.
■ Define metrics: Establish a team that includes other business units to obtain unbiased data and
define metrics on application cost and value.
■ Maintain momentum: Monitor the portfolio through regularly scheduled reviews. Demand
regular updates on modernization projects.
■ Conduct regular portfolio rationalization reviews: Identify the applications with the worst
performance in terms of meeting business needs in a cost-effective and reliable manner.
■ Segment the applications into pace layers: Reduce the cost of maintaining foundational
systems of record, while allowing faster and cheaper delivery of differentiating capabilities. This
may require refactoring and service-enabling applications.
■ Architect Solution: Define the architecture, technology and standards for the project. Model
business requirements and detail specifications for solution delivery. Recommend how to
implement the project. Define process details and performance metrics. Communicate the plan.
■ Select Solution: Set requirements, and issue RFPs. Analyze market intelligence. Evaluate
vendor/service provider options. Choose technologies and vendors/service providers. Negotiate
service-level agreements and contracts.
■ Deploy: Staff and manage the implementation. Coordinate solution deployment. Create the
development and test environment, and run tests. Seek feedback from users. Monitor risks. Shut
down the old applications.
■ Operate and Evolve: Operate and manage the implementation. Revise in response to feedback,
risks and changing business requirements. Measure performance. Monitor use and compliance.
Develop skills and define best practices for users. Refine governance processes.
About Gartner Careers Newsroom Policies Privacy Policy Contact Us Site Index Help Get the App