Thank you for all the comments and responses you sent. I received several detailed emails as well as posted comments that provided useful insight into the challenges that you face when customizing VIsual Studio Team Foundation.

A common theme in several of your responses pointed to a need to track all the different elements that can be customized from an end-to-end perspective.

Here is a summary of the customization scenarios that you indicated are important:

• Customizing  work item work flow - states, reasons, roles, and transitions.
• Customizing  VSTF to meet process requirements AND updating process to leverage VSTF  features.
• End-to-end guidance  that addresses iteration and area paths, work item tracking, queries,  reporting, dashboards, and process guidance.
• End-to-end guidance  that addresses work item tracking, version control, test, and build.
• End-to-end guidance  for customizing an existing process template.
• Guidance on keeping customized areas in sync.
• Add fields and then use them in reports and data warehouse reporting.
• Keeping/knowing what to keep in sync when customizing a work item tracking object.
• Updating reports to reflect information tracked with customized work items.
• Creating and viewing hierarchies of customized work items.
  The good news here is that VSTF 2010 Beta 1 addresses this with the addition of specific  link types and the ability to add customize link types. For more information, see Customizing How Work Items are Related through Link Types.
• Managing projects using Project Server that contained customized work items.
  There may have been a number of problems encountered here. The enhanced integration of Office Project with VSTS 2010 Beta 1 addresses a number of the round trip problems experienced previously. For more information, see Quick Tips and Operational Differences when Tracking Tasks Using Office Project and Team Foundation.
• Updating Process Guidance content to reflect changes made to customized processes.

The above scenarios identify many useful areas to address through documentation. I'm adding them to my backlog of content to develop for VSTS 2010. 

As a next step, I plan to post a working draft that lists the objects and elements that are subject to customization, the interfaces used to support them, and links to VSTF 2010 Beta 1 topics that provide information on how to customize them.

Please continue to provide feedback on the content that is most important to you when customizing Visual Studio Team Foundation.

Thanks,

Kathryn