Atlassian Blogs

Comments (2)

• 

  I have had 2 Wiki deployments completely nixed and one that I think is being slowed immensely because of existing Microsoft Sharepoint installations.
  The 2 Wiki deployments that were shut down completely after IT in large organizations went to management and complained of redundancy. They claimed that their costly Microsoft Sharepoint installation was a Wiki and people were creating redundant system. Users felt differently they didn’t feel at all in control over changes on the Sharepoint installation.
  The 3rd group, their Wiki adoption has been greatly slowed by a prior bad experience with Sharepoint which I think has left most people very scared of the Wiki and what it will or won’t do.
  Any other experiences of Sharepoint Shock? Also these were all in development groups.

  By Kin Lane on May 31, 2007 / Reply

• 

  I’m also trying to replace Sharepoint with Confluence. Many of our groups want something more powerful than Sharepoint (though some don’t and it doesn’t cost us anything to keep Sharepoint around). Our problem is that folks do not want to give up certain features of Sharepoint. The main one is being able to use WebDAV to directly add and edit Office documents as MHT files to a document store. This IS possible with Confluence (with the WebDAV plugin) – but it sure is clumsy. Frankly, Confluence could really do more to help folks that want to migrate from Sharepoint by making editin via Office apps a more streamlined process.

  By Ray Johnson on June 13, 2007 / Reply