I am reading software risk management to involve risks in test plan and also there is one ingredient “Risks” in software test plan I have gone through several articles on web and e-books, but I found the risk involved in that test plan has nothing to do with the testing and almost related to Software development risks
Can anybuddy please help out to understand what are the components of “Risks” which we do normally include in software Test Plan? And measures to eliminate that risk
Quality is Never Ending Process of Improvement
It may depend on company culture, but I will share my own experience. Through years I found that I could use "Risks" chapter in my test plan to request a support from PM about tasks/things that worries me - as a tester - most.
Either I want better support from developers, more RAM to my workstation or changes in process: I just describe why I need it in a form of risk - and if PM finds it reasonable he/she is going to help me.
?:the art of a constructive conflict perceived as a destructive diagnose.
I agree with Ainars' response in that this is largely a situational question. This is a good chance for you to think about your test plan rather than just using a template or what other people have used. I like to encourage thinking so ....
.... I would turn this back on you and say the best way to help you answer it is for you to tell us what you think some of the risks are with the testing you're doing or the risks that could happen relative to testing.
Remember also that software development risks also impact testing -- at least usually -- depending upon the extent testing is infused into the development lifecycle. So it's not necessarily like there's development risks and testing risks and the two never meet.