Visual-studio – TFS Basic for Non-Visual Studio Projects

The answer to this question requires some planning on your part: how you intend to use TFS, and which of those capabilities has inherent limitations in the product. I would summarize my advice as:

1. You will need [at least] 1 team project per process template. That is, if two teams want to adopt / customize different processes, they will need to be separated.

2. Once condition #1 is satisfied, you probably don't need as many separate Team Projects as you think. 90% of TFS features & settings are hierarchical in nature, allowing you to scope them as broadly or narrowly as each of your projects requires.

For complete details, see:

• http://www.codeplex.com/BranchingGuidance/Wiki/View.aspx?title=Guidance%20for%20Structuring%20Team%20Projects
• http://blogs.msdn.com/richardb/archive/2007/05/01/tfs-team-project-whitepaper.aspx
• http://msdn2.microsoft.com/en-us/library/aa974183(vs.80).aspx

The are a number of choices (most costing money):

1. Team System Web Access
   Team System Web Access (formerly known as TeamPlain) is a Web interface to Visual Studio 2005 Team Foundation Server. Team System Web Access is available as a free download for existing Team Foundation Server users, and will be incorporated into a future release of Visual Studio Team System.

2. Work Item Only View
   Team System Web Access provides a work item only view that restricts functionality so that you can create and view only your own work items. This view is designed to facilitate working with Team Foundation Server when you do not have a client access license (CAL). You do not need a CAL to create new work items or to view and update work items that you created. The work item only view restricts functionality so that you are in compliance with this aspect of the Team Foundation Server end user license agreement. For more information, see Visual Studio Team System 2008 Licensing White Paper.

3. Outlook integration (from Brian Harry's blog)
   Integration of Team Foundation Server work items into the Outlook user experience continues to be a popular area for innovation. Just recently an author sent me mail about a new one called Wit-It! that enables work item forms to be easily opened from TFS work item change notifications. It's not entirely unlike configuring links to Team System Web Access from event notifications but it uses local rich client UI that some will like better.

   There are several other Outlook extension offerings out there with varying levels of completeness. If it's an area that iterests you, you can also check out:

   TeamExpand

   TeamLook

   TeamCompanion

   And I appologize if I left any out. As I say, clearly there is a lot of interest here and some creative people.