Actually, I prefer this tool. It does task-tracking, burndowns, burn-ups, and is useful for project notes.
But to answer the question, tracking hours-remaining on a burndown should still work. It'll still tell you whether you're going to get all your release-sprint tasks (bugs/tweaks) done in time for launch. If the answer is "not all of them", then it's time to get the product owner in to do some prioritisation, and kick some of the tasks out of the sprint.
Your goal should be to get to a point where you don't need a release sprint to deploy to production:) But with that said, what are you doing in your release sprint? There are still tasks to be done, but they are even more predictable than developing code. I've never seen a difference in how the burndown/planning works other than it usually involves adding people to the team from ops. That of course can be its own problem. Maybe you could give a quick idea of what a release sprint looks like in your organization.
We're using a kanban board with scrum. Each product item is represented by a post-it note on the whiteboard. Its really obvious during the daily standups where everyone is with each of their tasks, and we can see how many tickets we have queued up in the 'pending' area on the board compared to the 'done' area at the other end.
发布评论
评论（3）
实际上，我更喜欢这个工具。 它可以进行任务跟踪、燃尽、燃尽，对于项目笔记很有用。
但要回答这个问题，跟踪燃尽剩余时间应该仍然有效。 它仍然会告诉您是否要在发布前及时完成所有发布冲刺任务（错误/调整）。 如果答案是“不是全部”，那么是时候让产品负责人进行一些优先级排序，并将一些任务从冲刺中剔除。
Actually, I prefer this tool. It does task-tracking, burndowns, burn-ups, and is useful for project notes.
But to answer the question, tracking hours-remaining on a burndown should still work. It'll still tell you whether you're going to get all your release-sprint tasks (bugs/tweaks) done in time for launch. If the answer is "not all of them", then it's time to get the product owner in to do some prioritisation, and kick some of the tasks out of the sprint.
您的目标应该是达到不需要发布冲刺即可部署到生产的程度:)但是话虽如此，您在发布冲刺中做了什么？ 仍然有任务需要完成，但它们比开发代码更可预测。 我从未见过燃尽/计划的工作方式有什么不同，除了通常涉及从运营人员向团队添加人员之外。 这当然可能是它自己的问题。 也许您可以快速了解组织中的发布冲刺是什么样的。
Your goal should be to get to a point where you don't need a release sprint to deploy to production:) But with that said, what are you doing in your release sprint? There are still tasks to be done, but they are even more predictable than developing code. I've never seen a difference in how the burndown/planning works other than it usually involves adding people to the team from ops. That of course can be its own problem. Maybe you could give a quick idea of what a release sprint looks like in your organization.
我们使用带有 scrum 的看板板。 每个产品项目都由白板上的便利贴表示。 在每天的站立会议中，每个人都在完成自己的任务，这一点非常明显，我们可以看到与另一端的“已完成”区域相比，我们在看板上的“待处理”区域中排队的票数有多少。
We're using a kanban board with scrum. Each product item is represented by a post-it note on the whiteboard. Its really obvious during the daily standups where everyone is with each of their tasks, and we can see how many tickets we have queued up in the 'pending' area on the board compared to the 'done' area at the other end.