Page History
...
- What and how "things" can affect our project?
- Risk Identification
- identification of risks to product (e.g. software/hardware) features; this is normally performed by the team and discussed together
- risks are identified before implementation starts and are reviewed throughout the development life cycle; new risks can be identified during implementation
- Risk Analysis
- risks are discussed together in the team (may involve customer)
- risks impact and probability are calculated, and thus the related risk level
- Risk Identification
- How will we handle it, in the most effective way (i.e. the one that can return most value)?
- Risk Evaluation and Treatment
- Test Planning
- using the input from Risk Analysis, the test manager can...
- define test strategy (e.g. level of testing to perform, techniques to use, environments to choose)
- estimate testing effort
- define/estimate schedule (target dates, number of testing iterations)
- using the input from Risk Analysis, the test manager can...
- Test Design
- specification of the Tests taking the identified risks as input; tests are designed to mitigate the risk (i.e. diminish their probability)
- make use of more extensive data with data-driven testing and automated testing/checking, if needed
- Test Execution
- perform testing by descending order of risk level (i.e. execute Tests related with higher risks first); experienced testers, with high degree of domain knowledge may provide more valuable feedback
- thoroughly test risky items, using scripted and exploratory approaches
- Test Planning
- Risk Monitoring and Reviewing
- look at items where you assessed the risk and evaluate if you need to take additional measures/treatments ("Are those items having failed tests? Were bugs founds? Are those bugs relevant? Did we find any new risk while testing?")
- Risk Evaluation and Treatment
RBT in Waterfall and variants
In projects following waterfall, or one of the waterfall variants, in their SDLC, RBT can fit as follows (high-level overview).
...