Managing Software Quality Assurance Test Rounds – Part Five (Critical Numbers)

In his book The Personal MBA: Master the Art of Business, the author Josh Kaufman recommends isolating two to five critical indicators, or what he calls Key Performance Indicators (KPI). These numbers should measure throughput and of a given system. The goal in identifying and following these critical numbers is to improve the system under investigation. At

Managing Software Quality Assurance Test Rounds – Part Six (Discovering What Went Wrong)

When discovering and resolving issues two attributes are absolutely necessary. These are a calm head and an experimental mindset. Uncertainty is inevitable. The sooner this is accepted, the better you will become at solving problems. Having numbers that expose issues are of little use unless the system under investigation is improved. A strong increase in

Managing Software Quality Assurance Test Rounds – Part Four (Test Round Scenario)

Now that we understand the overall project risk and have our project matrix in place, we are ready to actually plan our tests and follow the critical numbers. The purpose of this example is not to be entirely accurate in every detail. Exact test case and use case matching was not attempted. Such granularity was beyond

Managing Software Quality Assurance Test Rounds – Part Three (Developing the Project Matrix)

Now that we understand how to assess the project risk, we are ready to actually plan and manage our test rounds. Since software development is a dynamic process, each level of testing must allow a great amount of flexibility. Offering all testing methods and types at each level gives the quality assurance manager the ability