about training consulting publications talks blog
Roman Pichler – Pichler Consulting Limited

All Things Product Owner

Archive for the ‘Product Backlog’ Category

The Product Backlog as a Learning Tool

Jan
12

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.

spacing rule

The Product Backlog Board

Mar
07

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.

spacing rule

Roman’s Top Ten Product Backlog Tips

Feb
08

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.

spacing rule

The Definition of Ready

Dec
16

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
.

spacing rule

Prioritising the Product Backlog

Jun
18

This blog posts explores four useful factors to prioritize the product backlog: value; risk and uncertainty; releasability; and dependencies.

spacing rule

When to Break up your Product Backlog

Jun
11

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

spacing rule

Grooming the Product Backlog

Feb
15

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.

spacing rule

Making the Product Backlog DEEP

Feb
08

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.

spacing rule