January 2020
Intermediate to advanced
242 pages
6h 5m
English
Ever seen a bug backlog? Yep, some Scrum teams create a separate backlog just for bugs. How about a technical-debt backlog? This one is a favorite of Ryan’s from past coaching experiences: The Backlog of Broken Promises and Crushed Dreams, where every story we promised to deliver—but didn’t—went to die. Crazy right? Unfortunately, it’s not uncommon for Scrum teams to have multiple backlogs, especially on products that involve multiple Scrum teams.
When a product-development effort requires many development teams, the product owner often needs to delegate the task of refining the product backlog. In that situation, allocating each team their own separate product backlog might seem like the right thing to do. ...
Read now
Unlock full access