真北译文 | 应不应该做Sprint中期Review？

编按：

我们要看的，不是这个问题的具体解答，而是其中的思考。

对Scrum的逐层升高的思考，参阅：

• 真北敏捷 | 策略思维，超越原生感受

• Scrum原理：更亲密，更严密

• 真北敏捷 | 明治维新与敏捷：思想、制度和器物

• 暗宇宙

---

你曾经试图在Scrum中增加一个中期Review吗？

你并不孤独，我经常遇到团队这样做。

这样做有很多理由：

• 让团队成员同步工作

• 评估迭代目标是否能达到

• 决定在迭代中增加或移除PBI（product backlog item）

• 请求PO的反馈

但，团队应当这样做吗？

可能不应当。与其这样做，不如把这些理由当作迭代时间太长的警告。

例如，如果团队需要每日站会之外的额外同步（译者注：同步更多是项目管理活动，不包含技术讨论），那么这个迭代可能太长了，导致团队成员耦合度不够。

 

而如果团队例行增加或缩小范围，那么团队应当加强在短迭代中完成工作的预测能力。

 

而如果团队需要更多的反馈，那么更需要更短的迭代，或者当特性完成时，进行增量式Review。

当然，在迭代中期，团队会自然而然地思考能否完成迭代目标。

但那只需要在每日站会上花多一两分钟。不需要另一个正式的会议。

所以如果你试图增加一个迭代中期Review，不如考虑缩短迭代周期。

更短的迭代，而不是正式的中期Review，会帮助你成功实施敏捷。

 

延伸阅读：

• 真北敏捷 | 从Vision到Value，Backlog精化带你飞

• Scrum模式：双轨双耳双管理双环学习模型

• 真北敏捷 | Scrum游戏：纸上原型
  

---

If you're tempted to add a mid-sprint review, do this instead

Have you ever been tempted to add a mid-sprint review for your Scrum teams?

If so, you’re not alone. I frequently meet teams who have done this.

Teams will add a mid-sprint review for any number of many well-intentioned reasons. These include that a mid-sprint review is a good time:

• for team members to synchronize their work

• to assess whether the sprint goal will be achieved

• to decide to add or remove product backlog items from the sprint

• to solicit feedback from the product owner.

So, with all these good reasons to add a mid-sprint review, does that mean teams should do it?

Probably not. Rather than think of these as good reasons for a mid-sprint review, think of them instead as warning signs that the sprint length is too long.

For example, if team members need additional synchronization beyond what they get from daily scrum meetings, the sprint is likely too long and causing team members to drift apart from one another.

Or if a team is routinely adding or removing scope, team members should focus on developing the skills needed to better estimate the amount of work they can accomplish within the short boundary of a sprint.

And if team members would benefit from more frequent feedback, they should definitely consider shorter sprints or perhaps incremental reviews as each feature is developed.

Sure, the middle of a sprint provides a natural time for a team to think about things such as will they will finish their planned work.

But that should only take an extra minute or two during that day’s scrum meeting. It’s not an entirely separate, formal meeting.

So if you’re tempted to make a mid-sprint review a formal, additional meeting, you should instead consider going to shorter sprints.

Shorter sprints, rather than a formal, mid-sprint review, will help you succeed with agile.

译者：

求道致用，做最好的敏捷知识库：