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 46: Line 46:
 
=== Risk Management ===
 
=== Risk Management ===
  
 +
==== Future Risks ====
 +
{| class="wikitable"
 +
|-
 +
| style="background: #C082FF; text-align: center;" | <b>S/N</b>
 +
| style="background: #C082FF; text-align: center;" | <b>Risk Statement</b>
 +
| style="background: #C082FF; text-align: center;" | <b>Impact</b>
 +
| style="background: #C082FF; text-align: center;" | <b>Likelihood</b>
 +
| style="background: #C082FF; text-align: center;" | <b>Impact Level</b>
 +
| style="background: #C082FF; text-align: center;" | <b>Mitigation Strategy</b>
 +
| style="background: #C082FF; text-align: center;" | <b>Status</b>
 +
|-
 +
| style="background: #C8BBBE;" colspan="7" | Resource Risk
 +
|-
 +
| style="text-align: center;" |1
 +
| No available server storage for photos taken
 +
|
 +
* Inability to complete meaningful photo taking feature
 +
| High
 +
| High
 +
|
 +
* Search for complimentary storage
 +
* Make codes modular and dynamic in terms of storing photos
 +
* Utilize personal cloud storage account for this proof-of-concept
 +
|
 +
 +
|-
 +
| style="text-align: center;" |2
 +
| Unavailability of Internet connection to transfer photos from deployment machine to storage server
 +
|
 +
* Inability of shoppers to download their photos
 +
| Low
 +
| High
 +
|
 +
* For offline mode: upload photos manually to mall social networking page accessible by shoppers
 +
* Implement File Transfer Protocol (FTP) to enable transferring of photos through internal network
 +
|
 +
 +
|}
 +
 +
==== Resolved Risks ====
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-

Revision as of 22:13, 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

Future Risks

S/N Risk Statement Impact Likelihood Impact Level Mitigation Strategy Status
Resource Risk
1 No available server storage for photos taken
  • Inability to complete meaningful photo taking feature
High High
  • Search for complimentary storage
  • Make codes modular and dynamic in terms of storing photos
  • Utilize personal cloud storage account for this proof-of-concept
2 Unavailability of Internet connection to transfer photos from deployment machine to storage server
  • Inability of shoppers to download their photos
Low High
  • For offline mode: upload photos manually to mall social networking page accessible by shoppers
  • Implement File Transfer Protocol (FTP) to enable transferring of photos through internal network

Resolved Risks

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
  • Halt current development and focus on debugging
  • Forecast the features able to be completed & inform client of functionalities which cannot be completed
  • Core functionality is tested thoroughly before proceeding
  • Core functionality (gender recognition) is functioning at the moment
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