In October, I published a provocative research note entitled Maverick* Research: Should Microsoft Kill SharePoint? It may have been provocative at the time, but announcements from this year’s SharePoint Conference show that at least in one aspect, I was too optimistic.
The note looked at the expected split coming between SharePoint on premises (which is how most users currently deploy the product) and in the cloud (as part of Office 365). It paints a bleak picture for SharePoint on premises in the long term, with its users destined to become second class citizens, lagging ever further behind the shiny, new innovations coming in Yammer and SharePoint Online.
If anything, today’s announcements are even more bleak for SharePoint on premises. I said:
SharePoint Server continues to be supported and developed, with new versions expected at pretty much the same schedule as with earlier versions.
That was apparently too optimistic. In a blog post today, SharePoint general manager Jared Spataro made clear that they are “committing to another on premises release of SharePoint Server.” Another. As in one more. So there will not be new versions, but one more before the curtain falls on SharePoint as most users now know it.
We will be publishing a longer analysis of the SharePoint Conference announcements, which include quite a bit of good news for those looking for innovative functionality from the cloud. I will also be updating my “Should Microsoft Kill SharePoint” presentation for the Gartner PCC conference in Los Angeles in May.
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.