Define "Application" Based On Your Context To Avoid False Starts In Your Rationalization Efforts
January 26, 2011
Why Read This Report
Debate over the definition of the term "application" is needlessly stalling application rationalization, application portfolio management (APM), and application benchmarking efforts, based on the faulty assumption that there is only one correct definition for the term. For example, the definition an application developer uses to identify the technical boundaries of an application is needlessly technical and granular for application portfolio management (APM) and rationalization purposes. Don't allow analysis paralysis to lead your efforts astray, causing you to seek a one-size-fits-all definition for the term application. Instead, set a workable definition based on your context.
Already a Client?
Log in to read this document.
Become a Forrester Client
Timely and relevant, Forrester's RoleView research aligns to 13 leadership roles across business and technology management. Our expertise in customer experience, mobile, digital business, and big data will help your teams win in the age of the customer. Contact us to learn more.
This report is available for individual purchase ($499 USD).Purchase