Hi Steve and Tameflow-owers
I’m a Scrum Master who experiments with data to help the team improve its performance. Lately, in one of my teams, we have started experimenting on ways how we can increase our velocity by better planning our sprint work.
We started analysing cycle time, we started following the ageing chart, and try to sprint through the waiting states.
First sprint with experiment gave us immediate results, and we were extremely motivated.
Second sprint we got stuck! One of our stories was “too big”, we ended up with loads of stories waiting to be tested, and this remaining in progress.
My question is - is it wrong to do such analysis to increase velocity? Is velocity a push factor, which makes us “cost driven” rather than “throughput driven”?