The media setup at Sapphire in Vienna is interesting. For the analysts and traditional media, there are rows of tables and chairs facing toward the front of a large room.
Beyond IT Failure
Michael Krigsman is a recognized authority on the causes and prevention of IT failures.
Michael Krigsman is an internationally recognized analyst, strategy advisor, and authority on enterprise software leadership, CIO innovation, and social business. Interact with Michael on Twitter at @mkrigsman.
SAP is actively supporting a group of bloggers here at Sapphire in Vienna. Yesterday I engaged in a lengthy discussion between a half dozen bloggers and Pascal Brosset, Senior Vice President of Market Strategy for SAP.
SAP is pushing the notion that SOA offers the promise of “non-” (ok, let’s be real and call it “less-“) disruptive projects. Through the use of SOA, the plan is to help customers enhance and upgrade their systems with less interference to the business operations those systems are designed to support.
Sitting in the analysts’ and bloggers’ press conference, I asked the following question: “Would you please explain the role of SOA in SAP’s plans for mid-market adoption?” When I introduced myself as being from the projectfailures.
These last months have been a whirlwind of traveling, consulting and product development. I will be in Vienna next week for SAP’s Sapphire conference.
Dennis Howlett raises some questions to be used when evaluating lawyers and accountants. Similar guidelines could be applied when hiring consultants on IT projects.
Yesterday, I blogged about a rather uninspired article from Baseline Magazine, which described ten IT project pitfalls. In contrast, today I’m happy to share and excellent list of ten lessons for IT Project success, from CIO Insight magazine:Business processes should set the agenda, not technology.
I’ve always had respect for Forrester Research, despite complaints such as this. Maybe the Christmas to New Year’s holiday interregnum is to blame, but a recent recent report advising CIOs on how to spend their time just seems obvious to me.
Baseline Magazine published an article called “Top 10 Project Pitfalls You Can Avoid.” This list is hardy definitive, but does describe a bunch of good points:A project’s scope is too monolithic and gargantuan.
I often blog about stupid things that kill IT projects. This post describes how I almost killed my Vespa scooter today.