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 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.
Software quality is often perceived as something the nerds should worry about. But it can significantly impact customer satisfaction and brand value; the total cost of ownership and life expectancy of your product; and the product’s competitiveness. This post explains what product owners can do to help their development teams get quality right.
Business analysts play an important role: Traditionally, they act as the link between the business units and IT, help to discover the user needs and the solution to address them, and specify requirements. But in Scrum, there is no business analyst role. So what happens to the individuals?
Product backlog grooming or refinement plays an important part of creating and updating a product in an agile context. Done correctly, it helps you develop a successful product, a product that benefits the customers and users and the organisation developing it. This post provides my tips on grooming the product backlog. It answers questions I often get asked by product owners: Why is grooming important? What does grooming entail? Who should carry it out? When should grooming take place? Which tools and techniques are helpful? Where should the initial backlog be derived from? And how much grooming effort is required?
The product backlog is intended to be a simple tool. But in reality, product backlogs are often too long, too detailed, and difficult to use. This post explains how you can avoid this common trap by making your backlog DEEP: Detailed appropriately, estimated, emergent, and prioritised.