| || |
Producing a risk report
I've searched the forums (honestly, I have!) and can't find a topic which might address my query, hence the post!
You might need some background on where I'm at with a particular project and I'll be brief. Essentially in a twisted way I've been fortunate enough to have been subjected to the worst possible scenario in software testing. The deal with a third party was settled late, as a consequence development started late (putting strain on the dev team) and worse still, the test period was prescribed to us.
Again, as a consequence of the above all test analysis started later than usual - we tried testing alongside development but found this difficult for numerous reasons I won't go into. To the point - our analysis of risk based on changes to the application and the volume of testing required as agreed by myself and the product owner/marketing team simply cannot be done in the time available.
I have now been asked by senior management to produce a document which would state what *could* be tested in the time available, what risks would be present if we weren't to test certain elements of the application that really should. I have that information but since this is the first time I've had to do this to this extent and given that this document will be viewed by the CEO I'd like to ensure that it's presented in the most appropriate way possible.
I'd very much appreciate your suggestions and any value you may have to add to the above.
Re: Producing a risk report
Well, to start with you'd probably be best off defining the critical path functionality and listing it out by component or use case. You could do this in a Word or Excel table and add in columns for "test priority" (how important it is to test this function), "test risk" (how risky is it *not* to test this) and "test time" (how long would it take to execute the test). Once you have the basic rankings assigned you can outline several scenarios and estimate the test coverage and time from that. You can then optimize the test approach for the amount of time available, or demonstrate to management that the allotted time is not sufficient to cover all high priority / high risk items.
In terms of presentation, I'd write up a memo or short document that defines the situation (not enough time to test) and the goal (optimize the available test time remaining), and then shows the table of test areas and their associated rankings. You can then summarize which of the options are best (pick the top 3 or so) and list the general pros/cons of each, followed by your recommendation of which option to use. This documents your approach to the problem, the data you used, the associated risks, and the final recommendation.
Re: Producing a risk report
Under this link you will find relevant discussion and additional links.
Here is another.
... and another.
Are you by chance being TORGed?