View Single Post
  #2 (permalink)  
Old September 15th, 2010, 04:28 PM
briankel briankel is offline
Wrox Author
 
Join Date: Mar 2010
Posts: 9
Thanks: 0
Thanked 1 Time in 1 Post
Default

Apologies, Chris! I missed this question until now.

In TFS 2010, each Team Project should contain an entire product. The value of TFS is to help the team build the product by working collaboratively and with visibility to each other’s parts of the products which are divided by area paths. If a Program Management Office needs visibility across Team Projects, they are able to write queries which can be viewed in Team Explorer to track things like cross project dependencies. Reports can be created to view cross Team Project progress. Splitting a product into different Team Projects has limitations as the product team is unable to export/import work item with tools like Excel and MS Project client integration as they have a single team project limitation. If building cross Team Project schedules is required, the team can use MS Projects master plan capabilities to roll up multiple TFS bound project plans.

To further support visibility to the PMO, TFS is in the process of build integration Project Server 2007 and 2010. You can learn more about this feature by downloading the CTP found here: http://go.microsoft.com/fwlink/?LinkID=196413. Please give the team your comment on this forum site found here: http://social.msdn.microsoft.com/For...sprojectsrvint

Hope that helps,
Brian Keller