Microsoft Team Foundation Server 2010 and Microsoft Project Server Integration Feature Pack
Updated: June 2011
By installing Microsoft Visual Studio Team Foundation Server 2010 and Project Server Integration Feature Pack, project managers can use Project Server to access up-to-date project status and resource availability across agile and formal software teams who work in Team Foundation. This integration enables data to flow from work items in Team Foundation Server to tasks in enterprise project plans in Project Server. With this feature pack, project managers and software development teams can use the tools that they prefer, work at the level of precision that supports their needs, and share information transparently. After the two server products are configured, the synchronization engine maintains scheduling data and resource usage for the configured data in the mapped enterprise project plan and team project.
To enable this flow of data, you must install the feature pack on the App Tier servers for Microsoft Project Server 2007 with Service Pack 2 (SP2) or Project Server 2010. This step enables integration with Team Foundation Server 2010 with Service Pack 1 (SP1). Project managers that use Project Professional 2007 or Project Professional 2010 must install Visual Studio 2010 SP1 on their client computers.
In this topic
You can download a virtual machine that demonstrates how to integrate Team Foundation Server and Project Server 2010 to allow teams to share data between the two server products. This virtual machine includes enterprise project plans in Project Server that are mapped to team projects in Team Foundation Server, along with sample data to highlight key integration scenarios. The walkthrough documents illustrate four scenarios that simulate the interactions between the project manager, who is working in Project Server, and members of the software development team, who are working in Team Foundation Server. For more information, see the following page on the Microsoft website: Microsoft Team Foundation Server 2010 and Microsoft Project Server 2010 Integration Hyper-V Virtual Machine.
Review setup, configuration, and administration tasks that are required to integrate the two server products. As an administrator for the integration of Team Foundation Server 2010 and Project Server, you must configure the integration of the two server products to support the flow of data from team projects to enterprise project plans. For the initial configuration, you must install software, grant permissions, register instances of Project Web Access or Project Web App (PWA), and map components of Project Server to components of Team Foundation.
Plan the integration of the two server products. To synchronize data between Team Foundation Server 2010 and Project Server, you must install service packs and feature packs on those machines that you will use to configure the integration and manage projects by using Project Professional. To understand how you will configure the integration of the two server products, you should understand how components in Project Server map to components in Team Foundation.
Configure the integration to support a test or evaluation environment. You can use this topic as a quick reference to install software, assign permissions, configure integration, and verify data synchronization.
Configure the integration to support a production environment. You can use this topic to collect the information that you require for configuration, permissions that you must grant, and configuration tasks that you must perform to support a customized integration of the two server products.
Grant permissions to support configuration and data synchronization. You must grant permissions to administrators, service accounts, and team members. You must also make sure that specific service accounts have access to the Shared Services Provider (SSP) for the server that hosts SharePoint Products for Project Server 2007.
Manage and modify the integration of synchronized components. You can change how components are mapped or list the current mappings by using the TfsAdmin command-line tool. You can review the options and parameters that this tool provides and learn about the operations that specific options perform.
Understand the three types of synchronization that occur. The synchronization engine performs three types of synchronization: publishing, status, and approval. This process captures and maintains task-related and resource-related data in both Team Foundation Server and Project Server while respecting the ownership of data by the project manager in the project plan.
Choose how you want to manage projects. You can configure the integration to support the specific manner in which you want to manage projects. You can define high-level deliverables or both deliverables and tasks, you can just review progress that the development team reports, or you can combine these methods.
Understand the synchronization process and features. You can manage the project plans that map to team projects and the tasks that are synchronized with work items in Team Foundation.
Create resource assignments, and view resource utilization. When the development team breaks down requirements and tasks into child tasks, you can see how work and resources roll up through the project. You can use this information to view resource allocation and work estimates, perform resource leveling, and determine whether a resource is over-allocated within a project or across multiple projects.
Review deliverables, define tasks, and estimate work. For each deliverable that is submitted to Project Server, you define and estimate the tasks that are required to implement that deliverable. As you perform work, you update your task hours, which are automatically submitted to Project Server and the project manager for review.
Review work breakdown, and update work. As a development lead, you can use the Work Breakdown team query to review the work items that a project manager submits. As work progresses, team members update their task hours, which are automatically submitted to Project Server and the project manager for review.
Define and submit user stories or requirements to Project Server. As a development lead, you provide visibility into the project schedule and resource utilization by opening the Product Planning workbook and setting the Project Server Submit field to Yes for those user stories or requirements on which your team is working.
Find and address rejected work item submissions. When the project manager rejects an update to a work item, you must address the reason for the rejection and resubmit it to Project Server. Until you complete this task, the work item can no longer participate in data synchronization.
Resolving Conflicts and Managing Rejected Work Item Submissions
The following videos, which are available from the Microsoft website, illustrate the flexibility that you have to manage the product lifecycle after you integrate the two server products.