Scrum for Team System 2010 - 如何使用故事点而不是时间
我已经使用 Scrum for Team System v3 安装了 TFS 2010。工作项模板要求您输入包含故事点的项目待办事项列表项，然后您需要将链接的任务添加为 PBI 的子项。在任务级别，您可以分配团队个人、更新预计剩余工时等。
如果单个任务使用工时，那么 PBI 项目中使用的故事点的重要性是什么？
有没有人自定义此模板，以便子工作项任务使用故事点燃尽而不是小时？另外，我希望将每个单独任务的故事点总数汇总到 PBI 项目中，作为故事点总数的只读字段。
感谢您抽出时间。
I have installed TFS 2010 using the Scrum for Team System v3. The work item templates want you to enter a Project Backlog Item that includes story points, then you need to add linked tasks as a child of the PBI. It is at the task level where you can assign team individuals, update estimated hours left, etc.
What is the importance of the Story Points used at the PBI item if individual tasks are using hours?
Has anyone customized this template so that the child work item tasks use story point burn downs instead of hours? Also, I would be nice to have the total number of story points from each individual task roll up into the PBI item as a read only field for total story points.
Thanks for your time.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我工作的公司也在使用 TFS 2010 和新的 Agile Template v5.0。我们正在按以下方式进行该过程并取得了一些成功。迄今为止，我们所做的最困难的事情是尝试让每个人都明白故事点并不直接等同于任何形式的时间。
我们从发布计划会议开始这个过程，每周进行一次，但如果您从未做过，您可能想先从一个开始。我们有3个团队，只有产品负责人和团队负责人参加会议，如果我们都在的话，管理就太大了。正是在这次发布计划会议上，我们（仅团队领导者）玩计划扑克，将故事点分配给用户故事。
然后，我们召开一次冲刺计划会议，团队、产品负责人和利益相关者将在会上就一系列用户故事达成一致，以便在冲刺中执行一个故事。经过几次冲刺后，故事点可以让您了解在一次冲刺中实际可以完成多少任务。每个用户故事都会与产品负责人讨论，通常当 Scrum Master 听到团队讨论时，他们会向用户故事添加任务。
现在产品负责人和利益相关者离开了。然后，团队开始划分工作，并为每项任务分配时间（原始估计）。完成后，团队开始工作，通常是两周，但如果冲刺无法确定为两周，我可以看到我们会进行三周的冲刺。
当我们工作时，我们会调整已完成时间和剩余时间，而不考虑最初的估计。如果到目前为止我们已经花了 3 个小时，3 个小时后我们认为任务还需要 2 个小时，那么原始估计时间是 4 个小时并不重要。
因为我们已经“填写了方框”并且没有调整模板，所以所有报告和多维数据集都可以正常工作。我们不需要对报告或任何内容进行任何大的调整来捕获一些非常好的指标。如果您想要一个更简单的模板，您应该查看 Visual Studio Gallery 中的“Microsoft Visual Studio Scrum 1.0”。它确实更简单，但提供的报告较少，并且以集成 Office 文档的方式提供的支持也较少。
Mircosoft Visual Studio Scrum 1.0
The company that I work for is also using TFS 2010 with the new Agile Template v5.0. We are going about the process in the following way and having some success. The hardest thing we have done to date is try to wrap everyone's head around the idea that Story Points do not directly equate to any form of hours.
We start the process with a Release Planning meeting, this is done once a week but if you have never done one you probably want to start with one first. We have 3 teams and only the product owners and team leaders are in the meeting, it would just be to large to manage if we were all there. It is at this Release Planning meeting that we, the team leaders only, play planning poker to assign Story Points to User Stories.
Then we have a Sprint Planning Meeting where a team and the Product Owners and Stake Holders will agree to a number of user stories to execute one in a sprint. The Story Points, after a few sprints, give you an idea of how many you can actually don in one sprint. Each User Story is discussed with the product owner and usually the Scrum Master is adding tasks to the User Stories as they hear the team talk them through.
Now the Product Owner and Stakeholders go away. The Team then goes about dividing the work amongst itself and assigning hours (Original Estimate) to each task. After that is done the Team goes to work, usually two weeks but I can see us doing a three week sprint if the sprint just couldn't be nailed down to two weeks.
As we work we adjust the Hours Completed and Hours Remaining with no regard for the original estimate. If we have spent 3 hours so far and after 3 hours we think it is going to take 2 more that is what is on the task, it doesn't matter that the Original Estimate was 4 hours.
Because we have "filled in the boxes" and not adjusted the template all of the reports and the cube just work. We don't need to make any large adjustments to the reports or anything to capture some really nice metrics. If you want a template that is simpler you should take a look at the "Microsoft Visual Studio Scrum 1.0" from the Visual Studio Gallery. It is simpler for sure but offers less reports and less support in the way of integrated Office documents.
Mircosoft Visual Studio Scrum 1.0
我们最终使用了 TFS Agile 模板，但最终只是在工作项任务中使用了“工作时间”并将其称为故事点。
We ended up using the TFS Agile template, but just ending up using the "Effort Hours" in the work item tasks and refer to them as story points.