Recently I had an interesting call with a senior QA leader. He reached out to me He wanted to get a better sense of how his people are doing, both as a functional unit and individually. Primarily, I suspect he wanted to be proactive, and have some kind of a numerical early warning system in place, which he could cross-reference with common sense and qualitative input he got elsewhere.
As we spoke, he kept using the term “velocity” initially; however, it became clear that he meant velocity in a much looser sense than the typical iterative scrum/agile sense. It doesn’t really work for what he wanted to achieve.
Here’s what I mean: