What is a common anti-pattern that Advanced Scrum Masters should be aware of?

The scenario where the Scrum Master acts as a bottleneck instead of a facilitator is indeed a common anti-pattern that Advanced Scrum Masters should recognize and address. In the Scrum framework, the Scrum Master’s primary role is to serve the team by facilitating collaboration, removing impediments, and ensuring the Scrum process is followed effectively. When a Scrum Master becomes a bottleneck, it means that they are not enabling the team to work autonomously or efficiently, often by controlling too many aspects of the process or by becoming the sole point of communication for any issues.

This behavior can hinder the team's productivity, as team members may feel they are unable to make decisions or progress without direct involvement from the Scrum Master. Instead, the Scrum Master should empower the team, encouraging self-organization and facilitating open communication so that the team can resolve issues independently and efficiently.

Recognizing this anti-pattern allows Advanced Scrum Masters to reflect on their practices and shift their mindset from being a controlling figure to one that nurtures and supports team independence and collaboration. Identifying and mitigating bottlenecks can greatly improve the team's overall performance and adherence to Agile principles.