这也远非理想，但使用 Excel 简化了冲刺计划。每个团队都创建了自己的查询来查看他们的工作，并且他们在每个冲刺中更改查询。缺点是内置报告不起作用。我阅读了最新的《使用 Visual Studio 进行敏捷软件工程》一书，但它没有提供任何有关如何做得更好的见解。
We were advised to use the Iteration Path to identify teams. We're using the Agile 5.0 template, but I don't think that matters. We have 8 teams, so we have the iterations set up like this:
This is also far from ideal, but using Excel simplifies sprint planning. Each team created their own queries to see their work, and they change the query each sprint. The downside is that none of the built-in reporting works. I read the latest Agile Software Engineering with Visual Studio book, but it did not provide any insight into how this could be done better.
We tried to do the same thing and ended up just using TFS as if it was one team and one sprint since that was the easiest way for all the reports to work and upper management to see the big picture easily. We created sub reports based on the teams to help drill down.
I'm sure there is a better way in TFS, maybe creating your own field in the template for a team number and modifying the reports. We were not allowed to change anything in the templates.
发布评论
评论（2）
建议我们使用迭代路径来识别团队。我们正在使用敏捷 5.0 模板，但我认为这并不重要。我们有 8 个团队，因此我们的迭代设置如下：
这也远非理想，但使用 Excel 简化了冲刺计划。每个团队都创建了自己的查询来查看他们的工作，并且他们在每个冲刺中更改查询。缺点是内置报告不起作用。我阅读了最新的《使用 Visual Studio 进行敏捷软件工程》一书，但它没有提供任何有关如何做得更好的见解。
We were advised to use the Iteration Path to identify teams. We're using the Agile 5.0 template, but I don't think that matters. We have 8 teams, so we have the iterations set up like this:
This is also far from ideal, but using Excel simplifies sprint planning. Each team created their own queries to see their work, and they change the query each sprint. The downside is that none of the built-in reporting works. I read the latest Agile Software Engineering with Visual Studio book, but it did not provide any insight into how this could be done better.
我们尝试做同样的事情，最终只是使用 TFS，就好像它是一个团队和一个冲刺一样，因为这是所有报告工作和高层管理人员轻松查看全局的最简单方法。我们根据团队创建了子报告以帮助深入分析。
我确信 TFS 中有更好的方法，也许可以在模板中为团队编号创建自己的字段并修改报告。我们不允许更改模板中的任何内容。
We tried to do the same thing and ended up just using TFS as if it was one team and one sprint since that was the easiest way for all the reports to work and upper management to see the big picture easily. We created sub reports based on the teams to help drill down.
I'm sure there is a better way in TFS, maybe creating your own field in the template for a team number and modifying the reports. We were not allowed to change anything in the templates.