Scrum Guide 精读 - 5. Scrum team - Dev

Scrum guide 精读，今天接着讲到Scrum团队。

在介绍Scrum team的三个角色之前，指南里花了很长篇幅做铺垫。

第一段：

“The fundamental unit of Scrum is a small team of people, a Scrum Team. The Scrum Team consists of one Scrum Master, one Product Owner, and Developers. Within a Scrum Team, there are no sub-teams or hierarchies. It is a cohesive unit of professionals focused on one objective at a time, the Product Goal.”

点评：小团队，三个角色，没有层级和下属团队，每次只专注一个目标。

small这个词出现了多次，这整段话里反复透露 着一个意思，“简单”。简单的团队，简单的组织，简单的目标。每次只定一个目标，也就是当下的Product Goal。

第二段：

Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value each Sprint. They are also self-managing, meaning they internally decide who does what, when, and how.

点评：这里重点我认为是解释了self-managing：they internally decide who does what, when, and how. 当然这得是在目标的指导下，如果是外部指导谁来做，做什么，怎么做的话，那么这样的Scrum team充其量只是一个工具化的开发团队而已。

第三段：

The Scrum Team is small enough to remain nimble and large enough to complete significant work within a Sprint, typically 10 or fewer people. In general, we have found that smaller teams communicate better and are more productive. If Scrum Teams become too large, they should consider reorganizing into multiple cohesive Scrum Teams, each focused on the same product. Therefore, they should share the same Product Goal, Product Backlog, and Product Owner.

点评：这段讨论的是团队的大小，这里说的是10人以下，有一个时髦的说法是2 pizza size，对于披萨没概念的话，那么就是8、9个人以内就对了。也经常有人说6、7个人是最合适的团队大小。无论如何，维持团队人数在个位数是一个大家认同的观点。

    我的观点是，团队不一样，性质不一样，固定一个人数也不科学。判断团队沟通和管理的成本，是否大于人数上带来的劳动密集优势，我个人总结的一个接地气的做法是，如果有一两个人请假，大家伙感觉很慌，那么就说明人数不够。如果有一两个人请假，没有太大影响，更轻松了，效率更高了，那么就说明人多了。相信真正带过团队的leader应该会很有体会。