HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2012T1 M.O.O.T/Project Management/Risk Management"

From IS480
Jump to navigation Jump to search
(New page: <font face="century gothic" size="2"> {| style="background-color:none; color:#ffffff; border-bottom:3px solid #9400D3; border-top:3px solid #9400D3; border-left:3px solid #9400D3; border-...)
 
Line 38: Line 38:
 
| style="font-size:90%; text-align:center; background-color:#9400D3; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_M.O.O.T/Project_Management/Risk_Management|<font color="#ffffff">Risk Management</font>]]
 
| style="font-size:90%; text-align:center; background-color:#9400D3; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_M.O.O.T/Project_Management/Risk_Management|<font color="#ffffff">Risk Management</font>]]
  
 +
|}
 +
 +
=== Risk Management ===
 +
 +
{| class="wikitable"
 +
|-
 +
! S/N
 +
! Risk Statement
 +
! Impact
 +
! Likelihood
 +
! Impact Level
 +
! Mitigation Strategy
 +
! Status
 +
|-
 +
| colspan="7" | '''Technology & Learning Risk'''
 +
|-
 +
| 1
 +
| Lack of documentation for Kinect SDK
 +
|
 +
* Development is delayed
 +
| High
 +
| High
 +
|
 +
* Look for latest Kinect examples online
 +
|
 +
 +
|-
 +
| 2
 +
| No suitable gestures library that we can use
 +
|
 +
* Development is delayed
 +
* Some features may have to be dropped
 +
| High
 +
| High
 +
|
 +
* Write our own gesture library
 +
|
 +
|-
 +
| 3
 +
| Self-written motion gestures may be inaccurate/inconsistent/too difficult to perform.
 +
|
 +
* Development is delayed
 +
* Some features may have to be dropped
 +
| High
 +
| High
 +
|
 +
* Gather feedback consistently, assess written gestures and then decide whether to change them.
 +
* Watch videos of Kinect games to learn how to make better motion gestures.
 +
|
 +
|-
 +
| 4
 +
| Team is unfamiliar with working with new technology & tools
 +
|
 +
*Development is delayed
 +
* Schedule is affected
 +
| High
 +
| High
 +
|
 +
* Allow sufficient time for each member to learn the new technology and tools
 +
* Arrange weekly sessions to review on progress
 +
|
 +
|-
 +
| colspan="7" | '''Scope Risk'''
 +
|-
 +
| 5
 +
|  Sponsor changes his requirements frequently
 +
|
 +
* Core functionalities may not be able to be completed
 +
* Schedule is affected
 +
| Medium
 +
| Medium
 +
|
 +
* Update sponsor consistently with the latest progress of project
 +
* Develop paper prototypes to ensure sponsor & team are on the same level of agreement
 +
* Divide huge tasks into smaller features that can be pushed out a weekly basis
 +
|
 +
|-
 +
| 6
 +
| Team overpromising new features
 +
|
 +
* Schedule is affected
 +
| Medium
 +
| Medium
 +
|
 +
* Prioritize list of functions in client’s requirements list before coming to an agreement with him
 +
|
 +
|-
 +
| colspan="7" | '''Development Risk'''
 +
 +
|-
 +
| 7
 +
| There is a critical bug that affects the core functionalities
 +
|
 +
* Core functionalities are not working
 +
| High
 +
| High
 +
|
 +
* Team will halt current development and focus on debugging
 +
* Forecast the features able to be completed & inform client of functionalities which cannot be completed
 +
|
 +
|-
 +
| colspan="7" | '''Schedule Risk'''
 +
 +
|-
 +
| 8
 +
| Team members have other commitments and different priorities
 +
|
 +
*Team morale is low
 +
| Medium
 +
| High
 +
|
 +
* Communicate & align individual member’s priorities & project priorities together
 +
* Set clear tasks together as a team every week
 +
|
 +
 
|}
 
|}

Revision as of 09:00, 19 July 2012

Home

Team/Project Partners

Project Overview

Project Management

Design Specifications

Technical Applications


Project Schedule Methodology Metrics Risk Management

Risk Management

S/N Risk Statement Impact Likelihood Impact Level Mitigation Strategy Status
Technology & Learning Risk
1 Lack of documentation for Kinect SDK
  • Development is delayed
High High
  • Look for latest Kinect examples online
2 No suitable gestures library that we can use
  • Development is delayed
  • Some features may have to be dropped
High High
  • Write our own gesture library
3 Self-written motion gestures may be inaccurate/inconsistent/too difficult to perform.
  • Development is delayed
  • Some features may have to be dropped
High High
  • Gather feedback consistently, assess written gestures and then decide whether to change them.
  • Watch videos of Kinect games to learn how to make better motion gestures.
4 Team is unfamiliar with working with new technology & tools
  • Development is delayed
  • Schedule is affected
High High
  • Allow sufficient time for each member to learn the new technology and tools
  • Arrange weekly sessions to review on progress
Scope Risk
5 Sponsor changes his requirements frequently
  • Core functionalities may not be able to be completed
  • Schedule is affected
Medium Medium
  • Update sponsor consistently with the latest progress of project
  • Develop paper prototypes to ensure sponsor & team are on the same level of agreement
  • Divide huge tasks into smaller features that can be pushed out a weekly basis
6 Team overpromising new features
  • Schedule is affected
Medium Medium
  • Prioritize list of functions in client’s requirements list before coming to an agreement with him
Development Risk
7 There is a critical bug that affects the core functionalities
  • Core functionalities are not working
High High
  • Team will halt current development and focus on debugging
  • Forecast the features able to be completed & inform client of functionalities which cannot be completed
Schedule Risk
8 Team members have other commitments and different priorities
  • Team morale is low
Medium High
  • Communicate & align individual member’s priorities & project priorities together
  • Set clear tasks together as a team every week