Application Portfolio Management – Notes & Mindmap

March 19, 2012

Application Portfolio Management: TIME for the Application Masses

  • Findings
    • Large inventories of small applications can often be categorized rapidly by frequency of use.
    • Many infrequently used applications can be retired or consolidated.
    • Proactively proposing retirement can accelerate portfolio simplification
  • Analysis
    • Big, complex applications are often a fairly small percentage of the total application count., support a lot of business value, and merit a detailed analysis
    • How can we economically categorize and overhaul the thousands of smaller applications that form the rest of the portfolio?
    • ” Application-hunting license,” prescreening applications by usage and requiring user involvement in creating appropriate life cycle strategies.
      • Create a routine process that will rapidly align the thousands of applications into tolerate, invest, migrate and eliminate (TIME) categories — ideally driving extensive application elimination
  • Application Hunting
    • Start this routine with any applications that haven’t been accessed in a year, then systematically bring the time down to nine months, then six months and then three months.
    • It’s Rare that anyone thinks of retiring applications after task is done or the project is completed. In extreme cases, none of the people who used the application remain with the organization.
  • Send out a message listing five to 20 applications that have not been accessed in several quarters.
    • In the case of nobody responding, the exercise is straightforward to retire the system
    • Otherwise ask How often is the application used? Could you live without it? Is there another way to get that job don
  • One less system to maintain, fewer licenses for which to pay maintenance fees, and less storage and power being consumed
  • “mock” retire the system — that is, bring it offline for a full quarter, and if no one complains, then officially retire it