What is Project Risk Management? This definition stands for a row of activities that are related to the conduction of project risk management planning, identification as well as analysis. The major objectives of PRM are the increase of the positive events and impacts on the entire project. On the other end of the sword there are attempts of decreasing the probabilities of negative events happening and their impact on the project as a whole piece. Sounds quite a QA thing to do to me.
What can you, as a QA specialist do for PRM?
In order of getting to the point we have to be sure we are aware of the PRM cycle. PRM begins with identification of possible risks. That is pretty much experience-based data that is gathered from similar projects that are or are not finished. Now who better than a tester will know of the bugs that might occur it the particular project and ways of fixing those? He’s done it for like a thousand times, right?
The next step is assigning possible issues with priorities. How crucial might that bug be? How much time was spent on solutions earlier? May all that data influence deadlines or the project quality? Experience may actually show you what are the odds of a particular issue popping up in the middle of the workflow, how crucial it may be and what impact it can be surrounded with.
Then the risk treatment steps on the stage. The first thing you want to do is avoiding the risk. The second part is risk transfer. If you fear that you won’t be able of managing the possible risk, then inform your management. Quality assurance services are provided by multiple outsourcing companies. Allow them to do that job for you. Now to the risk mitigation part. This one is about reducing possible risks and their impact on the project. For example, if a new team is working on a project give them at least one experienced QA specialist that has been through ice and fire and will be their guiding star.
Thus with a proper quality assurance team you are not risking too much. When everybody in your team is working on a common goal your services as well as your software are not risking. At least not too much.