报告完成的冲刺 [英] Reporting on completed sprint

问题描述

想要构建一份报告，显示每个团队成员在每个完成的 Sprint 中的贡献百分比.我们分解任务中的工作并分配一个剩余工作值来指示所需的时间.那么问题是剩余价值随着冲刺的进行而清晰或减少.

Want to build a report showing each team member's percentage contribution per a completed Sprint. We break up the work in Tasks and assign a Remaining Work value to indicate the time needed. The problem then is that remaining value is clear or decreased as the sprint progresses.

一直在寻找找到原始剩余价值的方法，因此我可以将其用于 sprint 后的报告.所有这些都是为了尝试在最初设定的工作时间和实际工作时间之间建立关系.

Have been looking for a way to find the original remaining value, so I can use it for reporting post the sprint. All in an effort to try and build a relation between originally set Effort and Actual hours.

如有任何帮助，我们将不胜感激.

Any assistance would be appreciated.

推荐答案

首先我要说的是，作为 Scrum.org 的专业 Scrum 培训师，我们强烈反对将工作分解给单个团队成员作为标准的一部分报告.就 Scrum 而言，个人贡献在团队环境之外几乎没有影响，而在团队内部，我们认为团队成员应该能够公开讨论其他团队成员的感知价值，作为他们 Sprint 回顾的一部分.

First I have to say this, as a Professional Scrum Trainer with Scrum.org, we highly discourage the breakdown of effort to the individual team member as part of standard reporting. Where scrum is concerned, the individual contribution is of little consequence outside of the team context, and inside of the team we feel that team members should be able to openly discuss the perceived value added by other team members as part of their Sprint Retrospective.

其次，由于 TFS 无法注册分配给任务的多个用户，也不支持跟踪多个团队成员在同一任务上花费的时间，因此您的报告充其量是不完整的，在大多数情况下会导致额外的管理开销甚至可能导致团队成员在最坏的情况下无法协同工作.

Secondly, because TFS can't register multiple users being assigned to a task, nor support the trackign of hours spent by multiple team members on the same task, your report will either be incomplete at best, cause additional administration overhead in most cases and may even cause team members to not work together at worst.

说...

TFS 跟踪工作项字段的所有分配和保存的值.使用 API 可以轻松地遍历工作项并检索它们以前的修订版本.作为替代方案，API 提供了 asof 工作项查询，允许您跟踪特定日期工作项的值.此信息也存储在 TFS 数据仓库中(如果您正在使用它)，在每日级别汇总.

TFS tracks all assigned and saved values for work item fields. Using the API it's easy to iterate through the work items and retrieve their previous Revisions. As an alternative, the API offers asof work item queries which allow you to track what the values of a workitem were on a specific date. This information is also store in the TFS datawarehouse, if you are using it, aggregated at the daily level.

但如果您需要准确跟踪花费的时间，唯一可靠的方法是将已完成的工作字段添加到您的工作项类型定义中:

But if you need accurate tracking of time spent, the only reliable way is to add the Completed Work field to your work item type definition:

完成的工作

执行任务所花费的工作量.您可以以小时或天为单位指定工作.没有与此字段关联的固有时间单位.

The amount of work that has been spent implementing a task. You can specify work in hours or in days. There are no inherent time units associated with this field.

参考名称=Microsoft.VSTS.Scheduling.CompletedWork，数据类型=Double

Reference name=Microsoft.VSTS.Scheduling.CompletedWork, Data type=Double

任务，错误

这是必需的，以涵盖原始估计低于实际花费的时间，在这种情况下剩余工作将保持不变甚至增加，而团队成员已在该项目上花费时间的情况.如果不跟踪 CompletedWork，这些数据就会丢失.

This is required to cover cases where the original estimate was lower than the actual time spent, remaining work would in that case remain the same, or even increase, while a team member had spent time on that item. without also tracking CompletedWork, this data is lost.

Agile 和 CMMI 模板默认使用此字段.Scrum 模板没有，根据我最初的警告，你可以猜到原因.

The Agile and CMMI template use this field by default. The Scrum template doesn't, you can guess why based on my initial cautions.

这篇关于报告完成的冲刺的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！