Skip to content

Commit

Permalink
Merge pull request #19 from olafurjohannsson/update-risk-analysis
Browse files Browse the repository at this point in the history
Update risk analysis
  • Loading branch information
Eysteinn-Orn committed Dec 5, 2023
2 parents 217136d + 7bafa29 commit 377f71f
Showing 1 changed file with 11 additions and 11 deletions.
22 changes: 11 additions & 11 deletions src/RiskAnalysis.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,14 +2,14 @@

| Risk | Likelihood (1-5) | Impact (1-5) | Responsibility | Mitigation Strategy |
|---------------------------------------|-------------------|---------------|-------------------|---------------------|
| Integration of Feedback from Advisors | 5 | 4 | Ólafur | Schedule interim reviews with advisors and allocate time for revisions based on feedback. |
| Report Completion Delay | 3 | 5 | Whole Team | Set internal deadlines and checkpoints for report sections to stay on schedule. |
| Underestimating the Time Required for Revisions | 3 | 4 | Whole Team | Allow buffer time in the project schedule specifically for revisions. |
| Presentation Preparation Inadequacy | 2 | 5 | Whole Team | Conduct practice sessions, prepare well in advance, and ensure all team members are familiar with all parts of the presentation. |
| Inaccuracy in Reported Results | 2 | 5 | Eysteinn | Peer-review within the team, double-check all results and analyses. |
| Miscommunication Within the Team | 3 | 3 | Whole Team | Regular meetings, clear communication channels, and shared documentation practices. |
| Data Misinterpretation | 2 | 4 | Ólafur | Have findings reviewed by all team members for clarity and consistency. |
| Illness in Team During Writing Phase | 2 | 3 | Whole Team | Distribute the workload and prepare contingency plans. |
| Missing Documentation for Methods | 1 | 5 | Birkir | Ensure all methodologies are well-documented as we write the report. |
| Technical Issues with Document Sharing/Collaboration Tools | 2 | 2 | Birkir | Use reliable collaboration tools and maintain regular backups of the report. |
| Formatting and Submission Issues | 1 | 3 | Eysteinn | Follow the submission guidelines, stay vigilant, keep eachother updated and regularly save drafts in the correct format. |
| Presentation Preparation Inadequacy | 3 | 5 | Whole Team | Increase practice sessions, finalize slide deck early, and ensure clear understanding of each part by every team member. |
| Last-minute Changes or Feedback Integration | 3 | 4 | Ólafur | Allocate time for last-minute revisions, maintain flexibility in report and presentation content. |
| Technical Issues with Presentation Equipment | 3 | 4 | Birkir | Test all equipment prior to the presentation, have a backup plan for technical failures. |
| Report Completion Delay | 2 | 5 | Whole Team | Focus on the final touches, ensure each section meets quality standards, and set clear deadlines for completion. |
| Miscommunication Within the Team | 2 | 3 | Whole Team | Enhance communication especially for final report edits and presentation strategies. |
| Illness in Team During Final Phase | 2 | 3 | Whole Team | Maintain health protocols, ensure backup plans for team member roles in presentation. |
| Inaccuracy in Reported Results | 1 | 5 | Eysteinn | Final review of results for accuracy, involve another team member in cross-verifying data. |
| Missing Documentation for Methods | 1 | 4 | Birkir | Final checks to ensure all methods are properly documented. |
| Data Misinterpretation | 1 | 4 | Ólafur | Final review of data interpretation, cross-check with advisors if necessary. |
| Formatting and Submission Issues (Report & Presentation) | 1 | 3 | Eysteinn | Final review of formats, adherence to guidelines, and early submission to avoid last-minute issues. |
| Technical Issues with Document Sharing/Collaboration Tools | 1 | 2 | Birkir | Continuation of reliable practices for document sharing and collaboration, with regular backups. |

0 comments on commit 377f71f

Please sign in to comment.