Structure in Threes IT Lifecycle Management: EOL
January 15, 2014 Leave a comment
Spent a few minutes during breakfast pondering some of the issues around IT Lifecycle Management. Specifically the term End of Life (EOL). IT community is still a little behind other engineering disciplines in its understanding and application of this concept. Take S/W for instance. There EOL typically means either no more support for the product or that the product has been withdrawn from the market. That is on the vendor’s side of the equation. On the customer side EOL has other implications. Does the application still operate and provide utility? If so EOL is really a transition from vendor support to self-service; think out of warranty for your car. A third level of consequence are the customers of IT, the Line of Business that use the service based upon the application. Does EOL of the application mean EOL for the service or does it mean a mad scramble to replace the utility by some other means.
This brings me back to the nuances I am exploring in Portfolio Management. Currently one of the failings of IT Portfolio Management has been the lack of linkage between service utility and application serviceability in managing a portfolio. Too often have a seen that second and third order consequences were not considered during portfolio decisions. Y2K issues a decade ago are just one ripple effect of short term decision making. The hierarchical model of portfolio I’ve been prototyping and testing appears to address this issue. I’ve started to look at applying via usage strategies of Active Directory which was what I had considered when we came up with the conceptual design. Only a decade or so behind schedule. However, Cloud technologies may make implementations easier and harder now. IT Financial Management approaches are on an upswing again so the timing might be right