Scrum Methodology
Learn the Scrum Methodology
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.
30th
SEP
The ScrumMaster Role
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 and may never commit to work on behalf of the team.
In Scrum, the ScrumMaster is an arduous role and 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? First and foremost, 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 get it 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.
But a ScrumMaster’s work doesn’t solely address the needs of the team; he or she is also responsible for helping the Product Owner maximize productivity. Facilitating productivity for the Product Owner might include helping maintain the backlog and release plan or radiating Scrum artifacts to ensure the Product Owner is informed about the team’s successes.
posted by: scrum methodology
Comments Feed Reader's Comments
Leave a Reply
Newsletter Sign Up:
Recent Posts
- The Daily Scrum; It’s a Good Habit to Make
- Obstacles to Enterprise Agility
- What is Scrum?
- Can CSMs and PMPs Get Along?
- Orlando Scrum Gathering in March 2010
- Free Scrum Webinars
- ScrumMaster as Impediment
- Advice for Agile Adoption
- Share Your Story
- Free Agile Resources
- Advice for Extending the Sprint
- Danube’s New Scrum Video Blogs
- What Happens at Scrum Training?
- The CSM Exam Saga Continues…
- The CSM Exam
Categories
- Agile and Scrum (18)
- Scrum Basics (33)
- Scrum Discussion (20)
- Scrum Transitions (9)
- Uncategorized (6)
Archives
- June 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
Blogroll
- Agile ALM
- Agile Methodology
- Agile Programming
- Agile Project Management
- Eric Brown
- Free Project Management Software
- IT Today
- PM Student
Danube on Twitter
- Overheard from a Twitter post by @sgamel
- Overheard from a Twitter post by @euro_latino
- Overheard from a Twitter post by @onion_soup
- Overheard from a Twitter post by @DarkSpooky
- Overheard from a Twitter post by @xiaoputi
- Overheard from a Twitter post by @jbuissing
- Overheard from a Twitter post by @andrewcmy
- Overheard from a Twitter post by @adrianoron
- Overheard from a Twitter post by @TheSoftwareGang
- Overheard from a Twitter post by @tshrinivasan

It seems like Scrum Masters are more into “Admin” type role? Is that entirely true? Also is Scrum Master a part tiem role and memeber will take in or would it be a full time?