A topic we hear a lot during our talks with other QA organizations is around translating our QA Managers experience and intuition into metrics that help us communicate with our external managers and peers.
Specifically how to communicate when our sprints are actually ready to release or on the flip side, if we are getting close to release date, but we are not close to releasing the product.
We track stories, tests, bugs, coverage, and many other things. But these usually live in separate reports, and the final analysis still is based too much on gut feeling.
We sat with our Product Team in PractiTest, and after analyzing thousands of releases and speaking with hundreds of organizations, we created the Release Readiness Index.
The idea is simple: bring the relevant signals together and show how release readiness is evolving throughout the sprint, not only when it is time to make the final decision.
If this is a challenge your team is dealing with, take a look. I’d be interested to hear how you currently decide when you are ready to release.