Measure your Test Maturity Index
1
25
  • Introduction
  • Knowledge Transfer
  • Test Planning
  • Test Design
  • Test Execution
  • Defect Management
  • General
  • Submit
  • Sample Test Maturity Report

Relevant for: CXOs, VPs, Directors of IT or Software Product Development, QA Managers

Brief History: Vasu Swaminathan, QA Head - Aspire Systems, along with his team have interacted with 550+ global IT organizations over the last few years to understand their QA related challenges and have addressed them through innovative techniques and solutions. Over years, Vasu has practically experienced the need of improvising the overall Test Maturity (in terms of principles, processes, people and platform) and reap the direct benefits of reduced defect leakage, minimized test cycle time and lower dependency on people.

This quest led to the obvious next steps of assessing the Test Maturity Index of our customers' QA organizations, coming up with meaningful metrics, measuring and analyzing the metrics over a period of time and gradually improvising them! To begin with, we use this form and so can you. (It takes about 15 minutes to complete this!)

Continue
1) What are the stages do your testers get involved?
Least Unstructured / AdHoc Structured
Requirements
Design
Development
UAT
2) What is the typical duration of training for a new team member?
Upto 2 weeks
2 to 4 weeks
More than 4 weeks
3) How are the team members educated?
Unstructured Induction (No process)
Structured Induction (Mentoring, Documentation)
4) What kind of Peer Review process do you follow?
No Process in place
Basic process though no formal
Formal process in place (inspection, team, walk through, pair)
Other
5) Do you have a requirements traceablity matrix in place?
Yes
No
6) What is the estimated functional coverage of your manual test cases?
50% to 60%
60% to 80%
80% to 100%
7) What is the count of your regression test cases?
< 5000
5000 < x < 10000
> 10000
8) How did your customers perceive the recent major release?
Very Happy - high user adaption
Moderately Happy - teething trouble
Unhappy - low user adaption
9) How frequently do major software releases happen?
Once a year
2 to 4 times an year
Very rarely
10) How many patches / minor releases happen per year
Less than 10
10 to 30
More than 30
11) Do you code freeze before QA release?
Yes
No
12) Do you assign priorities for test cases
Yes we do assign
No
Other
13) Is test data available with your test cases?
100% available
Mostly available
Not available
14) How frequently is your test suite reviewed & updated?
At the end of every release
On Need basis
Rarely
15) How frequently is your test data reviewed & updated?
Periodically
On Need basis
Rarely
16) Whats your general cycle time for testing your product?
2 to 4 weeks
4 to 8 weeks
9 to 12 weeks
more than 12 weeks
17) During critical releases where coverage compromises can happen, what strategy you adopt?
Risk based testing
No Specific Strategy
18) Can you indicate your testing lifecycle?
Smoke --> Functional --> Regression
Functional --> Regression
Others
19) What is the ratio of adhoc defects vs defects identified through structured testing?
20:80
40:60
80:20
20) Do you have a plan in place to handle your adhoc defects?
Mapped as testcases for next cycle
No specific action plan
21) Please let us know the life cycle followed in your organisation.
Waterfall Model
V Model
Agile
Please provide your contact details to receive the Test Maturity Index report

*
*
*
Back
Home | About Us | Why Aspire? | Contact Us
© 2011 Aspire Systems | Terms of Use