Team Foundation Server 中不同的工作项有何用途？
在您尝试将其标记为“太有争议”之前，请先阅读整个问题。我实际上是第一次使用 Team Foundation Server 设置我的项目管理/错误跟踪环境（我之前使用过 JIRA、Mantis 和其他一些 PM 软件）。我非常了解如何将团队基础用于源代码控制之外的其他任何事情。
我确实在尝试将工作项用于它们的预期用途。话虽如此，我想确保当我添加新的工作项目时，我对它们进行了正确的分类。
当我选择添加工作项时，如果有以下选项可供选择：
1）Bug
2)问题
3)共享步骤
4)任务
5)测试用例
6）用户故事
显然我知道错误的分类，这不是让我困惑的地方。我真正想知道的是，问题如何分类？从技术上讲，任务是如何分类的？什么是用户故事？ 我知道对此
可能会有一些意见，但我真的在努力组织该项目，并将所有这些正确地分开。
Please read this entire question before you try to mark this as "too controversial". I am actually setting up my Project Management/Bug Tracking environment with Team Foundation Server for the first time(I have used JIRA,Mantis and some other PM software before). I am fairly knew to using team foundation to anything else besides source control.
I am really trying to use the Work Items for what they were intended to be used for. Having said that, I want to make sure that when I am adding new work items, I am classifying them correctly.
When I choose to add a work Item, If have the following options to select from:
1)Bug
2)Issue
3)Shared Step
4)Task
5)Test Case
6)User Story
Obviously I am aware of what classifies a bug, this is not what is confusing me. What I would really like to know is, what classifies an issue? What technically classifies a Task? What is a user story? etc.
I know there may be some opinion in this, but I am really trying to organize the project, and separate all of these correctly.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
这个问题讨论了一些内容你在这里提到过
This question talks about some of the stuff you've mentioned here
您可以在此处。当您创建团队项目时，您应该会在完成后收到一个选项来阅读流程指南。如果您选择 MSF Agile 5.0，这也将是您的目标。另请查看 VS Scrum 流程模板。它非常简单，并且与任何工具或流程指南一样忠实于 Scrum。它是带外提供的，但将包含在 TFS 的下一版本（如果不是 SP1）中。
You can find the MSF Agile 5.0 process template guidance here. When you create a team project you should receive an option, after it's complete to read the process guidance. This is what that will take you too if you choose MSF Agile 5.0. Also take a look at the VS Scrum Process Template. It's very simple and as true to Scrum as any tool or process guidance. It was shipped out-of-band, but will be included in the next version of TFS (if not SP1).