Mike Cohn：如何保证团队为产品列表梳理预留时间

大多数敏捷团队知道产品列表梳理的重要性，但很多团队不能做到在每个迭代为此预留时间。

确保团队有时间梳理产品列表的最佳方法是在迭代开始时计划出这部分时间。

在迭代计划会上，ScrumMaster或PO可能会说，“在本迭代中，我想我们可能需要两次产品列表梳理会，可能每次60到90分钟。因此在你们计划本迭代要做多少工作时，要记着这一点。”

如果你们做的是基于容量的迭代计划会，每个团队成员从可用时间中为产品列表梳理预留几个小时就好。

反过来，如果你们做的是基于速率的迭代计划会，你们需要猜测在下个迭代中少做多少个故事点。但是，在连续几个包含产品列表梳理的迭代之后，速率又会重新稳定。

产品列表梳理会议通常不长，速率的下降通常是微不足道的，甚至可以忽略。当然，那取决于你的速率是5还是500，比方说。

 

凡事不预则不立。在计划会上为产品列表梳理计划出时间，并根据需要降低容量或速率，确保梳理会议发生，这将会使你的团队成功敏捷。（如果不想用下班开会应对带薪拉屎的话）

 

 

How to make sure the team leaves time for backlogrefinement

 

Most agile teams acknowledge the importance of product backlog refinement but many struggle to make time for it each iteration.

The best way to ensure your team has time to product backlogrefinement is to schedule it at the start of the sprint.

During a sprint planning meeting, the Scrum Master or productowner might say, “I think we're going to need perhaps two backlog refinementsessions, probably sixty to ninety minutes each during this sprint. So let’skeep that in mind as you figure out how much work to bring into the currentsprint."

If you're doing capacity-driven sprintplanning, team memberswould each just reduce their personal availability by a couple of hours toaccommodate this.

If, instead, you're doing velocity-driven sprintplanning, you'll need toguess at how many points fewer to bring into the next sprint. But, after just afew sprints incorporating backlog refinement meetings, velocity will stabilizeagain.

The drop in velocity will usually be negligible (if it existsat all) for something as small as product backlog refinement meetings. That, ofcourse, depends on whether your velocity is 5 or 500.

When things aren't scheduled, they often don't happen.Scheduling product backlog refinement meetings during sprint planning, andreducing capacity or velocity as needed, ensures the meetings take place,enabling your team to succeed with agile,

Mike

真北敏捷社群，求道、连接，汇通天下有识之士、友士之识。