Every Product Owner is different. Every Product Owner needs to work out what is right the right way for them to fill the Product Owner role. Every organization is different. Every team is different, and every individual is different.
There are many examples of fake Product Owners (PO) in the companies (PO as Business Analyst, PO as Project Manager, Proxy PO). Companies cause this by using many organisational design antipatterns (assign one PO per team, “Product” being in fact a component, using committee for product decisions instead of one person).
Does Scrum ask too much of product owners? Is the role set up to fail? In this presentation, Allan Kelly looks at some of the problems Product Owners face… and tries to make some useful suggestions.
The Product Backlog Refinement (PBR) activity is one that many new Scrum teams struggle with. Insufficient PBR often results in long sprint planning meetings and incomplete backlog items at the end of the sprint. This article provides some tips on how to improve backlog refinement, which in the past was called backlog grooming.
The Minimum Viable Product (MVP) is an approach that aims to avoid building products that customers don’t need or want by maximizing your learning about what is valuable for them. In this article, Sergej Hermoni shares seven reasons why you should include building an MVP in your Agile approach.
Do you have a nagging feeling that your Scrum team may not be investing in building the right thing? Do your products have features that are rarely or never used? Does it take your organization the full investment of building and launching a product to validate an idea?
There is often a vacuum between the company vision and the final outcome of software development projects, causing late validation and low value. This vacuum is present in pretty much all companies, caused by a wrong and ill-conceived product delivery approach.
Scrum Expert Copyright © 2009-2023 Martinig & Associates