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 68: Line 68:
 
* 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
|  
+
|
 +
* Measurement taking provided us with clues of physical differences between male and female
 +
* Research supported primary findings from measurement taking sessions
 
* Neural Network with backward propagation made gender recognition possible
 
* Neural Network with backward propagation made gender recognition possible
* Gender recognition feature has been tested and worked at a minimum of 60% accuracy
+
* Gender recognition based on physical features has been tested and worked at a minimum of 60% accuracy
* Measurement taking provided us with clues of physical differences between male and female
 
* Research supported primary findings from measurement taking sessions
 
  
 
|-
 
|-
Line 78: Line 78:
 
| Accuracy of gender recognition
 
| Accuracy of gender recognition
 
|  
 
|  
* Development is delayed
+
* Low product quality
| High
+
| <strike>High</strike><br><span style="color: blue;">Medium</span>
| High
+
| <strike>High</strike><br><span style="color: blue;">Medium</span>
 
|  
 
|  
* Add more behaviour traits and characteristics as parameters to determine gender such as shape of clothes, heels elevation
+
* Add more behavioural traits and characteristics as parameters to determine gender such as shape of clothes or heels elevation
 
|  
 
|  
 +
* Accuracy is more than 80% in controlled environment, based solely on physical parameters
 +
* Based on the theory of Neural Network, adding behavioural parameters are likely to improve its accuracy
 +
 
|-
 
|-
 
|style="text-align: center;" |3
 
|style="text-align: center;" |3
Line 90: Line 93:
 
* Development is delayed  
 
* Development is delayed  
 
* Some features may have to be dropped
 
* Some features may have to be dropped
| High
+
| <strike>High</strike><br><span style="color: green;">Low</span>
| High
+
| <strike>High</strike><br><span style="color: green;">Low</span>
 
|  
 
|  
 
* Write our own gesture library
 
* Write our own gesture library
 
|  
 
|  
 +
* Confident of writing own gesture library after implementing grabbing of spear & jabbing for previous requirement
 +
 
|-
 
|-
 
| style="text-align: center;" |4
 
| style="text-align: center;" |4
Line 101: Line 106:
 
* Development is delayed  
 
* Development is delayed  
 
* Some features may have to be dropped
 
* Some features may have to be dropped
| High
+
| <strike>High</strike><br><span style="color: green;">Low</span>
| High
+
| <strike>High</strike><br><span style="color: green;">Low</span>
 
|  
 
|  
* Gather feedback consistently, assess written gestures and then decide whether to change them.
+
* 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.
+
* Watch videos of Kinect games to learn how to make better motion gestures
 
|  
 
|  
 +
* Minimum gestures required for photo taking feature
 +
 
|-
 
|-
 
| 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
 
|  
 
|  
*Development is delayed  
+
* Development is delayed  
 
* Schedule is affected
 
* Schedule is affected
| High
+
| <strike>High</strike><br><span style="color: green;">Low</span>
| High
+
| <strike>High</strike><br><span style="color: green;">Low</span>
 
|  
 
|  
 
* Allow sufficient time for each member to learn the new technology and tools  
 
* Allow sufficient time for each member to learn the new technology and tools  
 
* Arrange weekly sessions to review on progress
 
* Arrange weekly sessions to review on progress
 
|  
 
|  
 +
* Team is relatively familiar with Kinect SDK & C# now
 +
 
|-  
 
|-  
 
| style="background: #C8BBBE;" colspan="7" | Scope Risk
 
| style="background: #C8BBBE;" colspan="7" | Scope Risk
Line 128: Line 137:
 
* Schedule is affected
 
* Schedule is affected
 
| Medium
 
| Medium
| Medium
+
| <strike>Medium</strike><br><span style="color: green;">Low</span>
 
|  
 
|  
 
* Update sponsor consistently with the latest progress of project
 
* Update sponsor consistently with the latest progress of project
* Develop paper prototypes to ensure sponsor & team are on the same level of agreement
+
* Develop paper prototypes & proposal 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
+
* Divide huge tasks into smaller features that can be pushed out on a weekly basis
 
|  
 
|  
 +
* Completed confirmed features (gender recognition) first while re-negotiating scope
 +
* Scope was largely confirmed by the end of Iteration 2
 +
 
|-
 
|-
 
| style="text-align: center;" |7
 
| style="text-align: center;" |7
Line 139: Line 151:
 
|  
 
|  
 
* Schedule is affected
 
* Schedule is affected
 +
* Compromise on core features
 
| Medium
 
| Medium
| Medium
+
| <strike>Medium</strike><br><span style="color: green;">Low</span>
 
