The Rules of Scrum: Your ScrumMaster is truthful about the condition of the team and the Scrum process

Scrum relies on the ScrumMaster to be truthful and transparent about the reality of the team and how it is progressing in the use of Scrum. The condition of the team includes the ability of the team to discuss ideas, become united in their focus and build true bonds of friendship. It is valuable for the Scrum team to regularly identify the condition of its team informally through conversations and formally through the Scrum process. The ability of the ScrumMaster to help the team to reflect on its own team development helps them advance and overcome conflicts and challenges. It is also valuable to inspect and adapt on its use of Scrum so that it is aware and taking ownership of its own progress. A ScrumMaster that isn’t truthful about the condition of the team will be unable to help the team to advance and become a high-performance team. Reviewing the use of Scrum will help move the team to take on a posture of learning which will lead to the development of continuous improvement which is a tenant of Scrum. Those teams that don’t do this may fall into the trap of becoming “insane” – doing the same things each and every Sprint and expecting a different result. Regular and deep review of the team’s current state is essential for the team to become more productive, effective, and creative.

Find out more about how your team follows the rules by using the Scrum Team Assessment.

Try out our Virtual Scrum Coach with the Scrum Team Assessment tool - just $500 for a team to get targeted advice and great how-to information

Please share!
This entry was posted in Scrum, XP and Lean and tagged , , , by Mishkin Berteig. Bookmark the permalink.

About Mishkin Berteig

Mishkin Berteig is a Baha'i, a father of four, a husband and an experienced Agile consultant and trainer. Mishkin is a Certified Scrum Trainer (CST) with the Scrum Alliance, a certified Master of OpenAgile with the OpenAgile Centre for Learning and a certified SAFe Program Consultant (SPC) with the Scaled Agile Academy. Mishkin has a technical background including a B.Sc. in Computer Science and worked as a Chief Architect reporting to the CIO of Charles Schwab, but gave it up to be more Agile.

Leave a Reply

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

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>