Risk list - VikRic/MealPlanner GitHub Wiki
The purpose of the risk list is to ensure a successful project by identifying and highlighting risks, as well as developing a plan for how these should be managed. Risks are therefore an important input to iteration planning.
📌 The Risk List Should Include:
- A prioritized top list of risks
- Detailed risk specifications:
Risk Specification Fields:
- Risk Name
- Description
- Probability (1–5), Impact (1–5), Priority = Probability × Impact
- Monitoring Strategy – How can we monitor this risk? Who is responsible?
- Impact Strategy – Can we reduce the impact if the risk occurs?
- Probability Strategy – Can we reduce the likelihood of the risk occurring?
🔄 Maintenance
The risk list should be continuously updated and reviewed. Resolved risks should be de-prioritized, and new risks should be added.
By the time the project enters the Construction phase, no critical risks should remain unmanaged.
🚨 Risks
| Risk Name | Description | Probability | Impact | Monitoring Strategy | Impact Strategy | Probability Strategy |
|---|---|---|---|---|---|---|
| API offline | If the Spoonacular API goes down, the service will not function | 1 | 5 | Check status | Save data in MongoDB | Cache each GET request in a database to reduce dependency on live calls |
| API limit | Exceeded the number of allowed API requests | 5 | 5 | Set up email notifications for limit alerts. Upgrade plan if needed. | Use another API provider to increase request limits | Cache each GET request in a database to reduce API usage |