In this episode, we explore some of the critical lessons Jeff learned in his own career as a Product Owner. We review the missing aspects in most Product Owner role implementations and discuss the tools that have helped Jeff as a Product Owner first, and later his students.
The first steps of Jeff’s journey as a Product Owner
Read on for the detailed show notes, and all the links
As part of our “Coach Your Product Owner” course, we’ve been hard at work creating simple and actionable tools you can use to help your Product Owner progress. But that coaching cannot happen unless we tackle the biggest problems we have when coaching Product Owners. So, last week I asked people who receive my Newsletter to help me answer this question:
When it comes to Coaching and Supporting your Product Owner(s), what is the single Biggest Challenge that you are facing right now?
The reason for this question is my belief that, as Scrum Masters and Agile Coaches, we must help the Product Owners as part of our duties. Sometimes those duties may be just about helping them manage/facilitate a particular session, but often we need to help the Product Owner grow their skills, knowledge, and experience with Agile product development. All aspects of it.
So what are the key challenges we face, when coaching and supporting our Product Owners?
Would you want to have a simple, collected, set of solutions (techniques and strategies) to solve the most common challenges Product Owners face? So would I! But before we can collect the solutions, we must understand the problem!
That’s what I did in 2018.
I asked the listeners of the Scrum Master Toolbox Podcast and the readers of the blog what were their most common challenges when working with Product Owners. So, if you are a Scrum Master, an Agile Coach or a team member who wants to help the Product Owner, the list below is for you! (NOTE: there are links to solutions as well! ?)
As Scrum Masters we don’t just work with the team, we also work directly with the Product Owners that support the team. In this story, Paulo shares the case of the Product Owner that had a Business Analysis background and thought the job was about writing specifications in isolation. Listen in to learn how Paulo handled that and helped the Product Owner transition to User Stories and more team interaction.
Featured Book of the Week: Management 3.0 by Jurgen Appelo
In Management 3.0 by Jurgen Appelo, Paulo found a management model that better suited his goal to become a Scrum Master. By reading this book he learned about how he could become a better servant leader. A key aspect of the Scrum Master role.
About Paulo Rebelo
Paulo Rebelo helps companies to improve using agile and lean principles like Scrum, XP, and Kanban. He currently works at Blackhawk Network in the U.S., helping teams succeed by building great products. His background is a developer, Scrum Master, product owner, project manager, and coach. Paulo is a CSP, CSPO and a CSM from the Scrum Alliance and PMP from the PMI.
Many things can fail when we work with teams. But one critical anti-pattern that leads to problems is the lack of a good Product Owner. In this episode, we explore what are the consequences for our teams of having a Product Owner that is unable to filter input from many stakeholders or even to politely say “No!”. Listen in to learn about the many anti-patterns that can come from a poor Product Owner.
Featured Book of the Week: any book by Gerry Weinberg
What happens when the Product Owner and the team can’t collaborate? When the team just takes orders from the Product Owner and stops contributing to the planning and content of the User Stories? This was the situation that Peter had to face. Listen in to learn how he tackled this relationship problem.
Featured Book of the Week: Search Inside Yourself by Chade-Meng Tan
In this book, Peter found an approach that helps him as a Scrum Master. In Search Inside Yourself, Chade-Meng tries to offers a method for enhancing mindfulness and emotional intelligence in life and work.
About Peter Zylka
Peter is a freelancing Scrum Master who really loves what he does.
Peter is passionate about Agility and loves supporting teams and organizations on their way into the agile world. As a Scrum Master his goal is to enable each individual in the team to perform the best possible way and to actually understand what a team really is all about.
He starts every day with the goal to make the people around him better.
We often work within environments where the “vanilla” Agile approaches are insufficient. In this episode we explore what happens when more traditional organizations are adopting Agile. We talk about the role of the Product Owner in traditional organizations and the critical role that the Scrum Master plays in supporting the Product Owner.
In this episode we discuss the importance of Pilot projects in traditional organizations and what we can do to make sure they succeed.
About Darryl Sherborne
Darryl is an IT professional specialising in Kaizen (continuous improvement), Agile delivery and coaching, Lean Thinking implementations and more recently applications of DevOps and Data Science. Darryl can also be found singing in rock/pop choirs, and watching or reading anything in the realm of Sci-Fi / Marvel.
EXTRA BONUS: to get 30% off Barry’s Hypothesis-Driven Development course you can go to www.leanagile.study and use discount code THIRTYCPOFF before the end of December 2017.
Far too many companies act as if Product Development was a shopping trip: they get a list of things to “buy”, typically Features. Then they create documents explaining that shopping list: Roadmaps, Backlogs, PowerPoint presentations, Post-its on walls, you name it. And then they execute. Here’s the thing: if you act as if Product Development is a shopping trip all you will do is spend a lot of money and get lots of Features you don’t really need.
Barry suggests we treat Product Development differently. He calls it Hypothesis-Driven Development (HDD for short) and includes:
Leadership set an outcome (not a task!) Example: how to increase conversion by 10%
Look for observations: where you try to understand what is happening in the product and to the product you develop.
Set a hypothesis to validate ideas: where you make assumptions and write those down as assumptions. Assumptions should be about how to reach the goal set in step 1.
Create simple experiments: actions that drive results, which you will compare with the hypothesis you created in 3.
Gather the data, learn and repeat: the core process is LEARNING. Therefore, spend enough time on this step so that you generate new observations, insights. Then repeat the cycle.
A fundamental shift in product development
Barry claims that HDD is a fundamental shift in product development. The shift is from doing many things, many small changes, and switches to focusing on outcomes, on results to the business. This means that leadership is no longer accountable for the work, but for the outcomes. And this frees the teams to focus on self-organizing to reach those outcomes, instead of following a list of things that others have dictated.
As a result of the shift towards HDD, we stop focusing on big-bang, all-in projects and focus on running smaller experiments that drive the learning that will eventually generate the outcomes we defined. As Barry says in this episode: we go from 1 to 2 experiments per year (projects) to testing many more ideas every month.
But you can’t run that many experiments with the same approach to funding, and management that you used when you ran projects. So we focus on a different management paradigm that Barry explains further. The goal: learn and adapt faster, not produce more features.
As part of that, we need to get familiar with the concept of safe-to-fail experiments that can reliably generate knowledge without causing chaos or confusion in our product development process.
And it all starts with a simple change in product development: define the problem you are trying to fix, not the solution you are trying to create.
If I want to know more about the Hypothesis-Driven Development approach, where should I start?
Barry O’Reilly is a business advisor, entrepreneur, and author who has pioneered the intersection of business model innovation, product development, organizational design, and culture transformation.
Barry works with business leaders and teams from global organizations that seek to invent the future, not fear it. Every day, Barry works with many of the world’s leading companies to break the vicious cycles that spiral businesses toward death by enabling experimentation and learning to unlock the insights required for better decision making and higher performance and results.