PO collaboration Archives - Page 6 of 13 - Scrum Master Toolbox Podcast

Gemma Murray: The Key to Successful Agile Product Ownership, The Value-driven Product Owner

The Great Product Owner: The Key to Successful Agile Product Ownership, The Value-driven PO

In this segment, Gemma highlights the importance of a great Product Owner (PO) in agile methodologies. A great PO is always asking “why”, and is constantly seeking to understand the value of the product and the work being done by the team. Gemma describes a PO that came into a team that was maintaining a product, but with their focus on value and constant seeking of feedback, they were able to pivot and make improvements based on data and customer feedback. The PO was able to maintain a great relationship with the team by always listening and acting on feedback from the outside.

The PO focused on collecting metrics to validate their ideas and make data-driven decisions. By being able to listen to and act on feedback, the PO was able to make quicker and better decisions that were in line with the needs and wants of the customer. This ability to listen and act on feedback is a superpower for any PO and is key to their success in agile methodologies.

The Bad Product Owner: The Destructive Effects of a Disempowered Agile Product Owner

In this segment, Gemma discussed a common anti-pattern in product ownership, where the Product Owner may not feel empowered to make decisions. This can result in the team looking for clarity from other sources and the PO not feeling like they are part of the team. Gemma recounted out a real-life scenario where a PO manager became involved in the product development process and started imposing ideas onto the backlog. The manager believed they were supporting the PO and team but this resulted in the PO becoming a silent voice in the team.

To address this issue, Gemma offered several tips. She advised sharing observations with the manager to help them reflect on their behavior, separating behavior from consequences, and avoiding assumptions about others’ thoughts. It is important to clarify the consequences of the behavior, in this case, the PO not feeling confident enough to make decisions on the product. By taking these steps, Gemma aimed to help others resolve similar challenges in product ownership.

Are you having trouble helping the team work 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 Gemma Murray

Gemma works as an Agile Coach for MOO, a branding company whose vision is to provide ‘Great design for everyone’. Having worked in various change roles using both waterfall and agile approaches throughout her career, Gemma believes in the diversity of teams to unlock innovation, creativity and delivering value.

You can link with Gemma Murray on LinkedIn.

Tinatin Tabidze: The key to an awesome Agile team, the hands-on and insightful Product Owner

The Great Product Owner: The key to an awesome Agile team, the hands-on and insightful Product Owner

Tinatin highlights the key traits of a good Product Owner (PO) in this segment. She emphasizes that great PO’s are knowledgeable about the product they are working on, as well as its competitors. This knowledge helps the PO to understand what the team needs in order to deliver the best possible product. The PO should be hands-on with the team, and should work closely with them on defining clear acceptance criteria. This helps the team to understand what is expected of them and enables the PO to be more effective in their role.

Tinatin also notes that a great PO is easy to work with and has a good synergy with the team. She mentions that the synergy between the PO and the team is a telling factor in the team’s success. She stresses that there’s not only one way to be a great PO, as different PO’s can have different approaches to the role, but when a PO combines knowledge about the product and its competitors with a hands-on approach to working with the team, the result is an awesome PO.

The Bad Product Owner: Unleashing the Full Potential of a Product Owner in partnership with the Scrum Master

In this segment, Tinatin starts by questioning the essence of the PO role and highlights the importance of commitment and ownership of the product for a team’s success. Tinatin emphasizes that a PO should have a clear vision and evolve it based on data and feedback. She stresses the need for a PO to have a foot in both development and business and to be hands-on with the product. As a Scrum Master, Tinatin suggests testing the product and making time to play with it to help the PO understand it better. She also suggests sitting down with the PO to build a roadmap for the product and to ask why they value certain features or deliveries. Lastly, Tinatin highlights the importance of the PO being able to sell the ideas in the backlog to the Scrum team and recommends using tools to help the PO take a more active role with the team. Tinatin also mentions the books by Roman Pichler as resources for Scrum Masters and Product Owners.

About Tinatin Tabidze

Tinatin Tabidze is a Scrum Master currently working in Stuttgart, Germany. Originally she started out as a project manager. She has experience with multiple scrum and kanban teams, working with scaled agile frameworks.

You can link with Tinatin Tabidze on LinkedIn.

Bram De Block: Working with great Technical Product Owners, and how they use their technical expertise to help the team

