When certain behaviors emerge in a team, the consequences can be catastrophic. In this episode, we talk about what happens when one of the team members tries to constantly push their perspective. We discuss what were the consequences for this specific team, and how we can ensure that the team does not fall into a negative spiral of conflict, rumors, and disengagement.
Featured Book for the Week: The Scrum Guide
Although The Scrum Guide is not a book, it is a reference document for everyone wanting to practice Scrum at work. While the rules in the guide are simple, the more we read them, the more insights we get into the heart of Agile and Scrum.
About Angeliki Hertzfeldt
Angeliki finds that Scrum has transformed her into a better person: in the working environment, with friends and strangers, in social activities, and with her family, as a new mum.
This team that Joost was working with was confronted with top-down decisions over which the team had no control. As an example, Architects would tell the team what to do, and how to do it, but would not listen to the team’s perspective. Slowly the team lost motivation, and the bad results quickly followed. In this segment, we reflect on the impact that the environment had on the team, and what Scrum Masters can do to work with teams in that situation.
Featured Book of the Week: Management 3.0 by Jurgen Appelo
In Management 3.0 by Jurgen Appelo, Joost found the inspiration he needed to focus on the overall organization, as opposed to focusing only on the team. We discuss the example of Delegation Poker from Management 3.0, which shows that delegation is not a binary game, but can have many levels and approaches.
About Joost Mulders
Joost has been an agile practitioner since 2008 and is continuously uncovering new ways to help teams and organizations on their agile journey. He’s taken several roles in that journey, such as Scrum Master, agile coach or management coach. He strives to create work-life fusion with agile, ultrarunning and filmmaking as the main ingredients.
In some teams, the role of the leader or manager can be a blocker to the team’s adoption of Agile and ownership of the product and process. However, those same managers usually develop their command and control approach due to past successes. As Scrum Masters, we must learn to work with those teams, starting by creating a close relationship with the team members.
Featured Book of the Week: The Advantage: Why Organizational Health Trumps Everything Else In Business
In The Advantage by Patrick Lencioni, Remy learned about the concept of an executive team that he could apply to his own product when his team was struggling with direction.
In this segment, we also refer to Start with Why, by Simon Sinek, a book that helped him understand the importance of communicating the rationale behind the decisions and involving the team in owning those decisions.
About Remy Fletcher
Remy is a Scrum Master at a Fin-Tech corporation outside of Boston. Currently working with 3 scrum teams with a focus of migrating individual products onto a centralized, scalable platform.
The focus that some teams have on “execution” can be a great resource. It helps teams get into the details, and push forward even when finding the inevitable setbacks. However, when teams are completely focused on execution there are other aspects that lose focus, and that can derail the team. In this episode, we talk about how the execution focus that some teams have lead them astray from certain critical aspects of the software development process.
Featured Book for the Week: The art of doing twice the work in half the time, Jeff Sutherland
In The art of doing twice the work in half the time by Jeff Sutherland, Micah found a great reminder and introduction to the Lean principles he now applies in his own work. He also found a great reminder that software development has its own context, that needs to be taken into account in the work Scrum Masters do with software teams.
About Micah Stamper
Micah worked in technology for about 7 years. He has a background in lean principles and how to bring that to technology. Has done everything from Project Management to Software Engineering, Leadership, and Scrum Master.
When Rahul started to work with a team that was new to Scrum and Agile, he noticed that the team members were very focused on their individual part of the product. Front-end developers only worked and worried about the front-end, and back-end developers focused on the back-end functionality. In the Sprint reviews, team members focused on their individual contribution, and the inevitable synchronization and coordination problems followed.
In this episode, we talk about the risks of highly specialized teams and how to tackle those in your role as a Scrum Master.
Featured Book for the Week: The 4-hour workweek by Tim Ferriss
In The 4-hour workweek by Tim Ferriss, Rahul found an inspiring story about the choices we make in our daily lives. He learned about “time” as a spendable resource, and how to create more options for yourself as you seek a better life situation. In this segment, we also refer to the Tim Ferriss podcast.
About Rahul Bhattacharya
Rahul Bhattacharya is currently working as an Agile Coach at trivago. He is responsible for optimizing the ways of working within the organization, coaching others on best practices while simultaneously guiding teams working on different products. Rahul is passionate about constant learning through experimentation and feedback.
He is also the host of a podcast about Agile, called the Agile Atelier.