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
 
(20 intermediate revisions by 2 users not shown)
Line 31: Line 31:
  
 
| style="font-size:90%; text-align:center;" width="10%" |[[ IS480 Team wiki: 2012T1 M.O.O.T/Project Management|<font color="#000000">Project Schedule</font>]]
 
| style="font-size:90%; text-align:center;" width="10%" |[[ IS480 Team wiki: 2012T1 M.O.O.T/Project Management|<font color="#000000">Project Schedule</font>]]
 
| style="font-size:90%; text-align:center;" width="10%" |[[ IS480 Team wiki: 2012T1 M.O.O.T/Project Management/Methodology|<font color="#000000">Methodology</font>]]
 
  
 
| style="font-size:90%; text-align:center;" width="10%" |[[ IS480 Team wiki: 2012T1 M.O.O.T/Project Management/Metrics|<font color="#000000">Schedule & Bug Metrics</font>]]
 
| style="font-size:90%; text-align:center;" width="10%" |[[ IS480 Team wiki: 2012T1 M.O.O.T/Project Management/Metrics|<font color="#000000">Schedule & Bug Metrics</font>]]
Line 46: Line 44:
 
=== 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 publicly-available server storage for photos taken
 +
|
 +
* Inability to complete meaningful photo taking feature
 +
* Inability to download photo
 +
| 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
 +
|
 +
*Personal cloud storage used as CMA is sourcing for its own alternative server storage
 +
*User experience is not compromised for now, but storage from CMA is required for future maintenance and sustainability
 +
 +
|-
 +
| 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 in real time
 +
| Low
 +
| <strike>High</strike><br><span style="color: green;">Low</span>
 +
|
 +
* 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
 +
|
 +
FTP has been implemented for such situation
 +
 +
|-
 +
| style="background: #C8BBBE;" colspan="7" | Schedule Risk
 +
|-
 +
| style="text-align: center;" |3
 +
| Inability to complete photo-taking narrative in time as two members will be unavailable in week 8
 +
|
 +
* Delay in schedule
 +
* Delay in development
 +
* Compromised narrative
 +
| Medium
 +
| High
 +
|
 +
* Allocate minimum coding tasks for the iteration: more of refinement
 +
* Iteration to last from week 8 to week 9, design for narrative can be started in week 8 and implemented in week 9
 +
|
 +
Resolved: project has been completed in time
 +
 +
|-
 +
| style="background: #C8BBBE;" colspan="7" | Usability Risk
 +
|-
 +
| style="text-align: center;" |4
 +
| Shoppers do not know how to respond to AlterSense
 +
|
 +
* Compromised shoppers' experience
 +
* Reduced value proposition of AlterSense
 +
| Low
 +
| Low
 +
|
 +
* Adopt familiar interface e.g. countdown timer for photo taking
 +
* Insertion of speech bubble besides shopper's head to inform shoppers on how to respond
 +
|
 +
*Instructions have been refined according to User Testing observation and feedback
 +
*Users picked up gestures quickly after the first one during UT2
 +
 +
|-
 +
| style="background: #C8BBBE;" colspan="7" | Technical Risk
 +
|-
 +
| style="text-align: center;" |5
 +
| iOS6 incompatibility with Microsoft Tag scanner prohibits users from scanning tag
 +
|
 +
*Compromised experience
 +
*Inability to access photo gallery
 +
|<strike>High</strike><br><span style="color: green;">Low</span>
 +
|<strike>Medium</strike><br><span style="color: green;">Low</span>
 +
|
 +
*Use Microsoft QR code
 +
*Research on reasons for incompatibility
 +
*Recommend updates to Microsoft
 +
|
 +
*New version compatible with iOS6 was launched in end October
 +
*Tested and working during UT2 on 5 November
 +
|-
 +
|}
 +
 +
==== Resolved Risks ====
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
Line 58: Line 152:
 
| 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
 
|  
 
|  
 
* Development is delayed
 
* Development is delayed
| High
+
| <strike>High</strike><br><span style="color: green;">Low</span>
| High
+
| <strike>High</strike><br><span style="color: green;">Low</span>
 
|  
 
|  
 
* 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
|  
+
|
 +
* 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
 +
 
 
|-
 
|-
| style="text-align: center;" 2
+
| style="text-align: center;" |2
 
