...
- The distribution of work by size (assuming that the team is using estimation technique like story points)
- For work that is in a column about to be worked on (e.g. analysis or 'candidate stories') the team can quickly see which issues are too big and need to be sliced down
Setting up the chart
- Filter the data by the current version (release) if you want to focus on identifying work to be sliced down
- Select historical versions or sprints, if you want to see the distribution of sizes that have already gone across the board - which might help in estimating effort in the remaining backlog.