編按：

我們要看的，不是這個問題的具體解答，而是其中的思考。

對Scrum的逐層升高的思考，參閱：

你曾經試圖在Scrum中增加一箇中期Review嗎？

你並不孤獨，我經常遇到團隊這樣做。

這樣做有很多理由：

• 讓團隊成員同步工作

• 評估迭代目標是否能達到

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

• 請求PO的反饋

但，團隊應當這樣做嗎？

可能不應當。與其這樣做，不如把這些理由當作迭代時間太長的警告。

例如，如果團隊需要每日站會之外的額外同步（譯者注：同步更多是專案管理活動，不包含技術討論），那麼這個迭代可能太長了，導致團隊成員耦合度不夠。

而如果團隊例行增加或縮小範圍，那麼團隊應當加強在短迭代中完成工作的預測能力。

而如果團隊需要更多的反饋，那麼更需要更短的迭代，或者當特性完成時，進行增量式Review。

當然，在迭代中期，團隊會自然而然地思考能否完成迭代目標。

但那隻需要在每日站會上花多一兩分鐘。不需要另一個正式的會議。

所以如果你試圖增加一個迭代中期Review，不如考慮縮短迭代週期。

更短的迭代，而不是正式的中期Review，會幫助你成功實施敏捷。

延伸閱讀：

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.