Team Foundation Server - 什么流程模板适合我？
我终于能够完成 TFS 的安装并开始创建我的第一个团队项目，该项目向我介绍了流程模板。
在访问 Microsoft 网站 的链接以获取流程模板信息后，我被新的信息淹没了需要考虑的信息。 你们所有人都使用过哪些模板，这些模板要么非常适合您，要么更像是项目的绊脚石？ 您遇到的最大的优点和缺点是什么？
关于我的项目的一些信息，我是一家小公司的首席开发人员，将使用 TFS/VSTS 创建一个内联网门户来整合最终用户的日常工作并提高自动化程度以提高生产力等。这是一个全新的开发，利用了这一优势C#、ASP.NET 和 SQL Server 2008。
理想情况下，我希望利用这些功能来增强与利益相关者的协作，以帮助添加所需的功能并跟踪开发状态并提供反馈等。我还希望利用 JetBrain 的 TeamCity 来实现我的 TFS，因此如果有任何特定的模板/软件确实能够增加 TFS、TeamCity、开发人员和利益相关者之间的凝聚力，那么这正是我感兴趣的。
I finally was able to complete the installation of TFS and started the creation of my first team project which introduced me to the process template.
After following to the link to Microsoft's site for process template information I was inundated with new information to consider. What templates have all of you had experience with that either worked out very well for you or were more of a stumbling block to the project? What were the biggest advantages and disadvantages you've encountered?
Some information about my project, I'm the lead developer for a small company and will be using TFS/VSTS to create an intranet portal to consolidate the end users day to day and increase automation to enhance productivity etc. It's entirely new development taking advantage of C#, ASP.NET and SQL Server 2008.
Ideally I'd like to take advantage of features to enhance collaboration with the stake holders to help add desired features and to track the status of development and offer feedback etc. I was also looking to take advantage of JetBrain's TeamCity for my TFS so if any specific template / software really adds cohesion between TFS, TeamCity, Developers, and Stakeholders that would be ideally what I'm interested in.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（6）
吻！ 我根据敏捷工作项创建了一个自定义工作项。 就是这样，只是一项工作项目。 IT 使用“系统严重性”，客户/客户使用“业务优先级”。 还有一个“请求类型”。 通过这三个以及内置的区域和迭代，整个团队（包括客户）可以查询工作项目，以仅获取他们关心的发布的项目（或所有项目，无论发布如何）。
我根本没有对状态机进行太多修改。 这给我们留下了对每个人都非常灵活的东西。 从蓝天请求到平凡的内容/视觉错误的所有内容都可以记录在那里。
客户端使用 TFS Web Access（无限制 CAL），开发人员（我和另外 1 个人）使用 VS。 在我的上一份工作中，我创建了相同的设置，开发团队是一个 5 人的团队，而且在那里工作得更好！ 我也是那里的开发主管和技术 PM。
最大的优势是为每个人提供一个非常灵活的系统，对所有事情使用一种工作项类型。 缺点是客户需要一个学习曲线，但一旦他们知道如何使用它，他们就会最喜欢它。 建议寻找更便宜的工具来进行类似的实施，但是，我们与 MS 的 .edu 折扣是无与伦比的。
K.I.S.S.! I created a custom work item based off the Agile one. And thats it, just one work item. There is a "System Severity" that IT uses and a "Business Priority" that the client/customer uses. There is also a "Request Type". With those three along with the built in Area and Iteration the entire team, including the clients can query the work items to get only the items they care about for the release they are concerned with (or all of them regardless of the release).
I did not modify the state machine much at all. This left us with something that is very flexible for everyone. Everything from blue sky requests to the mundane content/visual bugs can be logged there.
The client uses TFS Web Access (unlimited CAL) and the devs (me and 1 other) use VS. At my last job I created the same setup, the dev team was a team of 5 and it worked even better there! I was dev lead there as well and technical PM.
The biggest advantage was having a very flexible system for everyone, when using 1 work item type for everything. The disadvantage would be a learning curve for the client, but once they knew how to use it most like it. A suggestion would be to look into cheaper tools out there for a similar implementation, but, our .edu discount with MS cant be beat.
我不得不说，您必须首先确定将用于您公司的 SDLC 的系统。 流程模板只是一个工具，如果没有很好地理解底层流程，它不仅没有帮助，而且会使事情变得更加困难。 用户采用对于 SDLC 和流程模板的成功至关重要。
我们使用Scrum for Team System。 我们选择此方法是因为我们在使用 Scrum 作为 SDLC 方法方面拥有丰富的经验。 网络上有一些优秀的书籍和文章可以帮助您快速入门。 Scrum 将把业务利益相关者整合到流程中。
在我们的系统中，产品经理全面负责产品待办事项列表项，并与我自己和 CTO 合作，将它们优先考虑到 Sprint 待办列表项中。
我们对流程模板所做的唯一更改是添加“失败测试”状态和相应的工作流程。
I would have to say that you must identify the system you will use for your company's SDLC first. The process template is merely a tool and without a good understanding of the underlying process it will not help and can make things more difficult. User adoption is crucial to the success of the SDLC and process template.
We use Scrum for Team System. We chose this due to our experience with Scrum as an SDLC methodology. There are several excellent books and articles on the web to help you get up to speed. Scrum will tie together the business stakeholders into the process.
In our system the Product Manager is in total charge of Product Backlog Items and works with myself and the CTO to prioritize them into Sprint Backlog Items.
The only change we have made to the process template was to add a "Failed Test" state and corresponding workflow.
它可能不是最适合您的模板，但我仍然想在这里提一下：XP for Team System 。 它基本上是 MSF for Agile Software Development 的简化版本：
It might not be the best template for you but I still wanted to mention it here: XP for Team System. It is basically a simplified version of MSF for Agile Software Development:
您是否已经在使用像 scrum 这样的软件开发流程？ 如果是，您可以在此处尝试此团队流程模板。
您的项目团队和项目有多大？ Microsoft 已在此处发布了其内部流程模板 (MPT) 之一。 您可以从此模板中获得一些指导和灵感。
正如 tangurena 提到的。 人们使用标准模板，稍微更改一下错误并在那里存储一些文档。 我建议也保持过程“轻松”。
然而，流程模板并不是全部。
以下是我会做的一些想法（针对您的情况）：
创建利益相关者可以创建的一些高阶工作项（功能/故事）（约束和 TFS 用户组是您的朋友）。 然后，他们可以通过 TFS 工作项 Web 访问访问其请求的功能。 这样您就不需要为他们提供 CAL
创建一些根据版本显示计划工作的报告。
设置构建自动化并根据构建从您的工作项创建报告（也称为发行说明）。
设置构建自动化并根据
恕我直言，最大的缺点是您开始相信模板是您的灵丹妙药。 不是的，这是你的起点。
TFS 生态系统为您提供了很多机会来创建适合您需求的自己的软件。 只需查看 TFS API。
Are you already using a software development process like scrum? If yes you can try this Team Process Template over here.
How large is your project team and the project? Microsoft has published one of it's internal Process Templates (MPT) over here. You can get some guidiance and inspiration from this template.
As tangurena mentioned. People use the standard templates, change the bug a bit and store some documents there. I would recommend to keep the process 'light' as well.
However the process template isn't all.
Here are some ideas what I would do (in your case):
Create some high order workitems (features/stories) which stakeholdes can create (constraints and TFS user groups are your friend). They can then access their requested features via the TFS Work Item Web Access. That way you don't need a CAL for them
Create some reports which show planned work accodring to releases.
Setup the build automation and create Reports (a.k.a. Release Notes) from your workitems according to the builds.
Imho the biggest disadvantage is that you start believing that the template is your silver bullet. It's not, it's your starting point.
The TFS ecosystem offers you alot opportunities to create own bits of software that fit your needs. Just check out the TFS API.
这是另一个不错的基于敏捷的模板（原始位于SSW，但您必须绕过登录墙）。
该模板通过为项目流程提供更强大的支持（文档、审查等），有助于增强开发人员、经理和其他利益相关者之间的凝聚力。 例如，有针对发布计划等流程元素的内置类型。
Here is another nice agile-based template (original is on SSW, but you have to get around a login wall).
This template helps enhance cohesion between developers, managers, and other stakeholders by including more robust support for project process (documentation, reviews, &c., &c.). For example, there are types built in for process elements like release plans.
一般来说，我倾向于您可以管理的尽可能小的流程。 州越多，字段越多，其中的信息就越有可能完全错误。
我们正在敏捷模板上运行我们自己的版本。 我们对其所做的大部分操作都是删除内容。
您可以使用 TFS API 将构建记录到数据库中，这将使您能够桥接 TeamCity 和 TFS。 除此之外，我可能只会使用 TFS 附带的 Web 界面，我认为您不需要为此使用第三方软件。
In general terms, I'd favour as small a process as you can manage. The more states, the more fields you have, the more likely the information in them is just plain wrong.
We're running with our own version on the Agile template. Most of what we did to it was delete stuff.
You can use the TFS API to log builds into the database, which should enable you to bridge TeamCity and TFS. Other than that, I'd probably just go with the web interface that comes with TFS, I don't think you need third party software for this.