|  
 
|  
 
* Prioritize list of functions in client’s requirements list before coming to an agreement with him
 
* Prioritize list of functions in client’s requirements list before coming to an agreement with him
 
|
 
|
 +
* Photo taking has been confirmed as the most important feature for client
 +
 
|-  
 
|-  
 
| style="background: #C8BBBE;" colspan="7" | Development Risk
 
| style="background: #C8BBBE;" colspan="7" | Development Risk
Line 149: Line 164:
 
|-
 
|-
 
| 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 core functionalities
 
|  
 
|  
 
* Core functionalities are not working
 
* Core functionalities are not working
 
| High
 
| High
| High
+
| <strike>High</strike><br><span style="color: blue;">Medium</span>
 
|  
 
|  
* Team will halt current development and focus on debugging  
+
* Test core functionality thoroughly before proceeding
 +
* Halt current development and focus on debugging  
 
* Forecast the features able to be completed & inform client of functionalities which cannot be completed
 
* Forecast the features able to be completed & inform client of functionalities which cannot be completed
 
|  
 
|  
 +
*
 +
 
|-  
 
|-  
 
| style="background: #C8BBBE;" colspan="7" | Schedule Risk
 
| style="background: #C8BBBE;" colspan="7" | Schedule Risk
Line 167: Line 185:
 
*Team morale is low
 
*Team morale is low
 
| Medium
 
| Medium
| High
+
| <strike>High</strike><br><span style="color: green;">Low</span>
 
|  
 
|  
 
* Communicate & align individual member’s priorities & project priorities together  
 
* Communicate & align individual member’s priorities & project priorities together  
 
* Set clear tasks together as a team every week
 
* Set clear tasks together as a team every week
 
|  
 
|  
 +
* Mondays & Fridays have been allocated for meetings
 +
* Members to report on allocated task progress on every meeting, keeping members accountable
 
   
 
   
 
|}
 
|}

Revision as of 21:49, 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
Low
High
Low
  • Research on possible ways/algorithms to do gender recognition
  • Devise feasible way to determine gender
  • Learn, modify and integrate algorithm into application
  • Measurement taking provided us with clues of physical differences between male and female
  • Research supported primary findings from measurement taking sessions
  • Neural Network with backward propagation made gender recognition possible
  • Gender recognition based on physical features has been tested and worked at a minimum of 60% accuracy
2 Accuracy of gender recognition
  • Low product quality
High
Medium
High
Medium
  • Add more behavioural traits and characteristics as parameters to determine gender such as shape of clothes or heels elevation
  • Accuracy is more than 80% in controlled environment, based solely on physical parameters
  • Based on the theory of Neural Network, adding behavioural parameters are likely to improve its accuracy
3 No suitable gestures library that we can use
  • Development is delayed
  • Some features may have to be dropped
High
Low
High
Low
  • Write our own gesture library
  • Confident of writing own gesture library after implementing grabbing of spear & jabbing for previous requirement
4 Self-written motion gestures may be inaccurate/inconsistent/too difficult to perform.
  • Development is delayed
  • Some features may have to be dropped
High
Low
High
Low
  • 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
  • Minimum gestures required for photo taking feature
5 Team is unfamiliar with working with new technology & tools
  • Development is delayed
  • Schedule is affected
High
Low
High
Low
  • Allow sufficient time for each member to learn the new technology and tools
  • Arrange weekly sessions to review on progress
  • Team is relatively familiar with Kinect SDK & C# now
Scope Risk
6 Sponsor changes his requirements frequently
  • Core functionalities may not be able to be completed
  • Schedule is affected
Medium Medium
Low
  • Update sponsor consistently with the latest progress of project
  • Develop paper prototypes & proposal to ensure sponsor & team are on the same level of agreement
  • Divide huge tasks into smaller features that can be pushed out on a weekly basis
  • Completed confirmed features (gender recognition) first while re-negotiating scope
  • Scope was largely confirmed by the end of Iteration 2
7 Team overpromising new features
  • Schedule is affected
  • Compromise on core features
Medium Medium
Low
  • Prioritize list of functions in client’s requirements list before coming to an agreement with him
  • Photo taking has been confirmed as the most important feature for client
Development Risk
8 There is a critical bug that affects core functionalities
  • Core functionalities are not working
High High
Medium
  • Test core functionality thoroughly before proceeding
  • 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
Low
  • Communicate & align individual member’s priorities & project priorities together
  • Set clear tasks together as a team every week
  • Mondays & Fridays have been allocated for meetings
  • Members to report on allocated task progress on every meeting, keeping members accountable