In this episode, we explore the dynamics that may happen between the Product Owner and the team. And how, sometimes, those dynamics can spiral and affect the team’s ability to perform. We also discuss how to approach the topic with the team and the Product Owner. How we choose to tackle the situation, and our communication approach may help or destroy that relationship.
The relationship between Product Owner and Team is critical for our success as Scrum Masters. Learn how to coach your product owner in our Coach Your Product Owner course. The Coach Your PO e-course includes 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.
Featured Book for the Week: Crucial Conversations, Patterson et al.
Olsen is an experienced Agile Coach and Scrum Master with a mix of Servant Leadership skills and technical knowledge acquired over his decade-long career. His background includes Ph.D. studies in Organizational Leadership, Agile Transformation and Coaching, Project Management, and Scrum Master duties.
Sometimes teams need to focus on consensus building, but at other points in their journey, their need to seek consensus is a sign that the team is avoiding conflict. In this episode, we talk about the case of a team that was undermining itself by trying to always establish consensus before taking action.
Featured Book for the Week: Radical Candor, Kim Scott
In Radical Candor by Kim Scott, Sami learned about the importance of building relationships and being in compassionate mode with fellow co-workers. She also found invaluable tips on how to get and give feedback to her co-workers.
It’s impossible for us to go an entire career without having to face difficult anti-patterns by management. We need to be ready to tackle those. In this episode, we talk about a team that wasn’t ready, and how the bad decisions by management triggered a negative spiral for that team.
As our workforce changes rapidly, Tom suggests it is going to be more and more challenging to attract and keep talent and knowledge, and that’s why we need a healthy and sustainable working environment. Tom is passionate about improving the industry for his children and their generations.
Retrospectives can be an engine of growth for the team, but they can also turn in complain fests, where teams drown in negative comments. However, this is not inevitable. In this episode, we talk about how Retrospectives can be turned in a positive tool for improvement when Scrum Masters help teams understand and focus on what they can influence, instead of complaining about what they have no power over.
In this segment, we also mention the “Food for Agile Thought” Newsletter at the Age of Product blog.
About Thomas von Busse
Thomas is a Scrum Master since 2013. After his Bachelors’s Degree in Software Engineering, he gained experience as a Programmer and uses this deep understanding of how to build software systems to help his Teams get better with each iteration.
When teams work well together, you won’t find much conflict. But when you don’t see any conflict in a team, that should make you wonder whether the work is so clear, or if the team is actively avoiding conflict. In this episode, we explore the story of a team that was actively avoiding conflict, and discuss why that is a problem for the team’s progress and performance.
Featured Book for the Week: The Monk Who Sold His Ferrari: A Fable About Fulfilling Your Dreams & Reaching Your Destiny
In The Monk Who Sold His Ferrari by Robin Sharma, Bola found an inspiring story about why he works, and what motivates him as a Scrum Master. In that book, Bola found many different lessons that inspire him as a Scrum Master.
About Bola Adesope
Bola is an experienced Business and Agile Transformation Consultant, Speaker and Coach with in-depth knowledge and experience working with businesses in implementing best practice frameworks, driving changes and solving complex business problems. Bola has worked on several transformation initiatives, coached teams and Scrum Masters. He’s an Agile Coach based in Toronto.
Sometimes we work with teams that are in a context where Agile values and principles are not applied correctly. In this episode, we explore the story of a team that thought they were practicing Agile, but in fact, were still in the Waterfall mentality. We discuss how the mentality of the team directly affects their ability to understand and benefit from Agile ways of working.
Featured Book of the Week: The Scrum Field Guide by Mitch Lacey
Leslie is a full-time Scrum Master. Prior to that Leslie was a Project Manager, and started her career as a mainframe database developer (COBOL, HCL, DB2, Oracle, Unix). After that, she moved on to Java support for a few years. Finally, she transitioned to an analyst role, and it was in that role that she first encountered Agile and Scrum.
Darren, aka the Naked Scrum Master, has been helping teams and organizations be better than they were by exposing dysfunction and helping people to remove obstacles from their path so they can be happier and more fulfilled in their working lives.
It is tempting to make project managers the new Scrum Masters. They just need to be trained, right? In this segment, we discuss what can happen when people with the wrong mindset get assigned to the position of Scrum Master. We also talk about the different leadership styles that Scrum Masters need to embrace.
Featured Book of the Week: Scrum a pocket guide by Gunther Verheyen
Addo is a good team player, has a broad experience in different roles (Agile Coach, Scrum Master). Trainer in Agile. He communicates very well within all levels of an organization. He is motivated by structuring, getting people to work together towards a common goal, and bridge the gap between Business and IT.
In this episode, we explore the story of a team that was scattered and working outside the office. We then explore the anti-patterns that made those team members feel like outsiders in their own team. Finally, we talk about the antidote, what to do to make the team feel like a team, no matter where they are.
Featured Book for the Week: The culture code, Daniel Coyle
In The Culture Code by Daniel Coyle, Rik found a definition of the characteristics of successful groups. What makes them tick and got some inspiring stories that help him be a better coach for his teams.
About Rik Pennartz
Rik is an agile coach, who’s worked during the last years at the Volksbank, the Dutch Railways and ABN AMRO bank. Rik also teaches various agile courses such as Professional Scrum Master, DevOps fundamentals and Leading SAFe.
When all works well with a team, there’s the temptation for us as Scrum Masters to think that the “team gets it”, but even if that is the case, your role, and who you are is part of that system. When you leave things will be different. In this episode, we explore what happens when the Scrum Master leaves, and the previous technical lead takes over. In this story, we will hear the anti-patterns that can easily develop when the critical role of the Scrum Master is taken by someone else.
Mo started her career in education and program management before moving into digital delivery. She’s pretty sure she was a servant-leader before she had even heard the term. Her passion is to build healthy teams and foster the all-important relationship between business and team, which allows a safe space for the magic to happen.