Ordering what to build.
WHAT IT IS
An ordered list of everything wanted, with the most important first.
WHAT ORDERED MEANS
A single sequence, not priority categories.
WHY
Everything marked high priority conveys nothing.
WHAT TO ORDER BY
Value Risk Dependencies Cost
WHO DECIDES
One person, accountable for the product.
WHY ONE
Decisions by committee produce compromise sequences nobody agrees with.
WHAT REFINEMENT IS
Preparing upcoming items: clarifying, splitting, estimating.
WHAT TO KEEP READY
Enough understood work for the next iteration or two.
WHAT NOT TO DO
Refine the whole backlog in detail.
WHY
Most of it will change or never be built.
WHAT TO DO WITH ITEMS UNTOUCHED FOR A LONG TIME
Delete them.
WHY
If it has not been prioritised in a year, it will not be, and it clutters the list.
WHAT TO REVIEW REGULARLY
The order, as circumstances change.
WHAT TO MAKE VISIBLE
What is coming next, so the team and stakeholders agree.
