Oskar Collin: Why relationships matter in the performance of a Scrum Product Owner

From the control-minded PO to the PO that wanted to learn and co-create with the team. This week’s PO patterns enlighten the need for focusing on the relationship building between the PO and the team, and the PO and the Scrum Master.

The Great Product Owner: The PO that wanted to run experiments

Great PO’s come in many shapes and forms, in this episode, we talk about the great PO that wanted to run experiments, to learn what worked in practice. We also talk about the importance of the relationship between Scrum Master and PO, and how that partnership can drive the success of the PO and the team.

The Bad Product Owner: The Control Freak

There are many reasons why the PO’s may not be able to perform as needed in a Scrum environment. However, the toughest reasons or root causes for that lack of performance are often tied to the PO’s own personality. In this segment, we talk about the reasons why some PO’s can’t give up control, and how that search for control directly affects the team’s ability to perform.

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 Oskar Collin

Oskar is a former software developer who became a passionate agile coach and Scrum master. He did so mainly because he was better at helping teams working together than building software. He loves experiments and questioning the status quo. He is passionate about helping teams build digital products and deliver value continuously. 

You can link with Oskar Collin on LinkedIn and connect with Oskar Collin on Twitter

Stefania Marinelli: The PO that knew how to engage the Scrum Team

Working with the team, in the right way, is critical for the PO to succeed, so we explore what a great PO would do differently, and what are some of the anti-patterns we should be looking out for.

The Great Product Owner: The PO that engaged the Scrum Team

When the PO listens to the team, and works every day to help solve some of the blockers that that team is facing is on the path to being a great PO. But the key is when the PO is present with the team, not only to listen but to understand how to help the team succeed. When this happens, the PO is contributing to the team feeling engaged and passionate about their work!

The Bad Product Owner: The “New day, new priority” PO

In this segment, we discuss several anti-patterns to be on the look-out for. We talk about the PO that wants too much technical detail, and the constant change in priorities that sometimes comes from the Product Owner. 

Finally, we talk about decision making, and how important it is to have a PO that can bring the right people into a meeting to make quick decisions.

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 Stefania Marinelli

Stefania is an Agile Manager @Hotels.com (Expedia group) former Scrum Master, former team leader/project manager, former developer. Stefania is fascinated by people dynamics and works every day to create a collaborative and safe environment. NVC practitioner.

You can link with Stefania Marinelli on LinkedIn and connect with Stefania Marinelli on Twitter

BONUS: 4 critical Product Owner anti-patterns with David Pereira

In this special BONUS episode with Daniel, we cover some of the most serious Product Owner anti-patterns. These are anti-patterns that can severely affect the teams’s ability to deliver, and to focus on value. 

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.

 

And we start with a big myth about the PO role…

Does the Product Owner REALLY own the Product Backlog?

Continue reading BONUS: 4 critical Product Owner anti-patterns with David Pereira

Anubhuti Agarwal: Extreme ownership, the Product Owner’s secret power

Feeling ownership of the product, and performing like an owner is one that really differentiates great PO’s from the rest. We also discuss what happens when the PO takes their role as a part-time job

The Great Product Owner: The impact of feeling the ownership of the Product

Although the clue is in the name, the fact is that many Product Owners miss the impact of that ownership perspective on the role. In this segment, we discuss what Ownership means for the PO role and the impact that it can have in the team when the PO expresses that feeling of ownership.

The Bad Product Owner: The part-time Product Owner

The PO role is not a part-time role. However, some people tend to think that it is possible to perform that role successfully while also being a leader of a department or organization. In this segment, we discuss the anti-patterns that emerge when the PO role is taken as a part-time job. We also discuss some of the ways in which the Scrum Master can help the PO realize the impact they have on the team when they are not available full-time.

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 Anubhuti Agarwal

Anu is a software tester turned Scrum master. She worked as Software QA in India for 6 years and then moved to Berlin to complete her Masters in Business Administration. She has been working as a Scrum Master for 3 years in an agency and has learned, first hand, the challenges of working with Agile in an agency.

You can link with Anubhuti Agarwal on LinkedIn.

Thomas Kofoed: Coaching the PO together with the Scrum team

Great Product Owners can tell stories, and motivate the team. They focus on the Vision and the “why” questions. In contrast, the anti-pattern we discuss in this episode is that of the command and control PO, who wants to know who’s working on what, and how they are doing it.

The Great Product Owner: The Great Storyteller

Thomas shares with us what a great storyteller Product Owner looks like. We discuss the impact of storytelling, and the need for the PO to be constantly learning so they can bring the right information and answer the team’s questions.

The Bad Product Owner: Coaching the PO together with the Scrum team

What should a PO focus on? In this segment, we discuss how the command-and-control PO’s focus on the wrong topics, and miss the most important aspects of their work. We also discuss how to encourage the team members to help coach the PO towards the most effective behaviors and actions.

 

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 Thomas Kofoed

