IS480 Team wiki: 2012T1 M.O.O.T/Project Management/Risk Management

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 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
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
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

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
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