When teams are pressured or pushed to work harder, or longer hours, the easy solution is to just say yes, and carry with it. However, the role of Scrum Masters is to help teams understand and prevent those cases when the “work harder” mantra is disconnected from the goals of the company. In this episode, we discuss one such example, where the team was not able to say “no” to the PO, and was, therefore, pushed to do more, and more work and forgetting to focus on improving as a team.
Featured Book of the Week: Leading Teams by Richard Hackman
In Leading Teams: Setting the Stage for Great Performances by Richard Hackman, Pieter found the results of a long research process that lead to defining some of the conditions and patterns that exist in successful teams. One such aspect was the definition of goals for the team. We explore what that means in practice and how to apply it as a Scrum Master.
About Pieter Verbaarschott
Pieter is a hands-on generalist with a background in software development. A passion for helping teams work together better. Agile aficionado since his first endeavors in Extreme Programming. Happened to be among Agile Manifesto authors when the discussion was hot. And he refuses to work the traditional way.