This post includes the discussion around combining the roles of scrum master and product owner.
Developing and delivering products which customers don’t want and for which there is no market can be costly. Agile can help you to efficiently develop products, but you need to know what to build. How can you find out which products your customers need?
Roman Pichler shared his views on product owner’s participation in sprint retrospective to increase collaboration with development team.
Many teams use the Definition of Done to check if a user story is finished and the product is ready to be delivered. But what about the user stories that a team receives from their product owner? Teams can check the quality of the user stories using a Definition of Ready.
Estimations are used by agile teams and product owners for prioritizing work and to plan releases of products. They can be done on different levels and in various ways.
Would better user stories improve software delivery? Gojko Adzic thinks applying small changes to the way teams manage their user stories can have a huge impact on the actual outcomes of their software delivery. He announced that he wants to write a book about improving user stories if at least 5000 people show that they are interested by pre-registering themselves in January.
The product owner role from Scrum is used to interface between the business and development. In larger organization with complex products and many decisions that need to be made, having this role filled in by one person is often not feasible. InfoQ did an interview with Timo Punkka about the role of the product owner, lean portfolio management, and customer collaboration.
The purpose of backlog grooming is to keep the product backlog up to date and clean. Different approaches are used by product owners and teams to do this.
Agile teams sometimes struggle with the planning of pure technical tasks that have no direct value for the user of a system, but have to be done to deliver working software. Should you create user stories to handle such technical tasks and technical debt, or not?
Henrik Kniberg has developed “a 1 day product ownership course compressed into a 15 minute animated presentation”. Based upon this video and some other on-line resources about the product owner role, collaboration between product owners and teams is examined.
A new "Scrum Kickoff Planner" has just been released by Adam Weisbart with the aim of facilitating team discussion around the important facets of starting a new Agile team or project.
A product backlog left unattended can become large and unmaintainable. The common approach of reviewing and updating the backlog regularly might be ineffective in the longer term, demanding alternatives to backlog grooming.
The Product Owner role is regularly debated and discussed. The challenges of the role and the responsabilities encompased by it are a frequent source of discussion and advice. Recently there has been discussion about common aspects of the role and the important activities a product owner needs to ensure happen on an agile project, and the difference between the product owner and product manager
What are the advantages and disadvantages of having the same person fill both the Product Owner and the ScrumMaster role on the same Scrum project? Is this really a workable option?
Scrum works most effectively with a prioritized product backlog. Prioritizing the backlog is part of the product owner role, but what can you do when your product owner won't prioritize the backlog because he or she doesn't see the value in prioritization?