Passionate Agile Coach / Scrum Master. Thomas focuses on engaging people while helping organizations and teams evolve their products guided by the feedback from their customers/users. 

Thomas switches between Facilitation Coaching and Teaching (sometimes Mentoring). He’s open about his purpose and that he strives to get his teams to where they don’t need him but might miss him 🙂 

You can link with Thomas Kofoed on LinkedIn

Denniz Dönmez: How to succeed as a Junior Product Owner

Seniority is not always a good asset for a Product Owner, but attitude and mindset can be. In this episode, we explore the kind of attitude and mindset that help Product Owners succeed.

The Great Product Owner: How to succeed as a Junior Product Owner

When a junior PO joined the team Denniz was working with, the expectation was that there would be certain challenges ahead. Turns out, being a junior was a great advantage for this Product Owner because of the attitude and the mindset he brought with him. Listen in to learn about some of the key attributes needed to succeed as a Product Owner when just starting to learn the role.

The Bad Product Owner: The Project “Owner” anti-pattern

When Product Owners come to the teams from a Project Manager role, they usually bring a specific mindset that has served them well in that previous role. However, those same patterns that worked well in a project management paradigm, don’t work so well when the role is the Product Owner role. In this segment, we discuss some of the anti-patterns that emerge when Project Managers join a Scrum team as a Product Owner.

 

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 Denniz Dönmez

Denniz has both huge academic and practical experience. He studied agile teams for his PhD at Swiss Federal Institute of Technology in Zurich (ETH Zurich) before becoming a Scrum Master and freelance consultant in 2016. Denniz believes the key to becoming more agile is to establish what he calls “enabling structures.”

You can link with Denniz Dönmez on LinkedIn and connect with Denniz Dönmez on Twitter

Samantha Menzynski and Brian Ziebart: The large backlog as a PO anti-pattern

In this episode, we talk 4 PO patterns, and discuss several techniques on how to recover from the anti-patterns we discuss.

The Great Product Owner: Difficult conversations as a catalyst for a better story and product understanding 

Good PO’s are there for the team, and answer their questions. However, great PO’s are able to have difficult conversations that help clarify the reasons for the Stories and motivate the team. Sometimes, those hard conversations lead to changes in the product. And that’s a good thing! For both teams, and PO!

In this segment, we talk about a tip: have the PO define “team hours”, when they sit with the team and answer their questions.

The Bad Product Owner: The large backlog as a PO anti-pattern

When the PO is not able to handle the Product Backlog anymore, the team will suffer. In this segment, we talk about a PO that had trouble keeping up with the Backlog as it was large, unwieldy, and had no structure. We discuss how the team helped the PO clear the backlog, and what tools and techniques they used to keep the backlog short and under control. 

Another anti-pattern we discuss is the PO who was too much into the details and lost the big picture. When that happens, the PO can’t help the team understand the “why”, and removes the motivation that comes from understanding the purpose of the work. We discuss how the PO can step back and help the team regain their motivation and convey a clearer picture of the reasons for the product changes.

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 Samantha Menzynski and Brian Ziebart

Samantha Menzynski has spent her entire career in software. Starting in support and account management, moving to customer support management, and with Penta’s transformation to Scrum becoming Scrum Master for the Core product team.

You can link with Samantha Menzynski on LinkedIn

Brian Ziebart started his career in software as a developer but found himself wanting to move towards coaching and developing people rather than product development.  When Penta’s Scrum transformation started in August 2019, he jumped at the opportunity to work more with people while still staying involved with development.

You can link with Brian Ziebart on LinkedIn

You can read more about Samantha’s and Brian’s work and the Agile transformation they were part of in this Scrum.org blog post.

BONUS: Collaboration between Product Owners and Developers with the Digital Product School

Every 4 months, about 8 teams comprised of University students, other students, and partner-company employees start working on a new product idea at the Digital Product School (DPS).

These teams become their own mini-startups, and work to develop, and sell their products in a 3-month accelerated program. They experience hands-on what it is to work in a start-up and to go from a fuzzy idea (the problem space) to a product they can sell in a very short period of time. 

This learn-by-doing program helps companies educate their employees in rapid product development methods, and helps students get hands-on experience with product development in a very short period of time. 

The most common problems teams face in DPS

The teams that join and complete DPS usually have the same problems all other teams face, but because of the accelerated time-frame, and because the DPS team has seen more than 10 batches already, the problems are obvious! And we can learn a lot from those problems when it comes to the more normal product development we participate in. 

The first challenge teams face is that they have a hard time locking down the problem they want to solve. As it happens, they want to solve too many problems, which is a common affliction of many teams and leads to confused and confusing products. 

The DPS team expected that it would be hard to convince developers to work with users and do user research. However, it turns out developers actually embrace that work, and the biggest problem is getting the Product Managers (PMs) to make decisions. PMs tend to expect that the “process” will ensure they have a good outcome, and that leads to having a hard time making decisions. 

