October 2009
Intermediate to advanced
504 pages
15h 39m
English
There’s a reason it’s not called a “project backlog” or a “team backlog” or any other similar but deficient term. It’s called a product backlog because there should be one per product. If a team is working from more than one product backlog, the multiple backlogs must be prioritized against one another. It is not enough to prioritize each product backlog and tell the team to take the top five items off of each. The top item on one product backlog might be lower priority than the lowest item on another product backlog.
As an example, consider successful Scrum adopter Ultimate Software of Weston, Florida. Ultimate Software develops Software as a Service (SaaS) for human capital management. This includes features ...
Read now
Unlock full access