The ScrumMaster

The ScrumMaster

ScrumMaster is a role in the Scrum Methodology. Sometimes it is written as “Scrum Master“.  Either spelling is correct and commonly used. The reason for the spelling is related to naming conventions in software development and the original Wiki. The ScrumMaster is responsible for the health of the team. They are sometimes referred to as the project manager but, this title is usually not appropriate.

The ScrumMaster removes impediments or helps identify impediments to be removed. The ScrumMaster helps both the team and the organization become better. A good ScrumMaster is someone who likes to work with people and can establish a pattern of continuous improvement.

The role of Scrum Master is distinctly and purposefully separated from that of the Product Owner so that there is a balance in both a a separation of interest and concerns.

A ScrumMaster with technical background is not required but, can help. However, the ScrumMaster does need to be passionate about people.

For more reading

Read Certified Scrum Master and how this key industry certification fueled an industry.

Read Scrum FAQs for a better understanding of Scrum.

Tagged with →  

5 Responses to ScrumMaster

  1. […] of as someone who is very senior in experience and typcially someone who has been an experienced ScrumMaster previously. A senior expert in Scrum can also be thought of as a Scrum Professional, certified or […]

  2. […] on work together and often one story at a time. This is an observable point of view an that the Scrum Master can use to detect when his/her team is starting to work well together. To an untrained observer […]

  3. […] The art of Backlog Management as with any complex endeavor is to keep things simple. Keeping things as simple and straightforward as possible is the job of both the Product Owner and Scrum Master. […]

  4. […] from the Scrum Alliance as a Certified ScrumMaster after the assessment given by the Scrum […]

  5. […] post I define Technical Debt and describe some of the issues.  In the past, I have stated that the ScrumMaster’s #1 issue on a Team is likely to be getting the Team to write Quality Code, which is code that the […]

Leave a Reply

Your email address will not be published. Required fields are marked *