In this segment, we talk about how to help PMs make decisions and the transformation that happens when PMs are faced with the need to make decisions. 

The biggest problem in the Developer-PM collaboration

In such an accelerated program (3 months from idea to product), it is natural that the pressure is high at some point. PM’s work needs to include facilitating and motivating the teamwork. Why are we doing certain decisions? What’s the goal of a certain user test? And many more questions come up during the work. 

This brings one of the biggest problems in the Developer-PM collaboration: the motivation of the team when under pressure. In this segment, we also talk about the most common anti-patterns developers and PMs fall into when under pressure. There are also some great insights for Scrum Masters about team building and coping with pressure!

Enabling good Developer-PM collaboration

One of the usual sticking points in the Developer-PM collaboration is the fact that these people speak different languages. Many Scrum Masters also experience that when they see PMs and developers fight about estimations, for example. 

At DPS, special attention is put into helping PMs understand what developers do and vice-versa. From explaining and using tools that developers use, to helping developers understand Story Maps and other PM tools, the way the DPS team helps developers and PM’s collaborate is especially about helping each other and learning each other’s job and responsibilities.

Why Product Manager and not Product Owner?

At DPS, the team decided early on to call the role of the product person the Product Manager, and not the Product Owner. Why did they do that? 

In this segment, we explore a question that most companies adopting Scrum will need to struggle with: what to call the product roles. 

The DPS team shares how the idea of “product” is owned by the whole team, and that the product manager role is much more than looking at the backlog or defining priorities, it’s about being responsible for user experience, business, and technology!

This emphasizes the idea of the DPS program: product development is a team sport! 

Resources for rapid product development

At the end of the episode, we talk about what resources DPS suggests teams to study, and we list the following books: 

About Digital Product School

DPS is an accelerated product development program in Munich that helps students from University and employees in partner companies experience hands-on what it is to work in a startup. In 3 months they go from idea to a product, and some ideas are brought back to the companies for further development. 

About the DPS team

Michi / Michael Stockerl is director of DPS and has worked as a software engineer with several teams in different setups. Before that, he gathered experience in smaller Startups in Munich and Germany’s biggest Q&A platform.

 

Steffen is a trained journalist, who slipped into product management through Content Management and e-commerce. He worked with Amazon and Haymarket media, did several hundred user interviews and tests, witnessed dozens of teams at DPS, a Digital Product School of the Technical University of Munich in Germany.

Bela is a Software Engineer at DPS. She helps teams with various software and hardware engineering tasks. She was previously also a participant at DPS. 

Jeffrey Koors: The full-stack Product Owner

The Product Owner role is not a simple one, so it is critical we help them understand the complete spectrum of topics the PO should be aware of. Even when the PO does not take care of all of those topics, they are critical in enabling the team by thinking about process, business and collaboration.

The Great Product Owner: The full-stack Product Owner

Product Owners that are able to manage their time to be present when the team needs them are sure to have a great contribution, but PO’s really excel when they are able to collaborate well with the team, and understand that reducing WIP, running-tested-software, and good communication with stakeholders are critical aspects of their role.

The Bad Product Owner: The PO that didn’t care about the details

When a Product Owner fails to discuss the details with the team, that leads to many possible misunderstandings and a deteriorating relationship between team and PO. In this segment, we talk about how to help PO’s go through the details enough so that the team feels confident they understand the story and are able to implement their vision.

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 Jeffrey Koors

Jeff started his studies and career as a fine artist and has gone on to use his creative thinking and vision to help many organizations find ways to design systems, solve problems and embrace Agile. Jeff is also the co-founder and host of Coaching Agile Journeys.

You can link with Jeffrey Koors on LinkedIn and connect with Jeffrey Koors on Twitter.

Charles Rodriguez: How to help the PO focus on value

In this episode, we talk about the PO’s role inside the team, and how we can help Product Owners focus on value.

The Great Product Owner: The PO who focuses on team success

The Product Owner in Scrum is a very difficult role, maybe even a super-human role. Unless we start thinking about the role as part of the success of the team, rather than the only responsible for the product. Great Product Owners focus on helping the team succeed, and learn to say “no” to everything that gets in the way, even if that’s a feature they “love”.

The Bad Product Owner: The PO that focuses on the “how” instead of the “why” 

When a PO focuses on the “how”, they miss their ability to communicate with the team in a way that describes what value is. The Value should be the center of the PO’s attention, but when the PO starts telling the team “how” something should be developed, they lose time outside the “value conversation”. In this episode, we explore ways to help the PO focus on, and define value for the team.

In this segment, we refer to an insight by David Hussman called “Dude’s Law” (Value = Why? / How?).

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 Charles Rodriguez

Charles has been working in software development for 16+ years with roles ranging from a database developer to manager to agile coach all in an effort to ‘try to make things better’ for future generations joining the IT industry.

You can link with Charles Rodriguez on LinkedIn and connect with Charles Rodriguez on Twitter.