Project Standard versus Project Pro
My IS Support team removed Project Pro and installed Project Standard on my VS Team client workstation which interfaces to TFS. I have a Universal MSDN contract which includes Project Pro. The statement from IS is as follows:
"After a lot of research with Microsoft, I have learned that the only benefit of using MS Project 2003 Pro is to interact with MS Project Server. Microsoft confirms that there is no benefit of using Project 2003 Pro with Visual Studio Team System Server. If you do not agree, please provide the details from an authorized source and I will reconsider your request."
My understanding was that TFS would eventually connect and use the Project server. We have a Project server. I also understood that Project Pro can access Project Portals and that these were used in the TFS.
Could someone elaborate on my (mis)understandings and the statement above? Maybe a definitive list of the pros and cons of Project STandard versus Project Pro in a TFS environment?
Thanks in advance.
Tony
[1805 byte] By [
TonyH] at [2007-12-18]
TFS can be used with project plans managed by Project Server, so it is not right to say that there is no benefit to using Project 2003 Pro. If you have a Project Server deployment and are using Project 2003 Pro to interact with your server to manage a portfolio of project plans and to apply global templates, TFS MS Project integration features can be used in a complementary way to push the project plan details into the Work Item Tracking system. This allows the tasks from the project plan to be linked to defects and other artifacts in the system, and more generally, to surface in all of the TFS-views on Work Items (e.g., VS, Excel, Reports). There is no direct connection between the tasks in the Work Item Tracking store and the tasks stored in Project Server - synchronization happens on the client manually through the TFS MS Project add-in. Deeper integration between TFS and Project Server is possible and is definitely part of the future plans. See:
http://www.gotdotnet.com/workspaces/workspace.aspx?id=b9f69ea5-ace1-4a21-846f-6222a507cc9c
I understand your answer, and it has the same information that I had.
However, what specific functionality do I lose when using Project Standard in this environment? Is it only items relating to the Project Server? I know the TFS MS Project add-in "kind of" works with Project Standard. Does it work better with Pro?
Bottom line, I still need a definite benefit stated by an "authorized source" to justify Pro, not just the fact that I have a license.
The TFS MS Project add-in is the same for Std and Pro and provides the same features in both environments. The benefit you lose with Std is in the loss of access to Project Server.
Bill,
could you comment on the first comment to the http://blog.accentient.com/PermaLink,guid,c5f34863-0c5e-4b6a-8c25-c45649caebbc.aspx blog entry stating that there may be no project server TFS connector for the RTM version of the TFS.
Hoping that this will not be the case, could you or anyone else from MS give any more info on when is a newer, TFS RC compatible, version of the connector to be expected.
Thanks,
Ognjen
At the
http://blogs.msdn.com/govdev/archive/2006/01/03/508801.aspx
website, they state that Project Pro is required to access the TFS if you do not have VSTE. Specifically "Note: Project Pro integrates with TFS, Project Std does not.". Is this true? See below:
Do I need a CAL to access TFS?
A couple of you have asked this question is different forms. Someone recently posted a comment asking whether they need a CAL to access TFS if they have MS Project. Here are some pointers:
If you have (Project Pro) AND (Visual Studio Team Edition or Team Suite), you DO NOT need an additional CAL to access TFS via Project Pro.
If you do not have (Visual Studio Team Edition or Team Suite), YOU NEED an additional CAL to access TFS.
Note: Project Pro integrates with TFS, Project Std does not.
If you are a project manager who does not have/does not need Visual Studio Team Edition/Team Suite, you can simply buy a CAL to access TFS via Project Pro or Excel. If you are a project manager who also has Visual Studio Team Edition or Team Suite, you do not need an additional CAL for yourself.
If you have Visual Studio 2005 Professional, you NEED an additional CAL to access TFS.
The retail price for a CAL is approx $500. Govt customers, as well as volume licence customers, can expect to get a 25-30% discount (depending on your agreement).
Hope I have added clarity and not confusion to the current state of affairs.
-Piyush
Tony - TFS works fine with either MS Project Pro or Std. I posted a response to the blog posting indicating that MS Project Std is supported.
Ognjen - Your question has not been lost... I am looking into it and will post a response soon.
Sorry: Got the gist but the wrong question . . . and not to beat a dead horse, but it keeps squirming . . .
For non-VSTS or non-VSTE users who will be using Project to work with TFS projects. the blog statement was that they would need a CAL and Project Pro.
We will hava project managers using Project to manage TFS projects who do not have Visual Studio. We will be purchasing a CAL for some of them so that they can access the Source Control.
I understand from the blogs that Project Standard requires a "portal" which is provided through Visual Studio.
So, will non-Visual Studio users need Project Pro to get a portal to TFS?
Will non-Visual Studio users with a CAL need Project Pro to get a portal to TFS?
Bill: Thanks for the info. looking forward to it.
Tony: Not quite sure what you mean with "portal". Every TFS project has its sharepoint project portal. Maybe you have referred to it. My understanding is that in order just to glance the project data on that portal you will not need a CAL. See> http://teamsystemrocks.com/blogs/chris_menegays_weblog/archive/2006/02/07/657.aspx
But for working in the MS Project, synchronizing the Project data and the TFS wit data, publishing changes and so on, you will need a CAL.
As long as the user has a copy of a Visual Studio she is covered by a CAL coming with a VS.
Anyone without VS needs to buy a CAL.
To answer your questions directly:
"I understand from the blogs that Project Standard requires a "portal" which is provided through Visual Studio."
Project can directly access data on the TFS server. It doesn't need anything in between.
"So, will non-Visual Studio users need Project Pro to get a portal to TFS?"
In order to access a Project portal mentioned above all you need is a IE.
"Will non-Visual Studio users with a CAL need Project Pro to get a portal to TFS?"
Non VS user will need a CAL in order to connect Project (Std or Pro , doesn't meter) to TFS.
Rob Caron recently blogged about Project Server to TFS integration:
http://blogs.msdn.com/robcaron/archive/2006/02/22/537486.aspx
The article contains this update on the Project Server - VSTS Connector:
Currently, Team Foundation Server supports loose integration with Project Server by using Microsoft Project plans as a means to synchronize data between the two servers. The Project Server–Visual Studio Team System Connector (available on GotDotNet.com) is an illustrative sample solution that explains the process for more tightly integrating Project Server and Team System to deliver even greater benefits of central planning.
This integration leverages two key areas of strength for Microsoft to deliver a better solution for customers in software development. Later this year, we’ll update the Connector to work with the RTM release of Team Foundation Server. Looking further into the future, we plan to formalize and increase the level of integration between Project Server and Team Foundation Server to maximize their potential.
