Sprint 待辦清單 (#8 – Manager vs. Sprint Backlog)

Comic Agilé 漫畫原創作者的話

The Scrum guide states that “the Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal”. We also see that it contains bugs, actions to mitigate risks and activities for improving the way the Scrum team works based on the previous Retrospective.

In the manager’s order above, we see several anti-patterns; using organizational hierarchy to tell a team to include an item in the Sprint Backlog, the content of the item (likely) not contributing to neither the team’s Sprint Goal nor Retrospective outcomes, and the motivation for the request being measuring and reporting on the “efficiency” of the team. At least, the manager got the voice of a User Story right…

---

Scrum 指南說「Sprint 待辦清單 (Sprint Backlog) 是為這個 Sprint 選擇的產品待辦清單項目 (Product Backlog items) 的集合，以及交付產品增量 (Increment) 和實現 Sprint 目標 (Sprint Goal) 的計劃”。 我們認為（這句話中）還包括了除錯、降低風險的措施、與基於之前的回顧會議 (Sprint Retrospectives) 改進 Scrum 團隊工作方式的活動項目。

在上面的經理的指示中，我們看到了幾個反面模式 (anti-pattern)； 使用組織階級制度要團隊在 Sprint 待辦清單 (Sprint Backlog) 加入工作項目、這個工作項目的內容（可能）與團隊的 Sprint 目標 (Sprint Goal) 和回顧會議改善事項無關、以及這個需求的動機是量測與報告團隊的「效率」。至少，這經理用對了使用者故事的句子格式⋯⋯