Product Backlogs are actually prioritised not ordered.
The change of Product Backlog from prioritised to ordered is actually an error. Priority means "the fact or condition of being regarded or treated as more important than others."
This is what we do with PBs. Whether because of risk, or value, or technology - We always work on the most important first.
Ordered just means "has an order" - In that way we could use scrum and legitimately work on the meaningless nice to haves rather than the key aspects of the product.
This also over empowers the PO role as it means they can decide in totality without interference an order of any type without any reason, where the priority rule in Scrum can help them not commit product suicide by mistake.
It also allows bad practice such as up front design, testing at the end by not encouraging a focus on the most important aspects of the delivery.
Short version. Prioritised does not contain an element of "only ordering by value" that was the original reason for the change. Ordered is weaker than prioritised, and can lead to malformed Scrum and/or bad PO practice. This is a small gap that inappropriate coaches and techniques such as SAFe can use to create poor scrum implementations.
1 commentComments are closed
I am not anonymous! This is Nigel Baker, Agile Coach, and certified trainer.