…use in an engaging retrospective
Use playback to show the team what was happening during the last iteration or sprint. Pause in interesting moments to discuss.
Use liquidity graph to analyse performance of the team. Generally, the higher the average liquidity the better as this means, that work was not stuck in any particular stage and issues kept progressing in the workflow.
…find bottlenecks in your process
Use Cumulative Flow Diagram (CFD) to find bottlenecks and other problems in your workflow and process. For an in-depth analysis of what CFD chart can show, check this article by Pawel Brodzinski.
Navigate to an interesting point in time using timeline. The board above will show which issues were in that status at that time. Depending on what these issues were and how often this particular status in your workflow gets too busy, you can adjust your process (for example increase number of people that can work on that area).
Note, that you can configure columns on the board to contain more than one status. This would allow you to merge all related statuses (for example ‘back end development’, ‘front end development’, ‘code review’) into one column to make it easier to spot bottlenecks.