| 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
 
| No suitable gestures library that we can use
 
| No suitable gestures library that we can use
 
|  
 
|  
 
* 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
 
| Self-written motion gestures may be inaccurate/inconsistent/too difficult to perform.
 
| Self-written motion gestures may be inaccurate/inconsistent/too difficult to perform.
 
|  
 
|  
 
* 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="text-align: center;" |6
 +
| Inability to refine overlaying of augmented background
 +
|
 +
* Compromised shoppers' experience
 +
| Low
 +
| <strike>Medium</strike><br><span style="color: green;">Low</span>
 +
|
 +
* Adopt sample codes of image overlaying more closely
 +
* Consult Team Bazinga from FYP AY1112T2 for tips on overlay refinement
 +
|
 +
* Outline has significantly been smoothed out
 
|-  
 
|-  
 
| style="background: #C8BBBE;" colspan="7" | Scope Risk
 
| style="background: #C8BBBE;" colspan="7" | Scope Risk
 
|-  
 
|-  
| style="text-align: center;" 6
+
| style="text-align: center;" |7
 
| Sponsor changes his requirements frequently
 
| Sponsor changes his requirements frequently
 
|  
 
|  
Line 123: Line 243:
 
* 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;" |8
 
| Team overpromising new features
 
| Team overpromising new features
 
|  
 
|  
 
* 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
  
 
|-
 
|-
| style="text-align: center;" 8
+
| style="text-align: center;" |9
| 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  
+
* 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
 
|  
 
|  
 +
* Core functionality is tested thoroughly before proceeding
 +
* Core functionality (gender recognition) is functioning at the moment
 +
 
|-  
 
|-  
 
| style="background: #C8BBBE;" colspan="7" | Schedule Risk
 
| style="background: #C8BBBE;" colspan="7" | Schedule Risk
  
 
|-
 
|-
| style="text-align: center;" 9
+
| style="text-align: center;" |10
 
| Team members have other commitments and different priorities  
 
| Team members have other commitments and different priorities  
 
|  
 
|  
 
*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
 
   
 
   
 
|}
 
|}

Latest revision as of 15:53, 30 November 2012

Home

Team/Project Partners

Project Overview

Project Management

Design Specifications

Technical Applications


Project Schedule 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 publicly-available server storage for photos taken
  • Inability to complete meaningful photo taking feature
  • Inability to download photo
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
  • Personal cloud storage used as CMA is sourcing for its own alternative server storage
  • User experience is not compromised for now, but storage from CMA is required for future maintenance and sustainability
2 Unavailability of Internet connection to transfer photos from deployment machine to storage server
  • Inability of shoppers to download their photos in real time
Low High
Low
  • 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

FTP has been implemented for such situation

Schedule Risk
3 Inability to complete photo-taking narrative in time as two members will be unavailable in week 8
  • Delay in schedule
  • Delay in development
  • Compromised narrative
Medium High
  • Allocate minimum coding tasks for the iteration: more of refinement
  • Iteration to last from week 8 to week 9, design for narrative can be started in week 8 and implemented in week 9

Resolved: project has been completed in time

Usability Risk
4 Shoppers do not know how to respond to AlterSense
  • Compromised shoppers' experience
  • Reduced value proposition of AlterSense
Low Low
  • Adopt familiar interface e.g. countdown timer for photo taking
  • Insertion of speech bubble besides shopper's head to inform shoppers on how to respond
  • Instructions have been refined according to User Testing observation and feedback
  • Users picked up gestures quickly after the first one during UT2
Technical Risk
5 iOS6 incompatibility with Microsoft Tag scanner prohibits users from scanning tag
  • Compromised experience
  • Inability to access photo gallery
High
Low
Medium
Low
  • Use Microsoft QR code
  • Research on reasons for incompatibility
  • Recommend updates to Microsoft
  • New version compatible with iOS6 was launched in end October
  • Tested and working during UT2 on 5 November

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
6 Inability to refine overlaying of augmented background
  • Compromised shoppers' experience
Low Medium
Low
  • Adopt sample codes of image overlaying more closely
  • Consult Team Bazinga from FYP AY1112T2 for tips on overlay refinement
  • Outline has significantly been smoothed out
Scope Risk
7 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
8 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
9 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
10 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