I guess this is the right thing to do but in the process it exposes the underlying shortcomings of legacy ITSM products. All the proprietary code out there makes life difficult for customers and even the vendors who are still struggling to patch together years of acquired technologies. These guys are stuck between a rock and legacy code base. Remaining options for the alphabet soup include: 1. keep creating patch work, custom integrations 2. start over and build on WOA and SOA (your customers are already used to choosing between version lock or nightmare upgrades) 3. do nothing and lose more customers to products built on the Internet and delivered via SaaS, like Service-now.com (shameless plug)
Latest management headlines from Network World:
IBM, South Carolina work to boost enrollment in IT classes
Compuware updates IT project portfolio management tool
Staff to stay at work over Christmas period claims report
|
Does Verizon's Voyager stack up to the iPhone? |
|
|
5 IT skills that won't boost your salary
[1,407]
Women 4 times more likely than men to cough up personal info
[589]
Japan's 10 funniest tech-related commercials [Videos]
[407]
Throwing away a promo CD is "unauthorized distribution"?
[1,265]
Adults too quick to dismiss educational video games
[682]
Attack of the iPhone clones [Slideshow]
[578]
10 things IT needs to know about AJAX
[1,258]
This Year's 25 Geekiest 25th Anniversaries [Slideshow]
[409]
|
|
Post new comment