Nicholas TufaroCEO| Tufaro Information SystemsHudson, Fl, United States
Hi All,
I am very curious to know how the rest of the Project Management community feels about these tools. For the storage and sharing of project communications and documents, I prefer SharePoint for its structure, version control and its ability to check documents in and out. But, I am old school.
I've tried Jive and I am not a fan. It seems more focused on "social" than "process", a Facebook for business, if you will. Perhaps I am missing something here.
Also, any thoughts on Yammer? My alumni account for the school where I attained my degree uses Yammer. Still not sure about that one either.
Only used SharePoint, so can't comment on the others. Saving Changes...
Ivo EssenbergSenior Program Manager| IDEXXHoofddorp, Netherlands
Haven't used Jive, but for me, it can be a combination of Yammer and Sharepoint, or, using the Microsoft O365 universum, Teams is the way to go.
Teams combines the chat/instant messaging/meetings from Skype, with a SharePoint site, storage and the ability to link to other sources of data/applications. It works well for projects as you can create a Team "group" for each project.
It is still a young product and has some gaps that will be addressed in the future I'm sure, but it already has much potential.
If you don't want to go that way, an embedded Yammer feed in your SharePoint site can also offer that combination of idea exchange with the more formal document storage and list management. Saving Changes...
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
I +1 Ivo here.
The O365 ecosystem is a great option. Also, have used Jive. You are correct, and that is it's intent, to be of a social/collaborative platform. Whereas there were certainly gaps in its functionality, it was great for discussions and bringing people together. Overall, though, and dependent on the internal organizations current capabilities, SharePoint is probably the most useful way forward. If a Microsoft stack org, Jive will be a disparate solution, while SharePoint/O365 will be integrated and more so enable work and sharing of content. Which is the goal, right, to bring people to the content.
...
1 reply by Ivo Essenberg
Oct 24, 2018 10:05 AM
Ivo Essenberg
...
And an added benefit of an integrated platform such as O365 is the search capability, which will go across all parts of the platform.
Saving Changes...
Ivo EssenbergSenior Program Manager| IDEXXHoofddorp, Netherlands
Oct 24, 2018 6:28 AM
Replying to Drew Craig
...
I +1 Ivo here.
The O365 ecosystem is a great option. Also, have used Jive. You are correct, and that is it's intent, to be of a social/collaborative platform. Whereas there were certainly gaps in its functionality, it was great for discussions and bringing people together. Overall, though, and dependent on the internal organizations current capabilities, SharePoint is probably the most useful way forward. If a Microsoft stack org, Jive will be a disparate solution, while SharePoint/O365 will be integrated and more so enable work and sharing of content. Which is the goal, right, to bring people to the content.
And an added benefit of an integrated platform such as O365 is the search capability, which will go across all parts of the platform. Saving Changes...
SharePoint, because of its screen-sharing and calendar-sharing features. Saving Changes...
Frank ValdiviaDirector of Analytics| Heifer InternationalShoreview, Mn, United States
Agree, Sharepoint for content management as you described and the other for "social" Saving Changes...
Elaine DiMasiProject Manager specializing in High Tech Instrumentation| Lawrence Berkeley National LaboratoryOakland, Ca, United States
Our company's Sharepoint faced a few problems. One, it quickly became unmanageable for lack of a strict file hierarchy or indexing. People put docs and pages "wherever" and only the search tools would eventually find them. Nobody ever cleaned up old drafts. Two, it wasn't possible to put a public-facing page of documents for stakeholders outside the firewall, so more web spaces had to be built for that also. In practice we had three sites with different kinds of version control. Sharepoint for "everything" plus formal pages for internal reviews; web pages for posting docs for external reviews; and Vault for controlling all CAD drawings and models under its release system.
... So then I built *another* sharepoint page for my control account, which had a table, updated by hand, showing where to find all our other pages...
How large typically are the projects you're managing? Saving Changes...
I prefer Teams because it also uses the basics of Sharepoint for a central page. I come from a regulated industry so we have to be able to find documents quickly. Saving Changes...
