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, one-page overview of the product owner role.
User stories are probably the most popular agile requirements description technique. It’s comparatively easy to write, decompose, and refine user stories. But writing good stories can be hard. This blog post helps you tell great stories.
This blog posts discusses techniques to progressively decompose use 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 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 if user stories or use cases are more appropriate to capture product backlog items.
Find out why product owners should care about software quality and what they can do to help get it right.
This blog post discusses the role of business analysts on Scrum projects.
Like a garden growing wild when left unattended for too long, the product backlog becomes unwieldy when it’s neglected. This blog post covers the essential grooming steps to ensure that your product backlog contains the right items and is ready for the next sprint planning meeting.
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.
RSS