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.
User stories come in different shapes and sizes. Large stories, also called epics, allow quickly sketching product functionality, which is handy for scoping a major release. But it means that larger stories have to be eventually refined and broken down into smaller, detailed ones, which the development team can implement. This post shares some tips to help you systematically refine your user stories.
Many product backlogs are too long, detailed and complex. This is in stark contrast to what the product backlog should be: a simple artefact listing the outstanding work to bring the product to life. This blog post discusses lean techniques to make the backlog concise and focussed by avoiding variation and overburden.
Many product backlogs are too long, detailed and complex. This is in stark contrast to what the product backlog should be: a simple artefact listing the outstanding work to bring the product to life. This blog post discusses lean techniques to make the backlog concise and focussed by eliminating waste.
This blog post explores the notion of a product in Scrum. Being clear on what a product is a prerequisite for effective product innovation.
This blog posts explores four useful factors to prioritise the product backlog: value; risk and uncertainty; releasability; and dependencies.
The product backlog is meant to be a simple tool that allows product owners to express detailed product decisions and direct the work of the development team. But in practice, product backlogs can grow big and become large and unwieldy. Break up your product backlog can address this issue, as this article explains.
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 discovery, exploring the value proposition, market, differentiators, business goals, and business model of a new or updated product, is crucial to achieve success. But getting the product out as quickly as possible is often equally important. In this post, I explore the question how much product discovery is required and how to best balance the necessary discovery work with reducing time to market.