Enterprise testing is no longer an afterthought. According to SQE Magazine, Enterprise Testing alone can take up more than 34% of the budget for any large implementation.
How well is your quality and testing organization doing? How can you measure its effectiveness? If you aren’t able to answer these questions, your testing organization might not be operating as efficiently as it could be. We’re all familiar with the results of poor testing on implementation projects; go-live dates that keep getting moved to the right or on-time delivery with half-baked functionality. With a proper assessment of your testing processes you can know what your chances are of making that go-live date with acceptable quality. You’ll also know how well changes were tested before being introduced into your production environment. Enterprise testing is becoming increasingly important in payer environments. IT systems are vital to everyday operations. Gaining control over all environments is essential to drive down costs and decrease problems that affect all aspects and bottom-lines. In this series of articles, I’ll be addressing all testing-related activities that a payer should use in deploying its business markets or lines of business. Periodic assessment, followed by continuous improvement will improve the testing process and have positive impacts on enterprise quality, configuration productivity, and cycle-time reduction efforts. I propose looking at several specific areas across your IT environment. The 14 Quality Maturity Indicators (QMIs) measured in an assessment are:
- Test Management & Organizations
- Master Test Plan & Test Strategy
- Test Plans
- Test Execution
- Test Cases
- Process & Standards Used
- Tools Used
- Automation Capabilities
- Regression Testing Capabilities
- Test Environments
- Performance Testing Approach
- Metrics Used
- Defect Management Process
Once a proper assessment is provided the findings for these 14 QMIs can be used by any number of individuals or teams within an organization to improve testing processes and capabilities. Some examples include:
- Internal assessment team – to identify current testing capability
- Upper management – to initiate a testing improvement program
- Software quality assurance management – to develop and implement process improvement plans
- Configuration/Development teams – to improve testing effectiveness
- Users/health plans – to define their role in the testing process.
In the upcoming series of articles I’ll outline each of the 14 QMIs in greater detail. I’ll conclude by providing a step-by-step assessment process for your team. Stay tuned for updates.