The product owner is a product management role that emerged in Scrum in the late 1990ies. But many organisations still struggle to effectively apply it. In this article, I offer an overview of the role including its authority and responsibility.
It’s not uncommon for me to visit a new client and discover that the agile development teams frequently change, sometimes after every single sprint. Changing the team composition too frequently is usually undesirable, though. Teams need stability to flourish and realise their full potential. This post provides practical tips to help you create stable agile teams.
This blog posts explores four useful factors to prioritise the product backlog: value; risk and uncertainty; releasability; and dependencies.
User stories and use cases are both powerful techniques to capture requirements. But which one is right for you? This post shares my recommendations.
Product backlog refinement, or grooming, plays an important part in delivering a product. Done correctly, it increases the chances of offering a successful product. This article shares my tips to help you effectively refine your product backlog.
The product owner role in Scrum has attracted plenty of interest and controversy. Some people believe it rebrands the traditional product manager. Others think it is a team lead or Scrum’s take on the project manager role. And some say the product owner is a helper role, a product backlog item writer so to speak. None of theses views is true. But each has some truth in it. This post attempts to demystify this important role.