Scrum Master

A Scrum Master is a facilitator of a scrum process for a scrum team (that follows a scrum methodology).

• Context:
  • They can (typically) manage a Sprint Backlog.
  • They can (typically) lead a Daily Scrum Standup.
  • They can (typically) participate in a Scrums of Scrums.
  • They can be a Project Manager, Technical Program Manager.
• Example(s):
  • …
• Counter-Example(s):
  • a Project Manager.
• See: Software Engineering Team, Scrum of Scrums, Scrum Retro, Sprint Retro, Scrum Sprint.

---

---

References

2016

• (Wikipedia, 2016) ⇒ http://wikipedia.org/wiki/Scrum_(software_development)#Scrum_master Retrieved:2016-3-16.
  • Scrum is facilitated by a scrum master, who is accountable for removing impediments to the ability of the team to deliver the product goals and deliverables. The scrum master is not a traditional team lead or project manager, but acts as a buffer between the team and any distracting influences. The scrum master ensures that the scrum process is used as intended. The scrum master helps ensure the team follows the agreed scrum processes, often facilitates key sessions, and encourages the team to improve. The role has also been referred to as a team facilitator or servant-leader to reinforce these dual perspectives. The core responsibilities of a scrum master include (but are not limited to):
    • Helping the product owner maintain the product backlog in a way that ensures the needed work is well understood so the team can continually make forward progress
    • Helping the team to determine the definition of done for the product, with input from key stakeholders
    • Coaching the team, within the scrum principles, in order to deliver high-quality features for its product
    • Promoting self-organization within the team
    • Helping the scrum team to avoid or remove impediments to its progress, whether internal or external to the team
    • Facilitating team events to ensure regular progress
    • Educating key stakeholders in the product on scrum principles
  • One of the ways the scrum master role differs from a project manager is that the latter may have people management responsibilities and the scrum master does not. Scrum does not formally recognise the role of project manager, as traditional command and control tendencies would cause difficulties

2014

• http://whatis.techtarget.com/definition/scrum-master
  • QUOTE: A scrum master is the facilitator for a product development team that uses scrum, a rugby analogy for a development methodology that allows a team to self-organize and make changes quickly. The scrum master manages the process for how information is exchanged.

    Although the scrum analogy was first applied to manufacturing in a paper by Hirotaka Takeuchi and Ikujiro Nonaka, the approach is often used in agile software development and other types of project management. In rugby, opposing teams huddle together during a scrum to restart the game. In product development, team members huddle together each morning for a stand-up meeting where they review progress and essentially restart the project. During the daily meetings, which are sometimes called "scrums," the scrum master asks the team members these three questions:

    1. What did you do yesterday?
    2. What will you do today?
    3. Are there any impediments in your way?

---

2020

• (Wikipedia, 2020) ⇒ https://en.wikipedia.org/wiki/Scrum_(software_development)#Scrum_master Retrieved:2020-4-27.
  • Scrum is facilitated by a scrum master, who is accountable for removing impediments to the ability of the team to deliver the product goals and deliverables. The scrum master is not a traditional team lead or project manager but acts as a buffer between the team and any distracting influences. The scrum master ensures that the scrum framework is followed. The scrum master helps to ensure the team follows the agreed processes in the Scrum framework, often facilitates key sessions, and encourages the team to improve. The role has also been referred to as a team facilitator or servant-leader to reinforce these dual perspectives. The core responsibilities of a scrum master include (but are not limited to): * Helping the product owner maintain the product backlog in a way that ensures the needed work is well understood so the team can continually make forward progress * Helping the team to determine the definition of done for the product, with input from key stakeholders * Coaching the team, within the Scrum principles, in order to deliver high-quality features for its product
    • Promoting self-organization within the team
    • Helping the scrum team to avoid or remove impediments to its progress, whether internal or external to the team
    • Facilitating team events to ensure regular progress
    • Educating key stakeholders on Agile and Scrum principles
    • Coaching the development team in self-organization and cross-functionality
  • The scrum master helps people and organizations adopt empirical and lean thinking, leaving behind hopes for certainty and predictability.

    One of the ways the scrum master role differs from a project manager is that the latter may have people management responsibilities and the scrum master does not. A scrum master provides a limited amount of direction since the team is expected to be empowered and self-organizing. Scrum does not formally recognise the role of project manager, as traditional command and control tendencies would cause difficulties.