我们正在设置 TFS 2010，并且有大约 15 个不同的应用程序想要迁移到 TFS。我们已经决定做1个系列了。我的问题是，我们应该为每个应用程序创建多个团队项目，还是应该将所有应用程序放在一个团队项目下？对于工作项、构建等这些场景，我们将面临哪些优点/缺点？
We are setting up TFS 2010 and we have about 15 different applications we would like to migrate to TFS. We have already decided that we will do 1 collection. The question I have is should we create multiple team projects for each of our applications or should we put all of our applications under one team project? What are the advantages/disadvantages we would face with those scenarios for work items, builds, etc?
发布评论
评论（2）
我对团队项目中应该包含的内容的标准是应用程序和/或处理应用程序的人员是否共享资源，例如工作项目。
在即将推出的 TFS11 中，存在积压的概念（如果您还没有看到它，我建议转到 \BUILD\ 录音）。如果您的应用程序共享冲刺或积压工作，那么我将创建一个团队项目（或为共享这些应用程序的每个应用程序池创建一个团队项目）。
如果应用程序是单独开发的并且您想要使用不同的流程，那么请使用多个团队项目。
My bar for what should be in a team project is whether the applications and/or people working on the applciations have shared resources, like the work items.
In the upcoming TFS11 there is the notion of backlogs (if you haven't seen it yet, I recommend to go to the \BUILD\ recordings). If your applications share the sprints or backlogs, then I would create one team project (or a team project per pool of applications that share these).
If the applications are developed seperately and you want to use different processes, then use multiple team projects.
最近，我看到一位 TFS ALM Rangers 发表了一篇关于此问题的好帖子，其中讨论了拆分为多个团队项目的所有主要缺点。
http://msmvps.com/blogs/vstsblog/archive/2010/11/12/good-reasons-to-not-create-a-new-team-project.aspx
但是正如 Ewald 指出的那样，TFS11 中新的 Sprint、Backlog 和团队支持实际上是拆分项目的充分理由。
I saw a good post by one of the TFS ALM Rangers on this recently which goes over all the major disadvantages of splitting into multiple team projects.
http://msmvps.com/blogs/vstsblog/archive/2010/11/12/good-reasons-to-not-create-a-new-team-project.aspx
However as Ewald points out the new Sprint, Backlog and Team support in TFS11 are actually fairly good reasons to split your projects out.