madison

Reducing the high cost of low-value applications

Walid Farha, Keane, Special to ZDNet | February 23, 2010 12:33 PM PST

Summary

The speed of technology advancements and rapid pace of today’s business environment often force companies to rely on an application long after it has ceased to provide maximum value, says Keane's Walid Farha.
Commentary - Every company faces the challenge of maximizing return on investment in IT applications. However, the speed of technology advancements and rapid pace of today’s business environment often force companies to rely on an application long after it has ceased to provide maximum value.

Such an application becomes increasingly costly to operate and impedes IT productivity because of its complexity and constant support requirements. Add costly non-core technology, redundant applications inherited from mergers and acquisitions and underutilized packaged solutions that most medium sized companies invest in, and it becomes clear how application portfolios can quickly – and quietly – drain IT resources and corporate bottom lines.

Although IT application portfolios are, as a whole, immensely valuable assets, they universally contain a mixture of high, low and medium value-producing applications. Once an application reduces in value-production, steps need to be taken to eliminate or renovate before it becomes disproportionately expensive to the level of business value it produces.

By objectively evaluating an application portfolio and measuring the cost of each application against the business value it provides, companies can then “rationalize” applications that generate little or no business benefit and simultaneously extend the lifecycle of aging applications that can still provide a desirable ROI. This approach, called “Applications Rationalization,” seeks to systematically and proactively, eliminate non-core technologies and platforms. Disciplined management of application portfolios allows these assets to achieve full potential by capturing greater benefit from production systems, freeing funds and IT resources to pursue high-value opportunities and providing the foundation and flexibility to respond more quickly to changing business requirements.

The following categories of low-value applications are typically found in corporate IT portfolios:

  • Aging assets
  • Redundant functionality
  • Disparate and incompatible applications
  • Non-Core functions
  • Non-core technologies

How Applications Rationalization can help
Applications Rationalization addresses low-value applications from a business point of view. Using objective measures, it identifies underperforming assets and, depending on the situation, either restores them to profitability or decommissions them to save funds and free resources. Typically, 10-20 percent of applications are targets for retiring and 20-30 percent of core applications are at risk because of their dependence on limited resources, small vendors or a lack of documentation. Applications Rationalization encompasses four major tasks as described and illustrated below.

Analyze the portfolio
Goal: Target your efforts to the areas of highest return
Analyzing the state of the applications within the IT portfolio is important to understand current conditions, quantify cost of operation and support, and measure value to the business. This information creates a prioritized action list to maximize the benefit of rationalization investments.

Eliminate redundant applications
Goal: Reduce costs and support efforts
This step identifies overlapping functionality and determines which application is stronger and should thus remain. Equally important is the clean-up and migration of data from the redundant applications to the remaining applications and decommissioning the extraneous applications.

Retire end-of-life applications
Goal: Reduce costs and support efforts
An end-of-life application can drain IT resources for years before it is noticed and retired. On average, over 99 percent of applications targeted for retirement are not decommissioned by the company in a timely fashion. In cases where the original business purpose still has merit, the best strategy may be to develop an archiving strategy application operating on a less costly and more strategic platform and retire the aged one.

Renovate worthwhile applications
Goal: Maximize the residual business value of all applications
Migrating an application from a non-core technology to a newer, more strategic platform extends the application’s useful life by enhancing its flexibility and scalability while eliminating the costs associated with supporting the older platform. Much of this highly defined work is suitable for assignment to offshore development facilities to lower cost and further increase ROI.

Rationalizing the benefits
IT organizations typically focus so intensely on application development and operational management of production applications they miss the straightforward, immediate and quantifiable benefits they could receive from addressing low-value applications. Investments in Applications Rationalization are easily justified. In tight economic times, it provides significant cost savings that flow directly to the corporate bottom line and frees resources for projects that would otherwise be deferred. In abundant times, it provides the resources and flexibility to respond more rapidly to business opportunities.

Conclusion
Disciplined management of application portfolios allows companies to maximize return on investment in IT applications, directly affecting the bottom line. By eliminating non-core, redundant and end-of-life applications and extending the lifecycle of any aging applications that can still provide a desirable ROI, companies can save money and resources previously spent on underperforming applications, experience enhanced flexibility to respond to or initiate business changes and see greater value from an application over a longer period of time.

biography
Walid Farha leads the portfolio solutions practice within Keane application management and outsourcing. He is responsible for implementing disciplines and processes to optimize client application portfolios and reduce their total cost of ownership. Mr. Farha's expertise spans every facet of large-scale application development, outsourcing and program management, including enterprise architecture planning and governance, IT portfolio management, development of IT strategy, and planning and management of end-to-end implementation.

