
Scrum Mythbusters: The Scrum Master Must Resolve Every Problem
About this episode
In this episode, it is all about how problems are resolved that are hindering a Development Team in their work. From a broken wifi router to a steady stream of meeting-requests from outside the team. And from clarifying unclear work to resolving a conflict between members. What problems should a Scrum Master resolve? What is the difference between impediments, blockers, problems and issues?
This audioblog is based on this blogpost:
http://bit.ly/2qmarBw
Follow us on Medium:
https://medium.com/the-liberators
Or check out our upcoming events at:
https://theliberators.com/events
Donate to support our work
https://bit.ly/supportheliberators
We're building Columinity to help teams improve continuously based on scientific insights:
https://columinity.com
Check out our webshop for tons of powerful exercises and workshops to run with your team(s):
https://shop.theliberators.com
The music for episodes 91 and onward was written and produced for us by Basanite. The music for episodes 1-90 was acquired through Yummy Sounds. Post-production by Jasper Huiskamp.
Get every episode summarized
Each time The Liberators Podcast publishes, we email you a written briefing from the transcript — the topics, who appeared, and any specific claims, with the ad reads skipped.
Email me new episodesFree for 3 shows. No card needed.
Hosts & guests
No transcript yet
This episode has not been transcribed. Request it and it moves to the front of the queue.
More episodes
More from The Liberators Podcast

In-Depth: What Is The Optimal Size For A Scrum Team?
The Liberators Podcast

5 Effective Ways To Increase Management Support For Agile
The Liberators Podcast

In-Depth: Is SAFe® Really That Bad?
The Liberators Podcast

In-Depth: How To Make Pair Programming More Effective
The Liberators Podcast