When this story starts, we hear about a Product Owner that had the unfortunate habit of micro-managing the team and assignments. On top of that, the PO was also a yes-man, who wanted to say “yes” to everything the stakeholders came up with. We explore how these behaviors led to the team imploding, and discuss what we can do to help teams and PO’s who start showing the same symptoms.
Featured Book of the Week: Agile Product Management with Scrum: Creating Products that Customers Love
In Agile Product Management with Scrum by Roman Pichler, found a book that distills the concepts down to practical advice and helps the teams and the Scrum Masters focus on customer needs. He also found that the book allowed him to have great conversations with Product Owners, and coach the PO’s he worked with.
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 Arjay Hinek
Arjay has been an Agilist for over a decade. In the last few years he’s focused on Agile and “product development” for non-software applications. A considers himself a teacher at heart, he uses metaphors and story-telling to help others see their challenges from a different perspective and overcome them.
In a new team, Leland noticed that the skill silo (everyone sticking only to their skill specialty) was affecting the team’s ability to deliver. The team was working as if they were doing several sequential waterfalls instead of acting like a unit. Every time one team member was absent, the team couldn’t make enough progress to deliver.
In this episode, we talk about how to remove the skill silo, and avoid the mini-waterfalls anti-pattern.
In this episode, we also mention the Skills Matrix as a tool to visualize the skill silo.
Featured Book of the Week: The Lean Software Agile Development Toolkit by Poppendieck
In The Lean Software Agile Development Toolkit by Poppendieck, Leland found a new perspective on what it means to improve an organization. This eye-opening book is a regular read for Leland, and reminds him of the importance of looking at the flow of work (Flow Efficiency), rather than trying to optimize activities that may ultimately be wasteful.
About Leland Newson
Leland is a SAFe Release Train Engineer and servant leader who is passionate about helping improve the work environment and helping teams uncover better ways to development software. He focuses on collaboration, shortening feedback loops, improving the flow of work through the system and increasing the team’s adaptability so they can quickly respond to changes and satisfy customers through early and continuous delivery of valuable software.
When working with a team, Ronny noticed that the team was making progress. He was satisfied with the progress, and when asked to move to help another team he readily accepted. However, there was a bad surprise about to happen. Listen in to learn about what happened to those teams and what was the lesson that Ronny learned from this experience.
Featured Book of the Week: Start with Why by Simon Sinek
In Start with Why by Simon Sinek, Ronny found an insightful explanation of why we should help discover their purpose or reason to deliver on those User Stories. When reading the book, Ronny also understood how to ask the questions that lead to the team and the stakeholders discovering the answer to the “why?” question.
About Ronny Deicke
Ronny is a Scrum Master and Agile coach with a developer and team lead background. Currently working as a part-time Scrum Master and in the rest of the time giving (agile) workshops, supporting people as a coach and Agile Coach. Video game enthusiast and Indie developer on the side.
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
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.
That there are projects where teams feel under pressure is no news. In fact, stress-related to pressure is a very common problem in software teams. However, sometimes the situation goes too far and turns into a toxic culture. In this episode, we explore what are the signs that the normal “pressure” teams feel is turning into a much more impactful and negative set of patterns.
Featured Book of the Week: Co-Active Coaching by Henry Kimsey-House et al.
As Rachel grew in the coaching role, she felt frustrated by the reactive mindset she saw in leadership. That led her to explore other approaches to help executives understand and benefit from Agile Values and principles.
Rachel is passionate about individual and team growth. She has fostered an environment of collaboration and continuous improvement in the manufacturing, biotech, and software industries. Currently, Rachel is focused on the power of an individual and recently acquired her Leadership and Performance Coaching certification.