The Scrum methodology of agile software development marks a dramatic departure from waterfall management. In fact, Scrum and other agile processes were inspired by its shortcomings. The Scrum methodology emphasizes communication and collaboration, functioning software, and the flexibility to adapt to emerging business realities — all attributes that suffer in the rigidly ordered waterfall paradigm.
Posted by admin under Scrum Basics
There are three fundamental roles in the Scrum method of agile software development: the Product Owner, the ScrumMaster, and the team. The second role I’d like to examine is the ScrumMaster, who, serves as a facilitator for both the Product Owner and the team. He or she has no management authority within the team and may never commit to work on behalf of the team.
In Scrum, the ScrumMaster demands a distinct personality type to succeed. The best ScrumMasters are real team players, who receive as much satisfaction from facilitating others’ success as their own. They must also be comfortable surrendering control to the Product Owner and team. For those two reasons, traditional project managers don’t usually make great ScrumMasters.
So, specifically, what does a ScrumMaster do? The ScrumMaster remove any impediments that obstruct a team’s pursuit of its sprint goals. In other words, the ScrumMaster does everything he or she can to facilitate productivity. When a developer’s computer dies, it’s the ScrumMaster’s job to ensure it is back up and running—or get another one. If developers are complaining about the high temperature in the team room, the ScrumMaster must find a way to cool it down. It might be easy to summarize a ScrumMaster’s work in a sentence or two, but scenarios he or she could face are truly infinite.
The second role for the ScrumMaster is to own the success of the teams process. This might means helping helping the Product Owner maximize productivity or helping the team turn the sprint retrospective meeting into an evolutionary / Kaizen experience. Facilitating for the team or Product Owner might also include tasks like helping maintain the backlog and release plan or radiating Scrum artifacts to ensure the Product Owner or The Team is informed about progress.
To understand the full scope of the Scrum Master role, see the newly updated ScrumMaster checklist for 2013.
posted by: scrum methodology
Leave a Reply
Scrum Training CoursesMarch 19 - 20, 2014
Michael James, CST
April 10 - 11, 2014
Petri Heiramo, CST
April 28 - 29, 2014
Gregory Smith, CST
Scrum Training Series
- Do you REALLY want to learn Scrum? Try a 3.1-day CSM class with case studies. July 25, 2013
- Scrum based funding model – 20 percent May 9, 2013
- MJは６月と７月の２ヶ月間、日本に滞在する予定です。スクラムのコーチングまたはトレーニングに興味のある方は是非ご連絡ください。 March 14, 2013
- The Next Big Idea March 5, 2013
- On Being Available February 17, 2013