Our AdaptiveQA™ process

There are numerous QA methodologies that have evolved since the advent of computers. Many are useful, some are not, and some have yet to be discovered. At CPS, we have developed our own approach to QA that has its foundations in traditional QA methodologies but is adapted to our unique situation. Since we work with different clients on different technologies for products designed for different industries, we need a methodology that allows us to adapt to each situation quickly and still provide a high level of assurance that a product works as designed. We call it AdaptiveQA.

Each of our clients have different requirements for quality assurance. Each of their products have different requirements for how they work. It is most efficient for us to start with a baseline or core set of values for QA responsibilities. We add a set of QA Plan templates that accommodate most projects and are added to as we learn and work on new technologies. We work in a fluid environment so we need a fluid process. This means we don’t test a feature on December 1 just because the QA Plan says to test it. If the feature isn’t ready, or has been tagged for redevelopment, we don’t waste the time testing something for no gain. If we learn new information regarding a feature, we change the test plan and submit it to our client for approval. If a client asks us to radically change a product that is already in a testing stage, we stop testing and work on other projects until it makes sense to reengage the test team.

The system is predicated on strong QA leadership. The QA Lead maintains a tight coupling with the project starting at the design phase. He or she develops a knowledgebase of the functionality and schedule so the QA Plan can be created. The lead then maintains close contact with the development team when changes are proposed and decisions made that affect the testability and testing schedule of the product. Triggers are identified in the QA Plan that spurn the QA Lead or QA Technicians into action, whether adapting or rewriting the test plans, identify the appropriate escalation path for issues, or other project impact scenarios. Click here to read more about AdaptiveQA.

©2004 Critical Path Software Incorporated.   All rights reserved.