Talkback Most Recent of 8 Talkback(s)

  • Isn't being redundant good?
    If one piece fails, a redundant piece backs up for it?

    Then again, this is business. Zero loyalty, unless they don't get their tax breaks or "government subsidy".
    ZDNet Gravatar
    HypnoToad72
    23rd Feb 2010
  • There is a difference between SMART loyalty and blind loyalty
    To have a company telling you that they refuse to update their program for the new era (unless they have gone out of business) and not looking for another company to do business with is the epitome of stupidity.
    ZDNet Gravatar
    Lerianis10
    23rd Feb 2010
  • There is a difference between SMART and STUPID
    Just rewriting things every time some schmuck
    thinks he has found the holy grail of
    programming is STUPID. Keeping code simple and
    maintainable is SMART.
    Some new trends are SMART, most are just blow-
    hard know-it-alls finding ways to get lucrative
    speaking engagements or seem really intelligent
    without finishing or accomplishing anything.
    Listening to the latter is STUPID.
    Understanding which is which is EXPERIENCE and
    WISDOM.
    ZDNet Gravatar
    verelse
    25th Feb 2010
  • RE: Reducing the high cost of low-value applications
    The concepts in this article are worrying - not because of
    what they're saying, rather that they still need to be said.
    Don't IT Directors learn anything? Will these guidelines still
    be re-hashed by someone else five years from now?
    ZDNet Gravatar
    efreedom
    24th Feb 2010
  • Yes.. we never learn
    We all fall for the next guru who promises us the
    world. Until we are wise enough to know better.
    The problem is that MBAs who seem to be taking
    over IT are just as bad at running IT as they are
    at running banks and companies.
    ZDNet Gravatar
    verelse
    25th Feb 2010
  • More money wasted rewriting everything in the latest style
    My personal, naturally limited analysis shows that the inherent desire of every programmer to rewrite any
    code not personally created by them is the biggest drain on IT resources.
    Ask any developer what needs to be done to a system they did not create and the answer will be: "Rewrite it
    in xxxx" where xxx is the platform/language/tool of their choice. The ancient Greeks complained that no one
    wanted to maintain existing buildings, the just wanted to demolish and build new ones. That is happening in
    IT now, especially with these so-called "low value" applications, a term I find dubious at best.
    These guidelines are a good start. I would add the Engineer's maxim: Keep It Simple, Stupid, which these
    guidelines reinforce. Needlessly complex apps such as the ridiculous trend to n-Tier everything, so-called
    "reusable" code that will never be reused, needlessly complex "patterns" and "object models" that seem so
    great and cutting-edge in discussion are just a way for someone to sound intelligent and not actually do
    anything.
    The correct approach is the least complexity that provides the solution. Instead, we are constantly deluged
    with articles from "experts" who tell us what we've been doing wrong and why, if we just listen to them and
    use their favorite platform/language/tool, all our IT problems will vanish. We are told that simple,
    linear, readable code is bad... rather, we should obfuscate, extract, inherit, pattern, separate,
    compartmentalize, objectify, ad nauseum. Not to worry, though, the next guy that comes along will toss it
    all out and rewrite it, presenting it as "something completely different" that will nonetheless get
    rewritten by the next guy. THAT is where the money goes.
    I am not saying let's all write COBOL, but the patterns shift too quickly without thought. Everyone's a
    guru in their own mind because everyone has a new buzzword on their lips that dazzle the PMs and BAs into
    believing they've got something effective instead of just new.
    Ask these questions:
    1) what are the odds that the massive framework I want to write will every be used widely? By widely I mean
    500+ developers, not the four on my team.
    2) Why is it necessary to write an n-tier (where n tends to be 6 or more for no good reason), highly
    scalable, patterned application for a 5-user, internal, corporate website? I recommend banging out the bare
    minimum of code needed to accomplish the task. Yes, use libraries (e.g. Java or .NET). Yes, don't reinvent
    the wheel. Yes, use object-oriented code recognizing that in the end, you will need to write something that
    USES it, which WILL be linear.
    3) Why ARE you reinventing the wheel? There's an app for that. Go find it, buy it, install it. So what if
    it isn't perfect? What YOU write won't be either...you know the user will want ten more features. Won't it
    be easier to tell them NO to these "low value" features when you don't have the source code?
    4) Why the heck are you not using open-source? Why have major companies not gotten together (like they did
    to standardize Electrical or Mechanical components) and just create a freakin standard that the Open Source
    community can target? Are thing REALLY so different at your company that you need to customize EVERY
    business process? I mean, and expense report IS an expense report. Maybe your BUSINESS practices are a big
    factor in your IT costs? Hmmm...
    I could go on, but who is listening?
    ZDNet Gravatar
    verelse
    25th Feb 2010
  • RE: Reducing the high cost of low-value applications
    How can one make evalutions of technology
    without any technical knowledge ?
    ZDNet Gravatar
    xmeshman
    26th Feb 2010
  • RE: Reducing the high cost of low-value applications
    while I agree in principal, at a closer look any savings is lost in the money and time spent implementing such a proposal. In the end its anouther case of the mouse being chased by the lion that is being followed by a mouse .
    ZDNet Gravatar
    docengles
    27th Feb 2010

Talkback - Tell Us What You Think

Formatting +
BB Codes - Note: HTML is not supported in forums
  • [b] Bold [/b]
  • [i] Italic [/i]
  • [u] Underline [/u]
  • [s] Strikethrough [/s]
  • [q] "Quote" [/q]
  • [ol][*] 1. Ordered List [/ol]
  • [ul][*] · Unordered List [/ul]
  • [pre] Preformat [/pre]
  • [quote] "Blockquote" [/quote]

The best of ZDNet, delivered

ZDNet Newsletters

Get the best of ZDNet delivered straight to your inbox

Facebook Activity