The Great Product Owner: Working with great Technical Product Owners, and how they use their technical expertise to help the team

Great Product Owners can have a technical background, and use it to the team’s and their own advantage. Bram notes that the PO’s understanding of the impact of technical debt makes it easier for them to understand the team’s struggles. Leading to productive conversations, and the team being given time to handle technical debt issues.

Bram advises that a great Product Owner should be present and available to the team, sitting down with them during lunch breaks to discuss issues and concerns. He suggests helping the PO develop their own system to keep the product backlog manageable and addresses common counter arguments he gets from PO’s when asking them to limit the size of their backlog. Bram also provides tips on how to have a conversation about the consequences of adding too many things to the backlog and how to help the PO say “no” to stakeholders.

The Bad Product Owner: Working with technical PO’s to address dictatorial behavior and improve team motivation

Sometimes, Product Owners who have a technical background tend to dictate solutions to the team without considering other options. Bram notes that these PO’s are often not open to different or better solutions and even question the team’s progress. He suggests addressing this issue by making it transparent, showing the impact it has on the team, and discussing how team members feel about the collaboration with the PO.
Bram also highlights the impact this behavior has on team motivation and provides tips on how to handle this situation, such as using real situations to help the product owner reflect and encouraging open discussion of team feelings in the retrospective.

About Bram De Block

Bram is not an official trainer, consultant nor freelancer. He is just himself, supporting colleagues in applying and growing their own potential and getting stuff done. Bram started as a software developer for 10 years, then grew into a half-time agile coach, and finally, full-time “Global Agile Lead” at Skyline Communications. Something “special” he learned (even if he wishes it wasn’t special): the meaning and impact of “respect”.

You can link with Bram De Block on LinkedIn, or meet Bram face-to-face at this meetup he hosts in Belgium.

Pino Decandia: The Product Owner committee, a serious anti-pattern

The Great Product Owner: The perfect project, with the perfect PO

The Product Owner Pino describes was intimately familiar with the product, and the problem that needed to be solved with it. Because of this, the PO did not have to seek permission or confirmation from someone else before making decisions. The PO was empowered! Also critically, the PO was “the face” of all decisions with the client, which allowed him to protect the team from unnecessary pressure. As Pino describes it: “it was the perfect project”!

The Bad Product Owner: PO by committee, a serious anti-pattern

Instead of one Product Owner, this project had a committee of people who were assigned the overall PO role. However, in this case, the committee did not work to fulfill the PO role. The conflicting needs in that group of people led to decisions that took too long, and to the alienation of the team, who was not allowed to give input after a decision because the committee was not able to process the feedback.

About Pino Decandia

Pino started in software development but realized he was more interested in people than code. With experience, Pino came to believe that people can change; they don’t resist change but offer their own vision, which needs to be met.

Secondly, needs drive behaviors. To provide help, we must allow them to be clearly expressed. To set the example, we need to be ready to be the first to state our needs.

And thirdly, that ideological battles are meaningless.

You can link with Pino Decandia on LinkedIn.

Peter Janssens: The core value of the User Story format for Scrum teams and Product Owners

The Great Product Owner: The advantage of knowing Scrum in depth!

This Product Owner had a deep understanding of Agile and Scrum. This enabled him to focus on the core interaction with the team. Every week, he’d meet with the team for the Review and Planning meetings. Through that, he was able to guide the team, communicate the updated Vision for the product, and help the team select the stories for the Sprint without overcommitting. The knowledge the PO had of Scrum helped him focus on the right communication cadence, and topics with the team!

The Bad Product Owner: The core value of the User Story format for Scrum teams and Product Owners

Peter was a Product Owner for one of his first projects. The project was very well defined and prepared, and they decided to do it with Scrum. Peter then tried to split the requirements and work packages into stories on his own. However, he did not reformulate the requirements in a way that would convey the goal or purpose of each story, or the product itself to the team. This experience helped Peter understand why the User Story format is so important.

In this segment, we talk about Inspired, the book by Marty Cagan.

About Peter Janssens

Peter built a long career in agile coaching and training, and worked in leadership positions leading a PO team, and recently became CTO in a SAAS product company. Peter loves all conversations on effectiveness of team decisions, but he quickly realized that being responsible is different from being a coach. As a leader there is the challenge of sticking to the same foundations when dealing with delivery pressure.

You can link with Peter Janssens on LinkedIn.