我们正在使用 JIRA 和 Agile Board，因此我们使用故事点来估计用户故事，而 JIRA 会注意烧毁。
但是，我们也有任务（不是在用户故事中，而是在单个任务中）和无法在故事点中估计的错误。在我们解决了这些问题之后，我们根据我们的故事点估计“完成的工作”，并将它们记录为票证（错误或任务）中的“评论”
是否有任何插件或工具可以仅为那些（错误和任务）构建一种燃尽图，以便我们跟踪。
在 sprint 结束时，我们不仅烧毁，而且还烧毁，有效的实际努力是这两者的总和。
问问题
472 次
1 回答
0
The simplest thing to do would be to create a search that returned the issue types you were interested in and then export the data to Excel. You could then generate the burn up chart that you want.
I should note that you are not using story points in the usual Scrum fashion. Bugs and tasks are not usually counted in the team's velocity. They represent an overhead which reduces the team's ability to deliver stories (which are where business value is added).
Remember that velocity is not a measure of work done. It is instead a metric used to help with estimating what the team's capacity for delivering business value is in future sprints.
于 2015-02-16T20:14:03.103 回答