Now Try This

1. Select a ranking approach aside from Shortest Work First. I’ll discuss estimation in Chapter 10, ​Agile Estimation: The Good, The Bad, and The Ugly​. Too often, the team can’t tell which story is shortest, so it’s a good idea to try other ranking approaches.
2. Try that ranking method either for an iteration or as the product owner updates a board. Discuss the ranking in the retrospective to see if the team thought it had delivered the highest-value work.
3. Articulate the value of the work under discussion. Sometimes the value changes over time. Sometimes the value is about quick learning. The more everyone can bring the discussion back to value, the easier it will be to rank the work.

Now that you know how to rank the work for the team, it’s time to show the team members their ranked work. That’s the point of the board—to help the team to visualize its work.