Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Part delivery is much slower than expected, pushing back testing and therefore project deadlines

  2. Members miss deliverable due to increased work load

  3. Schedule didn’t allow for multiple iterations to occur, now we’re stuck with a less-than-ideal product

  4. The drone isn’t competitive

  5. The drone crashing during competition

Risk Analysis (use to understand impact)

...

Risk Event

Related Subteam

Probability % (P)

Severity Rating (S)

Risk Score (P*S)

XXX

Competition paperwork isn’t finished on time leading to not being able to compete

all

Possible

Extreme

Extreme 80

The competition drone doesn’t fly adequately enough to be competitive

all

Possible

Tolerable

Medium 40

Risk Response (use to mitigate risks)

...

Risk Event

Risk Response

Assignee (RSE)

Competition paperwork isn’t finished on time leading to not being able to compete

  • Sysint to make sure templates and the bones of the report is finished

Hamza Ali to finish the rough draft for the report

The competition drone doesn’t fly adequately enough to be competitive

  • Iterate designs and test code by scheduling test flights and organizing different key areas to test each flight

Aaron Dyck (Deactivated) schedule flights and help with organizing flights

Risk Monitoring (use to document risks)

...

Risk Event
What happened?

Risk Impact
What consequence(s) occurred?

Future Mitigation
What can you do to prevent this from happening again?

Deadline for competition drone timeline went over

  • We don’t have a good way to keep track of deadlines, or see how other late deliverables affect the overall timeline

  • Prioritize tasks based on importance to not overwork members, while still getting the most important tasks finished