Sharepoint 2010 vs Jive SBS

We are a big sharepoint shop as well.  Currently on SP 2007 moving to 2010.  However 2010 does not compare at all to Jive on its own.  We did the analysis almost 9 months ago so my memory is fading. I recall that thei rmicrobloggin functionality was very poor.  It was a one and done sort of thing where you could not reply to a thread...it was just not very good.  It also required a lot more technical expertise to make it usable whereas Jive adds value right out of the shrink-wrap.  Sharepoint has better success when they partner with Newsgator or other third parties...but the costs start to mount there as well.   We do plan on using SP connector at some point, but right now focused on our Jive internal launch and we'll work on that in the next phase.

We had the same situation. We did a POC with SharePoint 2010...since our existing site was highly customized Sharepoint 2007 and was at the end of its useful life. Similar to Andrew, we found many areas where Sharepoint would require some work to get it to where we needed. I know alerts remained at the page level on 2010....as well as the microblogging not being as strong. Further, with going SaaS with Jive, we got a solid product with a roadmap. With a very small team and only 2 developers max, Sharepoint wasn't a viable option for us...it would require far more investment...so that is what formed the basis of our decision (1) feature set and roadmap with level of resource and (2) total cost of ownership

We do use the SP connector to tie our Jive implementation to our corporate SP based portal.

In terms of SP vs. Jive, here's the basic comparison we did about a year ago.

(This is for your use, but not for attibution or replication):

I pretty well agree with everything Roy Wilsker has said in the previous post.

