The relationship between Product Owner and the team is critical. So critical that if it does not work, it has the potential to derail the whole effort. In this episode, we talk about how to identify possible problems in collaboration between the team and PO, and how to help teams and PO’s collaborate.
Are you having trouble helping the team working well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it at:bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.
About Bradley Pohl
Bradley is a young Scrum Master working for a mid-sized US bank that is currently undergoing an “Agile Transformation.” As a part of the Transformation, his training consisted of a 4 week Agile boot camp that was designed to build scrum masters from the ground-up. In his free time, he applies lean and agile principles to designing websites and providing social media advertising to local small business as Catch On, at catchontech.com.
How we set up teams has a direct impact on their ability to deliver. As Scrum Masters, we should pay attention to the early signs that something is going wrong. In this episode, we discuss the “platform team” anti-pattern, the dependencies that it causes and how we can raise the issue early enough to have an impact.
Jeremy Willets is a Technical Writer turned Scrum Master/Agile Coach. He’s passionate about bringing Agile to all facets of his organization. He enjoys spending time with his family, making music, and drinking the finest craft beer the world has to offer!
Teams change. It’s a fact. Some team members join, sometimes two teams get merged. That’s the story we talk about in this episode. Elena was facing a challenge. A new team was formed from two previous teams. How to help the team form?
Elena tried several things, including forming the team around a common goal they called “a mission”.
However, forming a team is not an easy task. What have you tried? Listen in to learn what Elena tried, failed, and then learned from this story.
In this episode we talk about Modern Agile, a movement to highlight some aspects of Agile that often get forgotten.
About Elena Popretinskaya
Elena considers herself a lifetime learner (she says, she absolutely loves having “aha!” moments). And she especially enjoys learning together with and from other people: her team and her friends. Elena is curious about everything: people, software craftsmanship and the world around. Elena is also a passionate hiker and a cross-country skier 🙂
As we work with several teams, it is impossible to avoid working with team members that just don’t have good chemistry. As Scrum Masters, we should be ready for when that happens! In this episode, we talk about a particular incompatibility between team members and reflect on how to handle this type of conflicts.
About Catrine Björkegren
Agile coach and scrum master, Catrine has worked with agile for a decade in various areas like education, nuclear waste, government agencies, pharmaceutical and at the Royal Swedish Opera.
She believes that co-location is the key to building teams and that leadership is the key to successful agile transformation.
When working with remote teams we must be aware that the number of meetings can easily balloon up because the team does not meet in the corridor. As Scrum Master, we must help remote teams find workarounds for the calendar-driven, meeting-inflated anti-pattern for remote teams.
In this episode, we discuss how a Scrum Master can help a team find the right balance between meetings and ad-hoc interaction even when remote.
About Kristopher Stice-Hall
Is the co-owner of Digital Maelstrom, a consultancy specializing in custom software, DevOps, managed cloud services, and information security. He has been doing Scrum Master work for over 10 years. He has worked with fortune 500 companies to companies less than 15 people. He also has been doing software development for 17 years.
Scrum is a relatively small framework for teams to adopt. Certainly much smaller than some of the Agile at scale frameworks. However, even small frameworks can take a while to adopt. In this episode, we reflect on some of the most common mistakes Scrum Masters make when helping teams adopt Scrum.
About Varun Maheshwari
Varun is a Scrum Master and agile practitioner in Australia. He believes in “being agile” rather than “doing agile”. For him, Agile frameworks are not the goal, but rather “Delighting customers, Zero Defects, Quick ROI, Better team work, Excellent Quality & Shortest ‘Time to Market’” are some of the possible goals.
After a successful assignment as a Scrum Master, it is possible we think we’ve got the role down to a T. However, reality between teams is so different that even great Scrum Masters can struggle when moving from one team to another. We share one such story, and what principles and practices we can take as Scrum Masters to focus our work on the new team.
About Elena Astilleros
Elena coaches people who hate wasting their time with badly run agile ceremonies, meetings or projects. She gives them tools to get more out of their time while sprinkling in a little enthusiasm and cheerleading. You can find some of her tools in the forthcoming book Invisible Leader.
Scrum Masters naturally want their teams to apply Scrum “the right way”, but there are risks with that approach. As Scrum Masters, we must be able to detect when a team is getting frustrated by our actions, no matter how well-intentioned they might be. In this episode, we talk about a team that started to feel frustrated by Eddy’s approach and how he reacted to that. Helping the team get back to the positive adoption of Scrum
About Eduardo Ribeiro
Eddy is passionate about helping people, teams, and organizations foster a culture of continuous improvement where experimentation and embracing change becomes part of their DNA.
He’s also the author of the Beyond Lean Agile Blog, a Co-Founder of the Lean Coffee Portugal Community, Founder of Agile Online Community and Co-Founder & Director of Startup Grind Porto.
Many Scrum Masters have a background in other roles within their teams. Some were developers, others Project Managers, others Testers, etc.
Many of those roles are “doer” roles. Roles that focus more on execution and less on helping others execute.
As Scrum Masters, we must be able to transition from “doer” to “enabler”, and Nedeljko shares his journey with us.
About Nedeljko Damnjanovic
Nedeljko is a Scrum Master and a full-stack developer who has been in the IT industry for the better part of the decade. He spent the last 5 years actively working as a Scrum Master with many diverse teams and projects who has helped him understand his role better. One of the core developers of the first VivifyScrum release, he has participated in its development product-wise ever since.
Joining a team, it is good to see that they have their tools in order. They can follow-up progress, track what is missing and even leave notes for each other in the items they add to the tool. The problem is when the tool starts to take over the team, instead of the team owning the tool. In this episode, we talk about the tool-Scrum anti-pattern, when the team focuses more on the tool than the things it should enable: communication, collaboration, progress assessment, and metrics.
Henrique is a Blockchain Product Manager (i.e. dealing with the blockchain related features/user stories of the product). He is passionate about teams and agile, using scrum to manage even his personal tasks.