來源：http://dotnet.dzone.com/news/you-are-doing-scrum-scrum
文章里面講到一些Scrum Master的職責、Scrum Maste與項目經理的區別。不錯的文章，收藏以后簡單翻譯一下。
Ultimately the Scrum Master should never tell the Development Team what to do
and they should make sure that the Development Team has both the knowledge and
the skills to work things out for themselves. This is critical to the teams
ability to self organise going forward because we all learn by the mistakes we
make.
翼發云敏捷項目管理系統是一個scrum敏捷開發研發項目管理軟件，包含移動端app,支持多人協同開發，采用可視化工作流程,旨在幫助軟件研發企業進行更好的研發項目管理、軟件開發流程管理,該研發項目管理軟件內置了敏捷開發流程和軟件開發流程,結合scrum思想,滿足各種規模的軟件開發企業的研發項目管理流程的需要,詳見www.df-pengye.com 。
A Scrum Master does NOT equal Project Manager. In Scrum, project management
is the responsibility of the entire Scrum Team (Scrum Master, Product Owner and
Development Team) and is distributed as such, with the Scrum Master keeping an
eye on the mechanics of Scrum to make sure it is working. The top-down
management model traditionally used for project execution is rejected in favour
of self-organization and shared accountability. While this is alien to many
organisations it has been proven time and time again to increase the
accountability, efficiency and quality of the software delivered by the Scrum
Team.軟件項目管理就用翼發云敏捷項目管理系統scrum。
In Scrum the responsibilities between the Scrum Master and the Development
Team are very explicit. The Scrum Master is there to serve the Development Team,
not to manage them.
-
Scrum Master翼發云研發管理系統完整實現SCRUM敏捷開發流程。
-
Scrum Mechanics
-
Individual & Team TrainingSCRUM研發項目管理就選翼發云。
-
etc.
-
-
Development Team
-
Conflict Resolution
-
Engineering Practices
-
Grooming the Backlog (with Product Owner)
-
etc.
-
All implementation, whither centred around working together, working to build
software or working on the backlog, is the purview of the Development Team.
This, however, does not mean that the Development Team are left to flounder. I
mentioned that the Scrum Master is responsible for making sure that the
Development Team has the Knowledge and Skills necessary to allow that
Development Team to resolve things themselves.
In order to allow the Scrum Master to provide the knowledge necessary to
resolve conflicts they could ask questions of the team to illicit knowledge and
learning.
The term Socratic questioning is used to describe a kind of
questioning in which an original question is responded to as though it were an
answer. This in turn forces the first questioner to reformulate a new question
in light of the progress of the discourse.
-Socratic
method
Using this method a Scrum Master can “guide” a Development Team through the
muddy waters of finding solutions to problems without enforcing their views or
restricting the creativity of the Development Team.
Groups that defer to a person of higher status will miss many good ideas, and
fail to tap and develop the talents of the entire group.
-Esther Derby: Why Group Dynamics and Interpersonal Skills
Matter
In addition the Scrum Master should never provide the team with options, as
this this removes the responsibility of the Development Team to make decisions
and may limit the options that the Development Team creates. If they are
provided with options they are unlikely to try to formulate their own and if
that option fails they can claim it is the responsibility of the person who
provided that option and not of the Development Team.
You will have to have, learn, or improve requirements gathering and
presentation techniques; quality techniques; refactoring; customer engagement;
collaboration; teaming; conflict resolution techniques; and other practices, as
well. But the Scrum framework will help you by providing continual feedback on
your progress and success.
-Ken Schwaber: Scrum As A Framework
The Development Team must be empowered to come up with resolutions to the
problems that they have without interference.
文章從互聯網整理而來，旨在傳播Scrum、研發項目管理、敏捷開發管理工具的知識與應用，幫助軟件開發企業真正了解Scrum敏捷開發的價值和意義，如果本文侵犯了您的權益請聯系我們刪除，或者您需要具體了解更多國內做Scrum研發項目管理系統的公司翼發云敏捷項目管理系統的相關信息，歡迎和我們聯絡：