The Common Mistake Scrum Masters Make and How to Teach Teams to Fish

Many years ago the author transitioned from project manager to Scrum Master, believing the change would be simple, only to discover that abandoning a command‑and‑control mindset is far more challenging.

He recounts frequent errors such as turning the Daily Scrum into a reporting session where developers list yesterday’s work and today’s plans, and the Scrum Master merely moves sticky notes on a board and asks whether tasks are finished.

The article argues that this behavior must change: the Scrum Master should teach the team to track progress, plan, solve problems, and collaborate with the Product Owner, essentially “teaching them to fish” rather than managing them.

When the Scrum Master adopts a coaching stance, the team becomes self‑organizing, allowing the Scrum Master to step back from Daily Scrums and focus on facilitating rather than directing.

The author also recommends using the term “Daily Scrum” as defined in the Scrum Guide, emphasizing that the meeting is a Scrum practice, not just a stand‑up, and that the shift in mindset is crucial for successful agile transformation.

Finally, readers are invited to reflect on the current state of their Daily Scrum and consider how to enable their team to collaborate efficiently even in the Scrum Master’s absence.

Original author: Dan Sloan, Agile Coach and Scrum.org certified trainer.