Find out when it’s the right point in time to groom your product backlog: Before or after more development work is carried out.

Discover five essential steps that will ensure that your product backlog facilitates innovation and drives the work of the development team.

This posts discusses a user-centric, iterative, and collaborative design process for Kanban and Scrum teams.

Using the product backlog can be challenging, and many product owners wrestle with overly long and detailed backlogs. This blog post provides ten tips that help you work with your product backlog effectively.

High-priority product backlog items must be ready to be transformed into working software. Find out what does “ready” means and benefit from Yoda’s advice.
.

This post provides a concise overview of the product owner role.

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 posts explores four useful factors to prioritize the product backlog: value; risk and uncertainty; releasability; and dependencies.

Learn when it is time to break up your product backlog.

Find out why product owners should care about software quality and what they can do to help get it right.

This blog post covers the essential grooming aspects to ensure that your product backlog contains the right items and is ready for the next development cycle.
