#12: Risk Management.

As part of our weekly chores, we assessed the risks to our project.

While we thought of those, we became aware of some risks that we weren’t prepared for.

We didn’t have a regular database backup in place for example.

Below you can see our finished table of risks.

NameDescriptionProbabilityImpactRisk FactorMitigationIn Charge
Amazon blocks usAmazon blocks our crawler, because it sends too many requests0,483,2Send a minimal amount of
requests
Distribute Load
(Use Proxies)
Henning
Server has outageServer goes down for unkown reason –> All data is lost!0,05100,5BackupHenning
A Team member gets really sickWe have reduced manhours to finish our project.0,130,3Redefine scope in that caseGeorg
Essential Services go downOne of our main tools, like YouTrack or GitHub goes down0,0290,18Depends on tool:
YouTrack: Nothing? GitHub: Move to Gitea
Patrick
Data TheftAn Attacker gets hold of all our data0,005100,05Secure sensitive dataGeorg

While we hope that none of this happens, we still want to be prepared just in case.

On the other hand we identified a single point of failure that is out of our control:

YouTrack

We just need to hope that our project management information is safe there. Is maybe one of our readers aware of a solution?

2 thoughts on “#12: Risk Management.”

  1. Hello Betterzon,
    we like your blog and your project. For us, it is very interesting to see which risks you identified for your project 🙂 We think these are really realistic risks and we think that you found the most important risks.
    We recognized one thing. We should astimate the risk impact from 1 (negligible) to 10 (large). We can understand why you used there also percentages, but I think with a scala from 1 to 10 it is clearer because you don’t have many values.
    Keep up the good work 😉
    You friends from TaskHUB

    Reply
  2. Hello Betterzon,

    The risks you have in your list look very well put together. As mentioned the scale had to be from 1 to 10. None the less you have a nice list of risks we didn’t think of.
    Our focus was more on things in the development of our app and we didn’t look at our tools as a point of failure at all.

    Keep it up and running (especially YouTrack)
    The Work2Play Team

    Reply

Leave a Reply to Work2Play Team Cancel reply