关于能否命令Scrum团队的对话

Dennis van der Stelt在Yahoo的scrumdevelopment组（http://groups.yahoo.com/group/scrumdevelopment/）发起了题为“Commitment to Definition of Done”的讨论。背景是Dennis van der Stelt发现他身边的团队没有达成对完工定义的承诺，为解决这个问题，讨论区给他出了不少主意。

有人提出“不能强迫（英文原文是MAKE）团队做任何事，把问题暴露到业务，提供未来发展的预测”，引发了不同的看法，见如下的对话。

Dan Rawsthorne：

You can't MAKE the Team do anything. However, you have an obligation to the Business to make this problem visible, along with predictions of what will happen. That's what scrum does: expose problems to the business. You are obligated to do so as the ScrumMaster..

Joe:

People are free. And in Scrum, we respect their freedom.
Also, we find, wherever we need teamwork to get something done, that if the team
is to be truly successful, it must self-organize, for example, as a complex
adaptive system (wikipedia that).
In most 'real life' that I see, you can never make anyone do anything. In fact,
in trying to make them, you usually assure that they will resist doing it.

Little's Second Law: People are remarkably good at doing what they want to do.

BUT: As Dan said, one has the obligation as SM to show reality. And it is
remarkable how powerful the truth is. Good people cannot resist it. And they do
not take it as a violation of their freedom.

So, polish your mirror, learn to be more articulate. Speak the truth. And they
will act.

Zhangk:

Yes, People are free, they have their freedom. and the society still has laws.
SEAL in USA army is a very successful team, It takes the command@control mode. there are defined rules for SEAL member which tell the right practices derived from blood and sweat.
Software develop team isn't same as the army team.
fully command@control is pole, fully freedom is another pole.
For different team or organization, A suitable point could be got between the two poles, this's what the managers or coaches or EPG leaders or should do.
So if the right practices are got, these practices can be deployed to the team by the management methods even in a agile environment.

waiting for failure is not positive, Although the failure can convince the team more easily. if the failure is small and quick, it's OK for waiting. but if the failure is too big ,the positive direction should be taken early even the team maybe not understand.

Tara Santmire:

If you think SEALs are at the full command and control end of the spectrum, I think that you don’t know much about SEAL teams. SEALs have best practices and rules much like software development teams have good engineering practices and rules about how work will be done. Within that framework SEALs have latitude just as developers do to do their work as they see fit and meet the objectives. IMHO, they are self managing teams in many of the same ways that Scrum teams are.

Zhangk:

Thank Tara. I never think SEALs are at the full command and control mode. I also know and agree that "SEALs have best practices and rules much like software development teams have good engineering practices and rules about how work will be done."

In most instances, if the member of SEAL violates the best practices and rules of SEAL, what will be happened? I think a immediate correction will be taken if the leader finds it.

Adam Sroka:

SEALs also don't work for the Army. As someone who was born in a Navy hospital and spent his entire childhood on military bases (My dad retired as an O-6 in 2003) that one made me cringe a little.

The way I would put it is this:

SEALs and other special operations forces are strategic resources that, depending on the mission type, may operate for some time beyond the direct control of their superiors. There is actually a strong parallel to Scrum here. The team is given a mission and a set of guidelines for accomplishing that mission. They go off and get it done, and report back at appropriate times. When the team encounters an "impediment" (Such as: a need for additional resources, a need to modify the rules of engagement, time-critical intelligence, etc.) then the team contacts it's leadership for guidance (Though, depending on circumstances, they may have to wait hours or days to get the answers they need. And, they need to be able to continue to perform critical "tasks" in the meantime.)

Dave Rooney:

Navy SEALs, other special forces teams and even standard infantry are trained in the use of Boyd's OODA (Observe-Orient-Decide-Act) loop, which is a much more refined version of Inspect and Adapt. That loop allows individuals, teams and even battle groups to make the decisions required based on the actual information rather than the plans.

There have been observations that the agility of these teams has been hampered recently due to the technology that allows commanders to watch an action unfold, and make decisions and direct troops from places other than the immediate battlefield. THAT is command & control, and it is considered a bad thing even in the military.

Zhangk:

To say "It takes the command@control mode" maybe too simple, or wrong. but SEAL's team must accept and execute the commanders from the up-grade. and at the immediate battlefield, the captain or team leader must direct the team by the orders. An recent example: Message details decisions made by President Obama in directing the rescue of Captain Phillips from Somali pirates. http://www.snopes.com/politics/obama/pirates.asp

So on the whole，to say "SEAL takes the command@control mode" is not very wrong.

what I disagree with is "You can't MAKE the Team do anything".

Even a self-organized scrum team should accept the orders from product owner and the up-grade. The management can make the team do something. and the management can't make the team do everything.

"polish your mirror, learn to be more articulate. Speak the truth. And they will act." it is somewhat negative and time-consuming.

For SEAL, when facing the kidnappers and hostages, if the leader find a mistake or wrong action from a team member ,he must command the member correct at once.

关于能否命令Scrum团队的对话相关推荐

Scrum团队选择scrum看板工具的7点特征
首先: 什么是Scrum? Scrum 是一个用于开发和维护复杂产品的框架 ,是一个增量的.迭代的开发过程. 在这个框架中,整个开发过程由若干个短的迭代周期组成,一个短的迭代周期称为一个Sprint, ...
Scrum团队初建的十一件事——Scrum中文网
本文转自:Scrum中文网原文链接:http://www.scrumcn.com/agile/scrum/22585.html 越来越多的公司(IT/非IT)正在做或者计划做Scrum转型.很多的团 ...
0429 Scrum团队成立与第6-7章读后感
Scrum团队成立: 团队名称:何首污大战污妖王团队目标:每个人都尽可能的学到东西,共同进步. 团队口号:因为自信,所以成功! 团队照: 角色分配产品负责人(梁毅乾): 决定开发内容和优先级排序, ...
0502团队项目 SCRUM团队成立
Scrum团队成立团队名称:对不对?队团队目标:短期目标,完成O2O模式的第一个平台团队口号:我们都不是神的孩子团队照: 角色分配产品负责人: 许佳仪.决定开发内容和优先级排序,最大化产品以 ...
[团队项目3.0]Scrum团队成立
Scrum团队成立 5.Scrum团队成立 5.1 团队名称,团队目标.团队口号.团队照: 5.2 角色分配产品负责人: 决定开发内容和优先级排序,最大化产品以及开发团队工作的价值. Scrum M ...
Scrum团队: I-型人 vs T- 型人
有些人在一个领域有很深的专门性,但很少在该领域之外做出贡献.在敏捷社区中,这些人被称为"i-型人",因为他们像字母"i"一样,有深度,但宽度不大.相比之下,&q ...
什么是Scrum团队？
什么是Scrum团队? Scrum团队是一组个人(通常在五到九名成员之间)一起工作,以提供所需的产品增量.Scrum框架鼓励团队成员之间进行高水平的沟通,以便团队可以: 遵循共同的目标遵守相同的规范 ...
Scrum团队成立3.0
博客园首页新随笔联系订阅管理随笔 - 23 文章 - 0 评论 - 26 0428-Scrum团队成立3.0 ------------------------------3.0---- ...
.Scrum团队成立
团队名称:十三幺团队口号:我爱麻将,但更爱编程! 团队目标:改变自己,也让周围因有我们存在而有一点点不同团队照:团队照.............. 角色分配: 张国镜:PM项目经理陈彦生:Scr ...

关于能否命令Scrum团队的对话

关于能否命令Scrum团队的对话相关推荐

最新文章

热门文章