"We have a GA date approaching. PPM calls a Projet-Team meeting and takes a vote of confidence, which decides the fate of the software!!"
"A P1 bug is not a show-stopper if it already exists in production. The release will not degrade the production quality!!"
"QA gives a conditional GO with list of risks. By the time decision propogates to executives, the attachment is dropped and the Conditional-Go turns into a Sure-shot-Go!!"
"PM: The problem is not in our piece of the code. The issue is because of the other component that we are dependent on!!"
Sounds Familiar? Interesting, isn't it?
Let's face it, we need sophisticated tools that can generate real time metrics for anyone to make informative decisions. People often mix product quality with process quality. Even though a high quality process generates a high qualiy product (TQM principle), I believe the metrics for the two should be different. For example, higher percentage of test automation improves QA process quality and doesn't directly improve underlying product quality! Note: the automation of processes in the early ALM cycle would have a more direct impact on the product quality.
Here are the list of questions, that metrics should be able to answer:
- Q1. What is the overall Quality Index (QI) of the product. QI for a particular feature or requirements? What is the QI of different components?
- Consistency of the processes and measures is the key here.
- It is easy to fabricate a QI model that concentrates on intrinsic product quality!
- Q2. What's our Release Readiness? What's the risk if we release our product today?
- Q3. What's the QI trend for differenet releases and different builds?
- Trend is more important than actual QI snapshot.
- Errors in the QI (if any) cancel out when you read trends
- Q4. What's the Dependency Matrix (DM)? How does other SOA components impact my product? How does my product impact other offerings in the organization?
- Current snapshot from QI perspective
- Roadmap overlap for future releases. Cross-project Backlog Management.
- Q5. What's the realtime Coverage graphs?
- Test Coverage (test validating requirements)
- Code Coverage (tests validating code)
- Q6. Testing Strategy Automation.
- When files A, B and C change, which features get impacted. What test cases and configurations should a test lead plan for next build?
- Q7. Process Quality. How productive is my team?
- Measures of test automation.
- Comparisons with baseline (and manual testing)
- We are ready for the release!! Our product QI crossed 85% in the last build.
- Because of TTM (time to market) pressures, we have decided to release our product with 65% QI. To mitigate the risk, we have also decided to increase our customer support resources.
- Our product is not ready for GA because we have a dependency on products B, C and D, and product B has a QI of only 30%. Since B is tightly coupled with our core, we are not in a position to release our product.
- I can effecively utilized my QA resources to concentrate on only the impacted features in a build. We don't have to regress every build every time. We can validate a build with handfull of fixes in less than two hours, and that too with over 95% confidence!!
- We can now sell SLAs and QLAs around certan metrics because we have a consistent (and automated) way of capturing them.
- I can trace a customer escalation all the way back to requirements, because we have end-to-end integration of ALM tools with excellent search facilities.