We have one small instance of Jive running (hosted) and are a big SharePoint shop and are engaged in a nauseatingly exhaustive evaluation of Jive and SharePoint 2010 - we currently have WSS 2003 and are evaluating the possibility of upgrading to 2010 Server.  In a nutshell:  SharePoint 2010 is simply not competitive with Jive as a social platform - but SP2010 may be strategic to you for other reasons - content management and it's abilities as a 'development light' platform.  Having said that, the combination of SharePoint 2010 and the NewsGator plugin - which is what we are evaluating -  makes it much more difficult to choose between the 2 based strictly on features and functionality.  The major gap we see in Jive is lack of wiki functionality and the inability to manage nested document structures - but we haven't ruled out both SP and Jive and Jive has a pretty decent SP integration.  For SharePoint the issue is mostly usability (partially fixable by way of a development effort - but we have a tough time assessing the scope of this) and some pretty clunky functionality (eg: can't comment on a document) - but NewsGator is doing a good job of filling these gaps.  The slow Microsoft release cycle is mitigated by the speed with which NewsGator adds new features.

Hey Ashley!

We have SharePoint 2007 and Jive 4.5 with the SharePoint Connector. Now that we have Jive it is effecting the SharePoint instance (i.e. how it's organized, the features we enable/disable, etc.). For example, SharePoint has MySites and Jive has Profiles...do we keep both? Sync them? Disable one? Where do we tell users to upload content SharePoint or Jive or both depending on the type of content? The plan of attack is to identify feature overlap...what features do each system share and which system does that task better? Add to that, of course, our user's needs so we can clean things up and remove unnecessary clutter and overcomplicated features that aren't needed. We're developing a user survey to find out what users and site owners heavily use in SharePoint. We will analyze the findings and create a plan for our SharePoint instance keeping in mind the user needs and our plans with Jive. We will also look at the survey findings to see if upgrading SharePoint to 2010 is needed, or not. I'm happy to discuss our plan if you're interested.

Thanks!

Natalie

We did a reivew of Jive 4.x, SharePoint 2010 and Saba Social, before ultimately choosing Jive 4.x. Note our company still uses SharePoint 2007 and Saba Learning. My takeaways:

• I did not review NewsGator + SP2010. But I think you could make that solution work if your requirements for user experience are not high.
  
• At the time I felt Saba Social was not quite ready to compete with Jive 4.x. Though this was 8 months ago and Saba may have improved since then.
• SharePoint 2007/2010 has certain features that make it a complelling solution in the enterprise, as long as you are willing to customize and improve the out-of-box experience.
• I felt that Jive 4.x was a better match for our needs than SharePoint 2010 out of the box.

The attached ppt is how I've been thinking of SP vs Jive. Depending on your own company requirements, there is a case for both platforms. We also have the Jive SharePoint connector and after a rough start with the integration, it works well for search integration.

Gian...

Here is a related discussion, for those interested in replacing SharePoint vs co-existing with it (both are good!): What systems/apps have you replaced with Jive?

One option we used while I was at Kaiser was to use SharePoint as the repository of choice and primarily for the check-in and check-out features as well as the better calendaring and project management tools set. We used the Jive SharePoint connector and continued to use Jive as the Social engagement vehicle.

Hope that helps.

Noreen

My company (ThreeWill) is in the middle of writing a white paper on a this subject (with help from Jive and some of the customers who have deployed the SharePoint Connector) - look for a follow up response from me in a couple of weeks with the update on this.  The white paper is due for completion at the end of August.  I'll definitely post a link to the white paper on this thread. 

We cover everything from a comparision of SharePoint vs Jive to pro/cons of options to make SharePoint more social (including the SharePoint Connector/Jive, Newsgator, Yammer, Chatter, and (heaven forbid) building the social functionality into SharePoint yourself).  Which option you go with really depends on a number of factors that we try to spell out...we're hoping that this white paper can bring a lot of clarity to this subject since we are talking to people about this every day.  And the Jive + SharePoint story has incredible momentum for companies that have mature viewpoints of both products.

Also, we've created a SharePoint Lists app for the new Jive Apps Market (part of Jive Five).  Keep an eye on this as a lightweight option for SharePoint integration with Jive.  More info on this - http://threewill.com/sharepoint-lists-for-jive/

If I can help anyone in the meantime with this subject, just let me know...

Deirdre Walsh - could you set this up for me today?  I'd like the ability to invite others to the space and if you could set this up a secret space that would work well for our purposes.  Feel free to ask questions and guide me through this (haven't done this yet).

These are all some great discussions here, so I figured I'll just add my document I did last year comparing the two.

I've been working as a developer and architect with SharePoint for a few years, and I think the 2010 version of SharePoint makes more sense now from a content management perspective now, than the 2007. People tend to forget that SharePoint is an application platform (the out-of-the-box part of sharepoint would be the high resolution permission and version handling) rather than en off-the-shelve product (I’ve built patient/journal systems/logistics and tracking systems as well as regular intranets), and focus end up on the different site definitions deployed as a part of the SharePoint package (I like the glorified storage space comment :-)).

With Jive, the “big discussion” becomes supported. The one not tied to the specific project or the specific organization, but the one derived based out of interest or need rather than an assigned task. So difficult to compare, they both can be implemented in so many ways. According to me, you can bend and modify SharePoint a whole lot more (since you start from scratch basically :=), but Jive is a more appealing and user friendly experience from the beginning.

And, the most important part I guess. Jive enables a way to transform the way you do business, in that sense that you can collaborate around a process by utilizing the “social flavor” that Jive has. Regardless if it is getting all the right stakeholders and roles in insurance claim and collaborate around that, to peer2peer networking and crowdsourcing in a high-tech external communities.

Thank you all!

(it took me an hour to reviewall the content but it was worthwhile)

We are starting to deploy Jive (cloud) meanwhile we have "offcial collaboration" with SPS2007. I'm very interested in technical integration and functional overlaping concerns

Regars

We are a Sharepoint Shop.  We have been running it since WSS 2.0 and now I just released MOSS 2010.  I am also in the process of evaluating Jive to see if this will meet the needs of the user community for -micro-blogging and social networking.  It will be interesting to see how these two play together.  Once I have some testing done, I'll let you all know.

Do you have same for Sharepoint 2013, many customer starting to talking Sharepoint 2013 has everything and no need new Social Business Solution jike jive or top of Sharepoint.

Is there any new comparison list Jive vs SP 2013

I want to share a benchmark between Jive and Sharepoint 2013. You can select the importance of every feature for the customer and get a global result.

Enjoy! ;-)

I'm seeing Microsoft position a combination of Yammer and SharePoint as their competition to Jive. Yammer acts both as a standalone IM client and as a widget within SharePoint sites.

Has anyone evaluated this combination? I'd be interested in:

• How well the parts work together from an end user POV
• How much effort is needed to maintain the combined technologies
• How the combination compares to Jive.