I've seen groups use a whiteboard, and use different colors for each group of tasks.
If you use note cards for your stories, you can put them up there as well, and divide them by release/iteration/group of tasks. This concept is explained better here.
Not for everyone, but for those running TFS, Scrum For Team System provides excellent sprint backlog reports.
Failing that, Ive personally maintained sprint backlogs using a spreadsheet, as per this article. Sharing via something along the lines of google docs.
Somewhere on the web there is a blog post which is just a lot of scrum boards. It is really good to see how other people do it. Maybe someone can find it for us :)
I think this looks like a pretty comprehensive way of doing things!
Depending on your needs, there is a free community edition. It's very easy to track stories and tasks within a given sprint, including estimations, actuals, and states for each story and task.
I usually use an Excel sheet, on a shared network folder: one column is used to specify the "group" of the task, and one to specify the task itself. For completed tasks, we simply mark the row in green. The primary disadvantage for that is sharing - I've yet to find a decent solution that allows more than one person to edit the backlog. We have some ways to deal with it (by limiting the updates to a specific time of day, and then having the team update it together), but it is still annoying.
For sprints with a small number of tasks, we simply write the tasks on a whiteboard, and strike over the tasks as they are completed.
发布评论
评论（5）
我见过小组使用白板，并为每组任务使用不同的颜色。
如果您在故事中使用记事卡，您也可以将它们放在那里，并按发布/迭代/任务组划分它们。 这个概念在这里得到了更好的解释。
更新：我还使用电子表格来可视化我的冲刺/迭代，因为我的团队并不都在同一地点。 我使用与吉姆的回答中提到的类似的表格和图表。
I've seen groups use a whiteboard, and use different colors for each group of tasks.
If you use note cards for your stories, you can put them up there as well, and divide them by release/iteration/group of tasks. This concept is explained better here.
Update: I also use spreadsheets to visualize my sprints/iterations, because my team is not all co-located. I use tables and graphs similar to what was mentioned in Jim's answer.
不适合所有人，但对于那些运行 TFS 的人来说，Scrum For Team System 提供了出色的冲刺积压报告。
如果做不到这一点，我亲自使用电子表格维护冲刺待办事项，按照这篇文章。谷歌文档行。
Not for everyone, but for those running TFS, Scrum For Team System provides excellent sprint backlog reports.
Failing that, Ive personally maintained sprint backlogs using a spreadsheet, as per this article. Sharing via something along the lines of google docs.
网络上的某个地方有一篇博客文章，里面有很多 Scrum 板。 看到其他人是如何做到的真的很好。 也许有人可以为我们找到它:)
我认为这看起来是一种非常全面的做事方式！
http://www.xpday.net/Xpday2007/session/AgileInGovernment.html
Somewhere on the web there is a blog post which is just a lot of scrum boards. It is really good to see how other people do it. Maybe someone can find it for us :)
I think this looks like a pretty comprehensive way of doing things!
http://www.xpday.net/Xpday2007/session/AgileInGovernment.html
查看 Rally 工具，网址为 rallydev.com。
根据您的需求，有一个免费的社区版本。 在给定的冲刺中跟踪故事和任务非常容易，包括每个故事和任务的估计、实际情况和状态。
Check out the Rally tool at rallydev.com.
Depending on your needs, there is a free community edition. It's very easy to track stories and tasks within a given sprint, including estimations, actuals, and states for each story and task.
我通常在共享网络文件夹上使用 Excel 工作表：一列用于指定任务的“组”，一列用于指定任务本身。 对于已完成的任务，我们只需将行标记为绿色即可。 这样做的主要缺点是共享 - 我还没有找到一种合适的解决方案，允许多个人编辑待办事项列表。 我们有一些方法来处理它（通过将更新限制在一天中的特定时间，然后让团队一起更新），但这仍然很烦人。
对于任务数量较少的冲刺，我们只需将任务写在白板上，并在任务完成后将其划掉。
I usually use an Excel sheet, on a shared network folder: one column is used to specify the "group" of the task, and one to specify the task itself. For completed tasks, we simply mark the row in green. The primary disadvantage for that is sharing - I've yet to find a decent solution that allows more than one person to edit the backlog. We have some ways to deal with it (by limiting the updates to a specific time of day, and then having the team update it together), but it is still annoying.
For sprints with a small number of tasks, we simply write the tasks on a whiteboard, and strike over the tasks as they are completed.