| || |
Capturing 'test planning issues' (risks which actually occurred) during testing
Just wondering how other people go about capturing/recording incidents and issues which occur during testing activities and have an adverse impact on test planning and management. these are, if you like, potential test planning risks that were previously identified in the Risk Register, and which actually occurred. (This is not software defects, btw).
An example would be:
- Risk Register Item - testing starts on feature X before requirements are approved (identified as a potential risk) -
- And, some time later, this actually occurred - pressure from management, testing started against unapproved requirements, and the requirements were then scrapped - resulting in a lot of wasted time on Test Planning, Preparation (writing test cases, creating data), executing test cases, etc
I'd like to capture that
(a) something happened that caused us a problem during our test activities
(b) why it happened/what caused it
(c) what the impact of this was (time/cost/quality)
(d) what we can do to prevent this happening in the future
How/where would you keep track of incidents such at this? It's not the 'Risk Register' as this seems to be a predictive list for things which might occur. This is more of a log of what actually occurred, and which should trigger some activities to prevent it from happening in again (clarify the process, change the process, assess the time/cost impact, etc). At the moment i've got a 'Testing Issues Register' that I maintain, but is there a better name for this, or a more industry standard way of doing this?
I am not aware if there is an industry standard name for such a document, but I would suggest 'Retrospective document'