QA Velocity

I keep hearing this term through out the day and wonder if there is anything called QA velocity. How we measure QA velocity? Is it just by the number of points signed off by QA team in an iteration or averaged over few iterations. Or is it more of a expectation setting? Just to inform that QA team doesn’t act as a barrier. Testing and Development are no separate process.
Generally the QA team is involved in a series of activity like writing test scenarios, preparing test data, doing dev box testing, build deployment, system testing, integration testing, exploratory testing, bug filing and regressing. As the number of activities increases it introduces a potential barrier too with itself. Some of the potential barriers are unstable build, lack of preparation while doing dev box testing, finding bugs in the later phase of testing, improper bug filing. All these things potential acts like a barrier or halt in signing off a story. Some of these issues should be addressed as a part of QA training and some by being smart and showing a little diligence. Sign-offs are not purposefully delayed, neither keeping a story in “In-QA” state for longer time instils in me a sense of confidence. Testers job is to make sure that the story is working properly along with the existing functionalities. Stories are of varied nature and so is there complexity and test estimate. These things cannot be averaged out. More over points are relative numbers and can be misleading at times.
A card wall has different phases or stages of a delivery cycle (like In-Analysis, Ready for Dev, In Dev etc..), which eases the process of managing an iteration. Effort should be made at correcting the problems and maintaining a constant flow rather than throughput of a specific stage like QA Velocity.


Popular posts from this blog

The 3 qualities that will always help you become better at almost anything…

Test Case Paths : Happy, Sad & Bad

How to install Android Emulator on Windows