What is a common mistake a Scrum Master might make when introducing Scrum?

Assuming that the team already understands Scrum is a common mistake for a Scrum Master because it can lead to misalignment and ineffective implementation. Scrum is a framework that relies heavily on specific roles, events, and artifacts, all of which require a basic understanding to function effectively. If a Scrum Master presumes that the team has prior knowledge of Scrum principles and practices without verifying their understanding, this can create gaps in execution.

Without proper training and guidance, team members might not adhere to Scrum's best practices, leading to confusion about their roles, how to participate in events like Sprint Planning or the Daily Scrum, and how to engage with the product backlog. This oversight can compromise the team's ability to deliver value effectively and can foster frustration or resistance to the framework. It’s crucial for a Scrum Master to ensure that all team members are educated on Scrum fundamentals and to provide the necessary support for them to adopt the framework properly.

Incorporating a thorough onboarding process, including training sessions or workshops, sets a solid foundation for the team to embrace Scrum.