Main Menu
Home / IT Governance / Do you Rationalize your Application Portfolio?

Do you Rationalize your Application Portfolio?

From the blog:
What do we mean by Application Rationalization?   Once again we have IT terminology that sounds impressive but is vaguely defined and interpreted differently by many different people and organizations.   If you look up the definition of “rationalization”, you will find that it means to justify.   How does this apply to applications?   Why would we have to rationalize applications?   After all, if they were not providing benefit, they would not exist.   Unfortunately, this is not a true statement. Many applications were justified based on a defined business value when they were originally authorized.   The business benefits were defined and quantified, the costs were justified, functionality and technology were approved, and alternatives were dismissed.   This rationalization process occurred 10-20 years ago for most legacy applications. Ironically, organizations look at people and positions periodically and justify keeping, eliminating, or outsourcing these positions but they rarely assess their application portfolio to re-validate the value and benefits from continued operations.   Everyone assumes that if an application is in production, it must still provide benefits.

About Anne Grybowski

Anne is a former staff writer for CAI's Accelerating IT Success, with a degree in Media Studies from Penn State University.

Check Also

How Internal IT Support Lags behind External Customer Support

It’s no secret that most companies don’t have IT support that’s at the same level …

Leave a Reply

Your email address will not be published. Required fields are marked *

Sorry, but this content
is for our subscribers only!

But subscribing to ACCELERATING IT SUCCESS is FREE and only one click away!
Join more than 40,000 IT Professionals and get the best IT management articles to your mailbox with Accelerating IT Success!

Unsubscribe at any time