Project, cost and technology risks, strategy and personal risks – they all have effects on the application life cycle. That’s why you should have already assessed requirements with regards to the risks associated with them. With objectiF RPM, the relationships between requirements and their risks are clear and traceable.
centrally and securely
Record the results of risk analysis
You can decide the information you would like to document for risks. This includes, e.g., priority, likelihood of occurrence, and damage control measures. This means that it’s easy to carry out a risk assessment.
Don’t forget traceability, so that risks can be linked to requirements. This means each risk is version-controlled.
Keep an overview of risks
The connections between risks and other work results are clearly displayed with special queries and filters.
You can prioritize risks and thus create a list of the top ten risks. It’s also possible to export the list to MS Excel to send it to others.
Plan measures to reduce and avoid risks
Some risk avoidance and reduction measures might need to be planned into the project if they require workload to be allocated to them. To make sure this connection is traceable, you can create relationships between risks and activities in the project plan.
You can also record decisions on avoidance strategies and options for risk reduction for every risk.