This post discusses the strengths and limitations of a traditional product backlog, when to use it, and when to choose a different tool.
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.
Leverage the power of customer feedback, and use your product backlog as a learning tool. Discover the right product features and take advantage of emerging requirements by integrating customer a feedback into the backlog early and frequently.
Are you struggling with your product backlog? Then try Roman’s Product Backlog Board, a structured hierarchical product backlog that helps make sure you have ready items, capture non-functional requirements, and integrate your requirement models.
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 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.
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.
The product backlog is intended to be a beautifully simple tool. But real-world product backlogs are all too often too long and too detailed making them difficult to use. This blog post explains how you can avoid this common trap by ensuring that your product backlog is DEEP: Detailed appropriately, estimated, emergent, and prioritized.