With an eye on maximizing the flow of value using Smaller Backlog Items, priorities are determined using Cost of Delay evaluations to identify what work should be sequenced early/first. In addition, the sequence of work is influenced by understanding where there is need to reduce risk, orchestrate across or around dependencies, and leverage solution options.
While continuing to focus on Predictability in the release cadence and throughput, the intent is to “stack the backlog” with the work that is most valuable to meeting business outcomes (whereas, in Basecamp 1, throughput may have been “predictable,” the focus in Basecamp 2 is “predictable with the right priorities”).
We often teach forms of Cost of Delay to convert these business concerns into a priority score. However, the team must adopt a problem-centric approach and leverage options to ‘hedge bets’ against solving the problem. In this way, teams can be aware of the risk that their efforts don’t solve the customer or market problem. Risk management is integral to strategizing how we play these options to be in the best position to solving the problem.
Forced-Rank Prioritization of the Backlog is determined using objective value determination
“Trim the Tail” on Features and Epics to maximize value, address risk, but focus on the most valuable need
Teams are capturing and managing risks to “burn down” risks as early as possible