“We believe the ScrumMaster is a full-time position for one person on one Scrum team”


First created at the Scrum Alliance Global Gathering London, 11-13 October 2011

This manifesto has been created by ScrumMasters to help other ScrumMasters become better ScrumMasters. Please share this with those who you feel would benefit from reading it. For the latest updates to this guide based on empirical feedback from the practising community, and to show your support, follow @ScrumMasters on Twitter.

Facilitates the scrum process, remove impediments, delivers value, helps and guides people.

A ScrumMaster defined in 15 words or less...

The person who guides the team towards self-organisation and achieving the goal.
ScrumMaster is concerned about the system (people and tools) that create the product.
The ScrumMaster helps the team to continuously improve to have effective products whilst having fun.
ScrumMaster is someone who facilitates a team and makes the members collaborate together.
A change agent that grows a high-performance, continuously improving team that delivers value.

12 ScrumMaster Pocket Principles...

1.    Dedicated Delivery Improver

2.    Foster Continuous Improvement

3.    Help Continuous Improvement

4.    Empower Coach Deliver

5.    Nurtures The Team

6.    Transparent Team Helper

7.    Commitment To Excellence

8.    Empathetic Evangelistic Guide

9.    Resistant Persistent Dedicated

10.  Help The Team 

11.  Awareness Then Improvement

12.  Agile Driving Force

Top 10 things a ScrumMaster usually forgets to focus on (but is not SOLELY responsible for) ...

1.    Redefining career paths and goals to be more scrum focussed

2.    Missing Product Backlog items

3.    Team issues aren't being discussed because they are too uncomfortable

4.    Appropriate balance between end-to-end system test and unit tests

5.    Playing back the team's progress against the proposed release plan

6.    All tests roll up into the continuous integration results

7.    Team members realise the benefits of refactoring

8.    Code is regularly peer reviewed

9.    Pair programming is being utilised

10.  Definition of done is being expanded

version 1.2

DISCLAIMER: This manifesto is intended to be a guide for ScrumMasters to reflect and improve, not as a mandate for strict compliance. This has been created from an awareness that many new or inexperienced ScrumMasters may be compromising their role through a lack of understanding or knowledge, hence compromising their teams ability to become more self-organising. All the content was formed from data gathered from surveying 100 active ScrumMasters, and using consensus exercises with the 40-50 people who attended this session at the Scrum Alliance Global Gathering London, 11-13 October 2011. The vision is to iterate this artefact by running similar exercises with other ScrumMasters to show how the role is changing over time.