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 58: Line 58:
 
| style="background: #C8BBBE;" colspan="7" | Technology & Learning Risk
 
| style="background: #C8BBBE;" colspan="7" | Technology & Learning Risk
 
|-
 
|-
| style="text-align: center;" 1
+
| style="text-align: center;" |1
 
| No library available for gender recognition
 
| No library available for gender recognition
 
|  
 
|  
Line 70: Line 70:
 
|  
 
|  
 
|-
 
|-
| style="text-align: center;" 2
+
| style="text-align: center;" |2
 
| Accuracy of gender recognition
 
| Accuracy of gender recognition
 
|  
 
|  
Line 80: Line 80:
 
|  
 
|  
 
|-
 
|-
|style="text-align: center;" 3
+
|style="text-align: center;" |3
 
| No suitable gestures library that we can use
 
| No suitable gestures library that we can use
 
|  
 
|  
Line 91: Line 91:
 
|  
 
|  
 
|-
 
|-
| style="text-align: center;" 4
+
| style="text-align: center;" |4
 
| 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 103: Line 103:
 
|  
 
|  
 
|-
 
|-
| style="text-align: center;" 5
+
| style="text-align: center;" |5
 
| Team is unfamiliar with working with new technology & tools
 
| Team is unfamiliar with working with new technology & tools
 
|  
 
|  
Line 117: Line 117:
 
| style="background: #C8BBBE;" colspan="7" | Scope Risk
 
| style="background: #C8BBBE;" colspan="7" | Scope Risk
 
|-  
 
|-  
| style="text-align: center;" 6
+
| style="text-align: center;" |6
 
| Sponsor changes his requirements frequently
 
| Sponsor changes his requirements frequently
 
|  
 
|  
Line 130: Line 130:
 
|  
 
|  
 
|-
 
|-
| style="text-align: center;" 7
+
| style="text-align: center;" |7
 
| Team overpromising new features
 
| Team overpromising new features
 
|  
 
|  
Line 143: Line 143:
  
 
|-
 
|-
| style="text-align: center;" 8
+
| style="text-align: center;" |8
 
| There is a critical bug that affects the core functionalities
 
| There is a critical bug that affects the core functionalities
 
|  
 
|  
Line 157: Line 157:
  
 
|-
 
|-
| style="text-align: center;" 9
+
| style="text-align: center;" |9
 
| Team members have other commitments and different priorities  
 
| Team members have other commitments and different priorities  
 
|  
 
|  

Revision as of 19:36, 27 September 2012

Home

Team/Project Partners

Project Overview

Project Management

Design Specifications

Technical Applications


Project Schedule Methodology Schedule & Bug Metrics Gender Recognition 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 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
3 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
4 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.
5 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
6 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
7 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
8 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
9 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