Team:Groningen/Project Plan/Risk List

From 2009.igem.org

Revision as of 20:24, 27 April 2009 by Jaspervdg (Talk | contribs)

[http://2009.igem.org/Team:Groningen http://2009.igem.org/wiki/images/f/f1/Igemhomelogo.png]

Every project has to deal with risks. To ensure a smoothly running project without too many large hiccups it is important to identify these risks and develop strategies to avoid them (and/or reduce their impact).

Also see [http://www.upedu.org/upedu/process/artifact/ar_rskls.htm UPEDU's description of the Risk List] artifact and the enclosing artifact, our project plan.

Risks

For each risk the following is documented:

  • Identifier: a descriptive (short) name
  • Magnitude: one of the following numbers:
    1. Minor nuisance
    2. Bad, but not insurmountable
    3. Show stopper
  • Description/Impact: a brief description of the risk and how it impacts our project.
  • Indicators: when do we know this risk has materialized (or better yet, is about to materialize).
  • Mitigation Strategy: how are we reducing the impact of this risk?
  • Contingency Plan: what can we do if this risk does materialize?

TODO: This is currently just an example, this still needs to be filled in!

Identifier Magnitude Description/Impact Indicators Mitigation Contingency Plan
NoFunding 2 If we do not get any more funding we may not be able to cover our budget. This may mean that some things will not be possible. Our budget should largely be covered before the summer. We already have some funds and are attempting to acquire more. TODO: We should identify some things that could be scrapped if really necessary.