Integrating MSP Desktop, SharePoint, and/or Groove...

From the Project Management 2.0 Blog
New technologies, concepts, and Web 2.0 tools are popping up everywhere. How can you use them to help your project team collaborate, communicate - or just give your project an extra boost? [Contact Dave]

About this Blog


Recent Posts

Are You Prepping For The PMP 24/7?

Are You Just Too Darn Busy?

Eliciting Requirements... Creatively!

What To Expect When Your Stakeholders Are Expecting

8 More Templates to Save You Time

Situation: You need to bridge MSProject Desktop, SharePoint and/or Groove

John Milan, Senior Architect and Founder of Team Direction recently sent me a message regarding a new software add-in they've created for MS Project.  I asked him about some specific value points - sort of a "this would valuable to a company if..." angle.  Here are his responses.

TeamDirection would be valuable to a company if they...

1. Already have MS Project 2003 licenses for everyone on projects.

TeamDirection does not require licenses for everyone on projects. What you saw in the demo is the ability to publish and synchronize tasks from MS Project (2003 and 2007 supported, btw) to a SharePoint Task List (again 2003 and 2007 supported). Team members can then participate in the project via their browser. Since SharePoint services ship with Windows Server 2003, this can be very cost effective.

2. Already have SharePoint or Groove licenses for everyone Yes. Again we work with the SharePoint services shipping with Windows Server 2003, or we work with hosted providers running portal and SharePoint 2007. And, if you're an enterprise MS Office customer, Groove will be available.

3. Want to sitck with Tools they already have in house and are used to. Though its difficult to describe, rather than changing the process to fit our software, our software adapts to a company's process. For example, we also have a product that integrates with Mindjet MindManager and publishes topics to SharePoint and Groove. We also have another rich desktop that people can deploy so any user can see a rich gantt view of projects. And our features try to anticipate user needs to communicating in order to complete projects-- integration with Windows messenger for example.

4. Do not want to take on a big implementation effort.  MS Project *Server* 2007 is built on the SharePoint platform, but you have to be willing to jump into that IT/Consulting pool to get to it. MS Project standard does not give you Project Server/SharePoint capabilities, you must use Project Professional. MS Project Professional out of the box does not talk with SharePoint, you must purchase Project Server. And even then, MS Project does not work with Groove-- the third leg of Microsoft's collaboration group.  We work with MS Project Standard, Professional, SharePoint and Groove right out of the box.

Posted on: February 09, 2007 05:31 PM | Permalink

Comments (2)

Please login or join to subscribe to this item
Have downloaded the 15 day eval copy of this and it seems pretty functional - only interested in MS Project Add-In

Would be interested in other peoples feedback and opinion.

Great article! Our company planned to bridge MS Project Desktop, SharePoint, but not including Groove. It is very functional!

Please Login/Register to leave a comment.


"What is wanted is not the will to believe, but the wish to find out, which is the exact opposite."

- Bertrand Russell