"
Team:Groningen/Project Plan/Risk List
From 2009.igem.org
(Difference between revisions)
m (Template header.) |
|||
| Line 2: | Line 2: | ||
[[Category:Team:Groningen/Disciplines/Project_Management|Project Plan/Risk List]] | [[Category:Team:Groningen/Disciplines/Project_Management|Project Plan/Risk List]] | ||
[[Category:Team:Groningen/Roles/Project_Manager|Project Plan/Risk List]] | [[Category:Team:Groningen/Roles/Project_Manager|Project Plan/Risk List]] | ||
| + | |||
| + | ==Introduction== | ||
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). | 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). | ||
| + | |||
| + | The table below, shows the possible risks that may influence the success of the iGEM project. It gives an outline of 5 main risks, namely problems which emerge from finances, time span, lab work, modeling and members / instructors. Possible risks were traced from the problems of iGEM Groningen 2008 and of the iGEM 2008 teams which were withdrawn from the competition. | ||
Also see [http://www.upedu.org/upedu/process/artifact/ar_rskls.htm UPEDU's description of the Risk List] artifact and the enclosing artifact, [[Team:Groningen/Project_Plan|our project plan]]. | Also see [http://www.upedu.org/upedu/process/artifact/ar_rskls.htm UPEDU's description of the Risk List] artifact and the enclosing artifact, [[Team:Groningen/Project_Plan|our project plan]]. | ||
| Line 11: | Line 15: | ||
*Identifier: a descriptive (short) name | *Identifier: a descriptive (short) name | ||
| - | *Magnitude: | + | *Magnitude: ranking from 1-10, 1 is low risk and 10 is a high risk. Taking in account: how probable and severe the problem is. |
| - | + | ||
| - | + | ||
| - | + | ||
*Description/Impact: a brief description of the risk and how it impacts our project. | *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). | *Indicators: when do we know this risk has materialized (or better yet, is about to materialize). | ||
| Line 32: | Line 33: | ||
|NoFunding | |NoFunding | ||
|2 | |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. | ||
| + | |} | ||
| + | |||
| + | {| border="1" | ||
| + | |+Finances | ||
| + | !Magnitude | ||
| + | !Description | ||
| + | !Impact | ||
| + | !Mitigation Plan | ||
| + | !Contingency Plan | ||
| + | |- | ||
| + | |NoFunding | ||
| + | |6 | ||
|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. | |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. | |Our budget should largely be covered before the summer. | ||
Revision as of 14:38, 2 May 2009
[http://2009.igem.org/Team:Groningen http://2009.igem.org/wiki/images/f/f1/Igemhomelogo.png]
|
|---|
Introduction
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).
The table below, shows the possible risks that may influence the success of the iGEM project. It gives an outline of 5 main risks, namely problems which emerge from finances, time span, lab work, modeling and members / instructors. Possible risks were traced from the problems of iGEM Groningen 2008 and of the iGEM 2008 teams which were withdrawn from the competition.
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: ranking from 1-10, 1 is low risk and 10 is a high risk. Taking in account: how probable and severe the problem is.
- 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. |
| Magnitude | Description | Impact | Mitigation Plan | Contingency Plan | |
|---|---|---|---|---|---|
| NoFunding | 6 | 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. |
