Paths to Agility: A Developer's Journey to Scrum Master

Kate and Ryan come at agility from opposite ends of the org chart. Kate arrived through training, operations, and project management on the leadership side. Ryan started as a front-end developer who built a Kanban board before he knew it had a name.  In this episode they trace Ryan's path from coder to Scrum Master, and dig into the questions every agile practitioner eventually asks.  Does a Scrum Master need to be technical?  What does the role really protect?  Why do so many transformations stall without a dedicated Scrum Master?

Ryan makes the case that Scrum is agnostic to the work itself, that the Scrum Master creates the air the team breathes, and that the most important job is enforcing the pact between the team and the business so developers can do their best work without interruption.  He closes with practical advice for anyone growing into the role: go back to the Scrum Guide, get certified, and strip away the barnacles you have collected from role to role.