Project Risk Analysis - NextensArelB/SwaggerGenerationTool GitHub Wiki

Besides Feature Risk Analysis, which forms the basis for Risk Based testing, you can also perform a Risk Analysis on Project level. This is currently not yet implemented within Nextens, but below a short introduction of Why, When and examples of mitigations.

Why a Project Risk Analysis A project has never unlimited time and money to develop and to test. Risk Analysis is a way to help a team to allocate limited resources, to identify mitigations and to determine which features should have a high test coverage (manual and automated). Time and resources should be allocated to those functionalities where the risk is maximum, Risk Analysis assists in identifying and estimating those risks.

When to perform a Project Risk Analysis At start of the project, when breaking down the project into epics and features and creating the backlog, the epics and features are being assessed, where per feature the related risks and risk level is determined by the PO, BA, DM, QA and Dev lead.

Examples of mitigations out of a Project Risk Analysis While test mitigations are more re-active, other mitigations are aimed to be more pro-active in order to minimize the likelihood and impact of the risk. These mitigations are based on the motivations of the score, e.g. when Likelihood is high as new technology is being used in the team, it could be useful to have additional trainings or coaching in place. Examples of other mitigations are: • Additional resources or resources with specific qualifications • Training/coaching • Describe requirements in more detail • Increase reviews • Usage of standard components • Usage of coding standards