如何取消对 PBI 的承诺 [英] How to UnCommit to a PBI

查看:33
本文介绍了如何取消对 PBI 的承诺的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个已提交的 PBI.与之相关联,我有 6 个任务.两个已经完成,四个还没有开始.

I have a PBI that is Committed. Linked to it, I have 6 Tasks. Two are finished and Four are not even started.

事实证明,我们不会完成这项工作,但可能会在稍后的 sprint 中进行.我们不会将其移至下一个 Sprint.

It turns out that we won't be finishing this, but might pick it up in a later sprint. We will not be moving it to the next Sprint.

如果我将 PBI 移到待办事项列表中,那么这些任务在我当前的 Sprint 中就会成为孤立的.

If I move the PBI into the Backlog, the tasks are orphaned in my current Sprint.

如果我将任务移到 Backlog 中,我真的不知道它们去了哪里……但真正的问题是,每当我们再次拿起那个 PBI 时,我们都必须以某种方式记住它是一个未提交的 PBI,并且必须检查链接,然后用它拉出链接的任务.

If I move the Tasks into the Backlog, I really have no clue where they go... but the true issue is that whenever we pick up that PBI again, we'll have to somehow remember that it was an UnCommitted PBI, and will have to check the Links then pull the Linked Tasks with it.

有没有更好的办法?我想将完成的任务保留在他们完成的 Sprint 中,并在 PBI 去的任何地方拉取待办任务.

Is there a better way? I'd like to keep the Done tasks in the Sprint they were Done in, and pull the ToDo Tasks anywhere the PBI goes.

推荐答案

在 Scrum 中,一个产品待办事项已完成或未完成.这是一个二元状态.如果没有完成,将其移回产品待办列表,重新估算并让产品所有者重新订购.这些任务是被丢弃的候选对象.原因如下:

In Scrum, a product backlog item is done, or not done. It's a binary state. If it's not done, move it back to the product backlog, re-estimate it and let the product owner re-order it. The tasks are candidates for being discarded. Here's why:

您返回到产品待办列表的产品待办列表项可能不会在下一个 sprint 中处理,可能不会在多个 sprint 中处理,或者可能根本不会处理.所有这些操作都可能影响任务的内容.

The product backlog item that you return to the product backlog may not be worked on in the next sprint, may not be worked on for several sprints or may never be worked on at all. All these actions are likely to affect the content of the tasks.

例如,团队组成可能会发生变化,因此交付产品待办事项列表项的功能的方式可能会发生变化.当然,对任务的估计会发生变化.

For example, team composition may change and so the way of delivering the functionality for the product backlog item may change. Certainly, the estimates for the tasks would change.

放弃任务时,请考虑删除您描述为已完成的任务的代码.您希望保持代码库精简且易于维护.

When discarding the tasks, consider removing the code for the tasks that you describe as being finished. You want to keep your code base lean and easily maintainable.

最后,当您谈到孤立任务时,我的印象是您正在使用软件工具来管理您的产品待办事项.是这种情况吗?如果是这样,我鼓励您首先将该问题视为 Scrum 问题.这可能会突出您的软件工具的问题,您可以将其作为单独的问题解决.换句话说,不要让软件工具推动您采用 Scrum.

Finally, when you talk about orphaned tasks, I'm gaining the impression that you're using a software tool to manage your product backlog. Is this the case? If so, I'd encourage you to consider the problem as a Scrum issue first and foremost. This may then highlight issues with your software tool which you can address as a separate issue. In other words, don't let the software tool drive your adoption of Scrum.

这篇关于如何取消对 PBI 的承诺的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