Useful charts for a Kanban system shows how to read a Kanban cumulative flow chart. I am wondering what patterns stand out on a Scrum cumulative flow burnup? I've seen two patterns frequently: the hockey stick and the bottleneck. What other problem behavior can show up in a flow burnup, and what can be done to correct it? Also, what intermediate states may be fruitfully charted other than In Development and In Testing?
This example uses mock data; see How can we avoid finishing all stories on the last day of a sprint? for a real-life example and some great discussion.
See Best strategies for dealing with integration testing bottlenecks? and How to better balance resources in a cross-functional agile team? for some discussion relative to bottlenecks.