Tutorials SQAA manger should stick to a principle or a number of principles all the time to ensure the success of the process. In SQA, there are three principles that every SQA manager should observe:
Consistency – Every document and output should be according to what is planned and what was written. The SQA plan should always be the bases to what should be done and the same plan should be the bases if the application has reached the benchmark or not. Without the consistency, the SQA team would deviate to one goal at first which will resonate to another error. This error will eventually be highlighter through a bug or worst case scenario, system crash.
Minimize Risk – Being always at the safe side doesn’t mean the application is not that creative. Basically, SQA is there to test if the application works according to plan. SQA’s do not take risk and works with what is written on paper. This way, everything that has been stipulated will work as planned. Without going out of the way, developers will have the security that the application will work as planned.
Realistic – What is written in paper and in plan should be executed by the letter. However that doesn’t mean the SQA team will be hard pressed all the time. The SQA manager should ensure the plan should take a realistic approach at all times. If possible, the SQA manager should be realistic as early as the planning stage. This will ensure they have the right plan from the start. Compromise is possible but it should be done in the planning stage to ensure the smoothness of the operation
Everything that has been laid out so far is just in theories or in principles. But just as important, the SQA team should be able to provide the numbers the clients are looking for as this will dictate the success or failure of the project.
On the other hand, the SQA manager will not just provide numbers from their testing tools. Before these tools are executed, the SQA manager should lay out the expected metrics that will be produced. These metrics are probably the most important facts that any client will need. The SQA team has to make sure the metrics that will be stipulated will truly tell how the application will perform.
Sometimes, the metrics that will be used might not give the right type of numbers. The numbers are there and tell of the performance of the application but the SQA team should ensure that these tools will produce the type of metrics the clients are looking for.
Managing the SQA projects will greatly focus on the tools that will be used in testing the application. These applications will be the aid of the SQA team’s work. The manager will make sure the testing applications will produce the desired metrics.
First Page: Managing SQA Projects
