Editing Final Report 2011 (section)

===Risk Management===
None of the risks identified in the formation stages of the project<ref name=S1PR>Johnson, Patrick and Maxwell, Steven, ''Stage 1 Design Document 2011'', https://www.eleceng.adelaide.edu.au/personal/dabbott/wiki/index.php/Stage_1_Design_Document_2011</ref> have had a significant impact on the progress and results. The project has been completed on schedule, on budget and meets the objectives. This, in part, can be attributed to successful implementation of risk management strategies. The project risks and OH&S risks identified are summarised in the tables below.


<center>'''Table 6 - Project risks summary'''</center>
{| border="1" cellspacing="0" style="text-align:center; margin: 1em auto 1em auto"
|- style="color:white; background:#191970; font-weight:bold"
| width="300" | Risk || width="160" | Risk Estimation || width="300" | Reduction Strategy
|- valign="top"
| style="color:white; text-align:left; background:#4682B4" | Availability of personnel || style="background:#FF0000" | High || style="text-align:left" | Regular meetings with flexible schedule
|- valign="top" style="background:#DCDCDC"
| style="color:white; text-align:left; background:#4682B4" | Insufficient financial resources || style="background:#FFFF00" | Medium || style="text-align:left" | Open source software and project budget
|- valign="top"
| style="color:white; text-align:left; background:#4682B4" | Software development tool access || style="background:#FF0000" | High || style="text-align:left" | Suitable personal work environment on laptop for each team member
|- valign="top" style="background:#DCDCDC"
| style="color:white; text-align:left; background:#4682B4" | Unable to maintain software development schedule || style="background:#FFFF00" | Medium || style="text-align:left" | Progress management strategy
|- valign="top"
| style="color:white; text-align:left; background:#4682B4" | The Somerton Man case is solved || style="background:#00FF00" | Low || style="text-align:left" | No risk reduction strategy
|-
|}



<center>'''Table 7 - Occupational health and safety risks summary'''</center>
{| border="1" cellspacing="0" style="text-align:center; margin: 1em auto 1em auto"
|- style="color:white; background:#191970; font-weight:bold"
| width="220" | Risk || width="160" | Risk Estimation || width="220" | Reduction Strategy
|- style="color:white; background:#4682B4; font-weight:bold; text-align:center"
| colspan="4" | Physical Hazards
|-
| style="color:white; text-align:left; background:#4682B4" | External construction noise || style="background:#FFFF00" | Medium || rowspan="3" style="vertical-align:top; text-align: left" | University of Adelaide OHS policy
|-
| style="color:white; text-align:left; background:#4682B4" | Falls within laboratory || style="background:#FFFF00" | Medium
|-
| style="color:white; text-align:left; background:#4682B4" | Injuries due to electrical shock || style="background:#FFFF00" | Medium
|- style="color:white; background:#4682B4; font-weight:bold; text-align:center"
| colspan="4" | Chemical Hazards
|-
| style="color:white; text-align:left; background:#4682B4" | None || - || -
|- style="color:white; background:#4682B4; font-weight:bold; text-align:center"
| colspan="4" | Biological Hazards
|-
| style="color:white; text-align:left; background:#4682B4" | None || - || -
|- style="color:white; background:#4682B4; font-weight:bold; text-align:center"
| colspan="4" | Ergonomic Hazards
|- style="vertical-align:top"
| style="color:white; text-align:left; background:#4682B4" | Work place layout || style="background:#00FF00" | Low || style="text-align:left" | University of Adelaide workstation ergonomic guidelines
|- style="color:white; background:#4682B4; font-weight:bold; text-align:center"
| colspan="4" | Radiation Hazards
|-
| style="color:white; text-align:left; background:#4682B4" | None || - || -
|- style="color:white; background:#4682B4; font-weight:bold; text-align:center"
| colspan="4" | Psychological Hazards
|-
| style="color:white; text-align:left; background:#4682B4" | Work related stress || style="background:#FFFF00" | Medium || rowspan="2" style="vertical-align:top; text-align: left" | Individually developed and monitored strategy
|-
| style="color:white; text-align:left; background:#4682B4" | Repetitive tasks || style="background:#FFFF00" | Medium 
|-
|}

Of these risks, the most prevalent were the Personnel Availability and Access to software development tools. Both project team members had extremely busy schedules relating to outside work at stages throughout the project however, high levels of communication meant the progress didn’t fall significantly behind schedule at any point.

Access to developmental software was a particular issue given neither Steven nor Patrick had allocated workstations at the University. As the table identifies, personal laptops were used extensively to avoid this issue.