When a product grows and becomes a success, so will the demands on the Product Owner.
There will be more stakeholders interested in the product, which leads to more meetings. The number of teams developing the product will grow, which will increase the number of meetings and daily questions to the Product Owner.
The more successful the product becomes, the harder it is to manage that product with one single Product Owner.
It is no surprise that most successful products seem to be constantly affected by the lack of time on the part of the PO. However, that’s not the only cause for a PO to be pressed for time. In smaller companies that are adding products to their offering, we often need to start working on a new service or product before a new PO can be hired. On top of that, the knowledge that is already in the PO’s head will be hard to transfer to a new PO, so hiring more Product Owners may even be the wrong thing to do.
Read on for more details and the full article download.
Why do we have daily meetings? Why do I need to be involved with the team every day? Why can’t I just give you the requirements document and concentrate on other tasks?
This blog is part of Module 2 of the Coach your Product Onwer v2.0 video course.
The Anti-Patterns When A Product Owner Is New To The Team, The Product And To Scrum
These are just some of the questions that Product Owners that are new to Scrum will ask. But sometimes we need to onboard Product Owners that are new to Scrum, new to the Product and new to the team. That’s not an easy task.
The Product Owner may not have any technical knowledge of the product or the understanding of the business the product supports. When a Product Owner is new to the team, and the collaboration habits have not yet developed. For example, he may be tempted to just go away and write all the User Stories in isolation or with a Business Analyst, and never involve the team. Which later leads to the “tell the team what to do, and disappear” anti-pattern. Continue reading Product Goal-Setting: How Scrum Masters can onboard a new or beginner Product Owner
The overly busy or absent Product Owner is a common anti-pattern in agile organizations.
This can have serious consequences for the teams we work with as Scrum Masters.
Additionally, Product Owners that are spread too thin may not even have time to be in the Scrum meetings because they serve many teams or handle several products, or because they have so many other meetings with C-level, or other stakeholders. Missing critical Scrum meetings (e.g. Sprint Review, Sprint Planning, Grooming) will quickly lead to a de-motivated team, as well as lack of trust and potential conflict between the team and the Product Owner. In my own experience, when the Product Owner starts missing critical Scrum meetings, the team will quickly start asking: “why do we even do these meetings”, which quickly leads to the meetings being dropped.
How do we help our Product Owners overcome these challenges? Read on…
The Product Owner (PO) is a tough role to fill. Product Owners are torn between users, senior management, team and other stakeholders that they need to attend to.
While the team is working on completing the backlog items, the PO is probably meeting with the Director of Product to agree on a roadmap; with the CEO to hear about the latest ideas he got from visiting a client; trying to meet with the user research group to understand better the customer; reporting status to the head of Project Management; and still needs to visit the Sprint Planning, Backlog Grooming, Demo and the occasional daily meeting to answer questions from the team. And let’s not forget the email backlog! With all of these tasks one has to ask: do we believe a single person can do this all alone? What I describe here is not even rare! We seem to collectively think that the Product Owner is a super-hero!
Given all of these tasks, it is little wonder that the PO’s end up struggling to even manage the JIRA tickets the teams ask them to review, give feedback on, and prioritize.
Before reading the post, I wanted to share with you a great interview about how we, as Scrum Masters are always starting from Scratch (just like new year! 🙂 Here’s a Podcast episode as a new year gift from the Scrum Master Toolbox Podcast archive built over the last 3 years interviewing Scrum Masters from all over the world.
Podcast Topic: We start a new with every team (interview with Lucian Stroie)
Now for the list! 🙂
Here in the Scrum Master Toolbox Podcast, we share insights and inspiring stories from Scrum Masters every day of the week because we believe we need inspiration and ideas every day. Therefore we also visit sites and blogs for the same reasons. To end the year with a bang, I wanted to create a list of Top blogs / Sites for Scrum Masters. Was I in for a disappointment… read on to know why…
Product Owners have an impossible job! I know, I’ve been a Product Owner. And even worse, a Product Manager transitioning to Product Owner! And even worse! I was also the Project Manager. Geeez! When I look back I am amazed I survived that phase of my career.
Here’s the kicker, that was the best time of my Agile adoption journey. I got to see my ideas come to life so quickly! And have a concrete business impact (the product we delivered went on to generate 10 Million Eur in sales a little over 3 years).
My Product Owner journey towards Agile was not easy! Let me tell you how I survived that stressful time, and lived on to learn a lot from the experience.
Retrospectives are one of the key ceremonies for teams. Well prepared and executed retrospectives can take a team from ordinary to extraordinary and can help teams avoid the anti-patterns that so often lead to difficult problems down the line.
One of the resources that Jiri uses when preparing his retrospectives is Getting Value out of Agile Retrospectives.
The Product Owner role can enable to make the work of the team very difficult. In this episode Jiri talks about how important the Product Owner role really is and how to help teams align. We also talk about aligning remote teams discussing some of the techniques that Jiri uses to have remote teams collaborate effectively.
Scrum has a foundational story that many of us know. The Pig and the Chicken story. Through that story we learn that in Scrum there are “insiders” (the Pigs, who are committed), and outsiders (the Chickens, who are merely involved). The role of the Product Owner is often looked at as a “chicken”, however Angel relates a different perspective. He talks about the critical role of the Product Owner in a Scrum team as well as the approach he used to bring the Product Owner role back into the team.
About Angel Diaz-Maroto
Angel is a seasoned and very energetic Agile coach and a frequent speaker at international conferences and Agile events in Europe and America. He is Certified Scrum Coach. Currently he is member of Agilar, one of the leading Agile coaching firms in Europe and Latin-America.
He is now at Agilar, but before he was the leader at one of the biggest Agile transformations in europe, including business and IT at the Spanish branch of a multinational bank (ING). He lead the transformation from the trenches and starting from scratch. He as more than 15 years of experience in many different roles and is a professor at ESNE (University School of design, innovation & technology).
You can link up with Angel Diaz-Maroto on LinkedIn and connect with Angel Diaz-Maroto on Twitter.