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
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
“What gets measured gets managed and what gets managed gets done.” – Peter Drucker Before the project is organized and critical numbers are calculated, I recommend running a risk assessment exposing weaknesses in your quality assurance planning and processes. This analysis is a great tool that identifies issues well in advance. The assessment is much easier
