A PO has many responsibilities, too many to mention them all here. I will focus on the three that are in my view the most important.
The text is very much an answer to the question “Why is the Product Owner needed?” or “Why is the Product Owner important?”. However, much of what I write below is also valid for project leaders or team leads within product development - even if those teams are not working with Scrum or other agile methods.
Now that the intense part of the corona pandemic is over (fingers crossed), companies and teams are transitioning to a permanent new normal, and figuring out how to do so. Thus, now is a good time to write down some thoughts on how to deal with the effects of remote work, specifically on company culture.
I recently wrote about the benefits of doing one thing at a time and the downsides of Multitasking. While listing things that can be done to facilitate doing one thing after another for a team, I completely missed to mention maybe the most important factor: having a dedicated team.
We want to satisfy stakeholder requests, regardless if that means saying yes to a new feature or if it means to answer an e-mail. It's hard to say no. It makes us feel good to always answer, it makes us feel like we get a lot of stuff done. Spoiler alert: we actually don't get a lot done and productivity suffers.
Trying out elements of agile in non-software development with a set-up that is not according to the book might be controversial. However, applying the principles can have some real benefits if this is done mindfully.
Let me tell you something. It can be really liberating, to say the three words "I don't know". As soon as you have done it a few times you will find that it turns out to be very easy and that it brings some real benefits.
they all have important wishes and ideas on how to improve the product. However, product development is always constrained by capacity and available time. Thus, the PO has to rigorously prioritize and frequently deny requests.
Besides the retrospective, the backlog refinement (sometimes called grooming) is in my view the most important ceremony within the scrum framework. One could even argue that it is the most important one. It certainly has an outsized positive impact on team productivity, created value, and team chemistry - if done correctly.
Oh boy, what a topic this is going to be. Everybody seems to hate them. Yet, they somehow can´t be avoided. So much has been written about them but we still seem to struggle on how to deal with them, meetings.