To paraphrase Charles Dickens, Q2 2010 seemed like the best of times or the worst of times for the big software vendors. For Microsoft, it was the best of times; for IBM, it was (comparatively) the worst of times; and for SAP it was in between. IBM on June 19, 2010, reported total revenue growth of just 2% in the fiscal quarter ending June 30, 2010, with its software unit also reporting 2% growth (6%, excluding the revenues of its divested product lifecycle management group from Q2 2009). Those growth rates were down from 5% growth for IBM overall in Q1 2010, and 11% for the software group. In comparison, Microsoft on June 22, 2010, reported 22% growth in its revenues, with Windows revenues up 44%, Server and Tools revenues up 14%, and Microsoft Business Division (Office and Dynamics) up 15%. And SAP on June 27, 2010, posted 12% growth in its revenues in euros, 5% growth on a constant currency basis, and 5% growth when its revenues were converted into dollars.
What do these divergent results for revenue growth say about the state of the enterprise software market?
So what does this mean for CIOs and IT, the custodians of enterprise technology architecture?
It is clear Jive wants to play with the big boys in the enterprise software space. To date, many Jive deployments have not involved IT. This ability to deploy its technology without IT’s involvement has no doubt helped Jive to this point. Of course, having market-leading functionality hasn't hurt. (Jive has featured highly in recent Forrester Wave reports).
At the recent Enterprise 2.0 conference in Boston, I sat down with Jive’s new CEO, Tony Zingale, to explore the company strategy. From our discussion, it was apparent that Jive intends to compete for a big slice of the enterprise collaboration marketplace. Fundamentally, this is the right direction for Jive, but I foresee some big challenges for the company along the way.
There has been a lot of negative press and commentary regarding the recent Queensland Health Implementation of Continuity Project (SAP HR and Payroll), which recently experienced a very public failure as many employees were not paid due to multiple points of failure in the project. The recent Auditor-General's Report on the process is damning, spreading the blame across multiple agencies and the systems integration partner, IBM. I make no claims to be familiar with the intricate details of the process, but I have read the report and feel I have a clear understanding of the (many!) points of failure.
While this project did seem to be a monumental failure, I would suggest that we consider two important facts: