TFS结构-多个项目还是单个项目? [英] TFS Structure - Multiple Projects or Single Project?

查看:93
本文介绍了TFS结构-多个项目还是单个项目?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们的小型开发机构正在寻求将我们的项目从VSS迁移到TFS,并且我们正在评估TFS与其他项目的比较(尚未触发).我们软件商店的性质使得我们在VSS中有100多个项目,从小型的单人演示项目到大型的企业级应用程序.

Our small development shop is looking to migrate our projects from VSS to TFS, and we're evaluating TFS vs. others (haven't pulled the trigger quite yet). The nature of our software shop is such that we have 100+ projects in VSS ranging from small one-man-show projects to massive enterprise-wide applications.

我们正在尝试确定在过渡过程中如何构建项目,并且在很大程度上决定将所有内容放到一个项目站点/系统中,每个项目都从根目录开始有一个子文件夹.

We are trying to determine how to structure our projects in the transition and have, for the most part, decided on putting everything into one project site/system with each project having a subfolder off the root.

使用这种类型的设置,我们担心我们将失去TFS提供的许多功能(错误跟踪,scrum烧录,报告,文档存储等),因为所有项目都将位于同一个门户网站/项目中空间,很难将各个项目的票证/项目分开.

With this type of setup, we are concerned that we will lose a lot of the functionality that TFS provides (bug tracking, scrum burndowns, reporting, document storage etc.) because all the projects will be in the same portal/project space and it will be difficult to separate out individual project tickets/items.

有人对此有经验吗?您的解决方案是什么?您坚持使用TFS吗?

Does anyone have experience with this? What was your solution? Did you stick with TFS?

推荐答案

这个问题的答案需要您自己作一些计划:您打算如何使用TFS,以及哪些功能在产品中具有固有的局限性.我的建议总结如下:

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. 每个流程模板您将需要[至少] 1个团队项目.也就是说,如果两个团队要采用/自定义不同的流程,则需要将它们分开.

  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.

一旦满足条件#1,您可能就不需要您想象的那么多独立的团队项目. 90%的TFS功能和设置本质上是分层的,可让您根据每个项目的需要对它们进行宽泛或狭窄的范围设置.

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

这篇关于TFS结构-多个项目还是单个项目?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