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
Line 63: Line 63:
 
| High
 
| High
 
|  
 
|  
* Research on possible ways/algorithms to do gender recognition�
+
* Research on possible ways/algorithms to do gender recognition
 
* Devise feasible way to determine gender
 
* Devise feasible way to determine gender
* Learn, modify and integrate algorithm into application
+
* Learn, modify and integrate algorithm into application
 
|  
 
|  
 
|-
 
|-
| 1
+
| 2
 
| No library available for gender recognition
 
| No library available for gender recognition
 
|  
 
|  
Line 75: Line 75:
 
| High
 
| High
 
|  
 
|  
* Research on possible ways/algorithms to do gender recognition�
+
* Research on possible ways/algorithms to do gender recognition
 
* Devise feasible way to determine gender
 
* Devise feasible way to determine gender
* Learn, modify and integrate algorithm into application
+
* Learn, modify and integrate algorithm into application
 
|  
 
|  
 
|-
 
|-
| 1
+
| 3
 
| Accuracy of gender recognition
 
| Accuracy of gender recognition
 
|  
 
|  
Line 90: Line 90:
 
|  
 
|  
 
|-
 
|-
| 2
+
| 4
 
| No suitable gestures library that we can use
 
| No suitable gestures library that we can use
 
|  
 
|  
Line 101: Line 101:
 
|  
 
|  
 
|-
 
|-
| 3
+
| 5
 
| Self-written motion gestures may be inaccurate/inconsistent/too difficult to perform.
 
| Self-written motion gestures may be inaccurate/inconsistent/too difficult to perform.
 
|  
 
|  
Line 113: Line 113:
 
|  
 
|  
 
|-
 
|-
| 4
+
| 6
 
| Team is unfamiliar with working with new technology & tools
 
| Team is unfamiliar with working with new technology & tools
 
|  
 
|  
Line 127: Line 127:
 
| style="background: #C8BBBE;" colspan="7" | Scope Risk
 
| style="background: #C8BBBE;" colspan="7" | Scope Risk
 
|-  
 
|-  
| 5
+
| 7
| Sponsor changes his requirements frequently
+
| Sponsor changes his requirements frequently
 
|  
 
|  
 
* Core functionalities may not be able to be completed  
 
* Core functionalities may not be able to be completed  
Line 140: Line 140:
 
|  
 
|  
 
|-
 
|-
| 6
+
| 8
 
| Team overpromising new features
 
| Team overpromising new features
 
|  
 
|  
Line 153: Line 153:
  
 
|-
 
|-
| 7
+
| 9
 
| There is a critical bug that affects the core functionalities
 
| There is a critical bug that affects the core functionalities
 
|  
 
|  
Line 167: Line 167:
  
 
|-
 
|-
| 8
+
| 10
 
| Team members have other commitments and different priorities  
 
| Team members have other commitments and different priorities  
 
|  
 
|  

Revision as of 12:21, 16 August 2012

Home

Team/Project Partners

Project Overview

Project Management

Design Specifications

Technical Applications


Project Schedule Methodology Metrics Risk Management Minutes Repository

Risk Management

S/N Risk Statement Impact Likelihood Impact Level Mitigation Strategy Status
Technology & Learning Risk
1 No library available for gender recognition
  • Development is delayed
High High
  • Research on possible ways/algorithms to do gender recognition
  • Devise feasible way to determine gender
  • Learn, modify and integrate algorithm into application
2 No library available for gender recognition
  • Development is delayed
High High
  • Research on possible ways/algorithms to do gender recognition
  • Devise feasible way to determine gender
  • Learn, modify and integrate algorithm into application
3 Accuracy of gender recognition
  • Development is delayed
High High
  • Add more behaviour traits and characteristics as parameters to determine gender such as shape of clothes, heels elevation
4 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
5 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.
6 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
7 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
8 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
9 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
10 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