Legacy systems integration: If you can’t beat ‘em, join ‘em
Posted by: Kristen Caretta
legacy systems
Recently, while researching some information for a story on legacy systems integration, I dug around to figure out how midmarket IT execs determined and measured the benefits of legacy applications — How did they decide what was important? What needed to go? Was it worth investing time in one of the many process acronyms offered (BPM, APM, etc.) to sort everything out?
I asked one midmarket CTO just that — what he uses to justify the existence of any of his legacy systems. His response? “If you are a CTO in the SMB world, you don’t need very organized thinking to detect differences in criticality among applications. As soon as something fails, you get to measure its importance very viscerally.”
TTYL to the APMs, huh?
In sorting through the legacy systems of his 25-year-old business, he has not found practices like application portfolio management (APM) necessary. Quite frankly, he has other things to do. In a large enterprise organization with hundreds or thousands of applications that need sorting and analyzing, portfolio management may prove very useful — necessary, even. But in the midmarket? Continued »
0 Comments
RSS Feed
Email a friend
