In a class recently, a student asked a question that caught me by surprise. He asked if Scrum Master was a necessary role. If the team was fully engaged in approaching the work with an Agile mindset, inspecting, and adapting from one Sprint to the next both with respect to the deliverable AND the way they work together, AND they were self-organizing, then why would they need a Scrum Master? And, if management was imposing a Scrum Master on a team that was functioning this way, wouldn’t that indicate a lack to trust in the team?
In this episode of the podcast, I’m joined by the person who asked the question, Kyle Macey, who works as a Senior Backend Engineer at Chow Now. And, because I wanted to do my best to keep my bias in check during the conversation, I asked a friend, Bjorn Jensen, if he’d be willing to lead the discussion. Bjorn and I volunteer for the Scrum Alliance TAC together. He’s not only a CST with a background in development, Bjorn has a level of openness and calmness that I only wish I could achieve.