:: redSpot :: Risk Management Plan

	A	B	C	D	E	F	G	H
1	Risk Management Plan							(updated as of 20 Feb 2012)
2	No.	Risk Type	Risk Statement	Impact Level	Probability	Risk Exposure Level and Description		Mitigation Strategies

3	1	Technical	Working with new technologies and tools. i.e. iPad, PhoneGap, XCodes	3	3	5(High)	The team members may be overdependent on the strong coders, this may cause uneven distribution of work and a delay of the project tasks.	- Cater a dedicated research Phase for the technologies (Iteration 1) - Lead developer to pass the knowledge to all the other team members (AY2011/12 Term 1 Week 8) - Way ahead if necessary>> Pair programming according to the coding capabilities, such that the strong coders will be paired with the weaker ones so that everyone will learn from one another
4	2	Technical	Development and production environment may be different. (PhoneGap VS iPad)	2	3	4(Medium)	Delay in project delivery as the team have to do more debugging, and to solve several configuration issues	- Deploy to iPad early and try to resolve any issues that we encounter as soon as possible.
5	3	Project Management	Different priorities and schedules of team members	2	1	2 (Low)	Due to lack of communications, misunderstandings may occur and hence it may delay our project schedule.	- Set a common meeting slot that is agreed by all members - Compromise schedule to cater to weekly meetings where everyone must be present - Set a agenda for every meeting so that the meetings are efficient - Communicate and align individual members' priorities and project priorities.
6	4	Project Management	Could not complete basic functionality request by client	4	1	4 (Medium)	All the team member faced problem in their individual task and delay the project schedule planned.	- Re-allocation manpower to work on the unresolved tasks. - Approach professor or peers on how to resolve the issues.
7	5	External	Changes of requirements by the client during the course of project	2	3	4 (Medium)	Application may not be what the client wanted.	- Team will meet up with the client every week to provide updates and make changes accordingly. - Use iterative development process - Increase sponsor involvement
8	6	External	Could not get enough UAT users to test our project	3	3	5 (High)	UAT usually happens near exam periods, students are more reluctant to participant in user testing, especially our UAT requires participants to travel around different locations for testing	- Team will approach school or course which have field trips so as to leverage on the trip to do UAT, in particular, MGMT304, arranging with the TA so as to make proper adjustment based on his/her inputs for our use cases. - Schedule the development process in accordance with MGMT304 Course Outline, and communicate with the TA for the planning of the execution. - Team will need to design short and specific task for user testing to meet the UAT objective and ensure that UAT will be a short and interactive to attract and convince friends to take part in the UAT.
9	7	External	Phones must be added to a list of approved devices by school in order to be use for UAT testing	3	3	5(High)	UAT requires several groups of students to carry their own mobile devices to perform the UAT testing moving from one waypoint to another. However, for iOS devices, it requires the device to be registered and tagged to a developer account which requires school approval. The school may not be possible to authorize so many devices, thus it may possibly affects the conduct of UAT.	- Upload the application into the App store, but the process is stringent and long - Utilized the 6 designated iPads made available by eLearn pre-loaded with the app for the testers to use during UAT
10	8	External	Unforeseen server inactivity	4	3	5(High)	Unforeseen server down will cause all activity related not able to work.	Request for public IP address
11	9	External	Unable to loan 6 iPads needed for UAT 1	2	2	3(Medium)	The 6 iPads from the school might have been borrowed by other Professors and not available.	- Borrowed 2 Motorola Milestone 2 Android phones from school. - In our own FYP team, we have 3 users of iPhones and 2 users of Android phones, which we will deploy in all of them for use and testing purposes.
12	10	Technical	Fail to take into consideration server capacity for multiple access usage, thus causing latency and error for the mobile application discovered during UAT 1.	4	2	5(High)	Application was not able to launch or faced error when using.	Team will re-design the architecture such that there will be less interaction with the server.
13	11	Project Management	Unable to meet the planned UAT2 milestone with a fully deploy solution	4	1	4 (Medium)	Unable to meet the planned objective due to unforeseen architecture issue	Adjust schedule and re-assigned roles and responsibilities.
14	12	External	Unexpected intermittent server downtime	4	3	5(High)	Unforeseen server down will cause all activity related not able to work.	Purchased another server for backup.
15	13	Technical	Cross-browser compatibility	4	3	5(High)	Functions that worked in iOS might not work in Android and vice versa	To test rigorously after every function to ensure all is functioning well
16	14	Project Management	Change in mobile architecture	3	2	4(Medium)	Unable to meet project deadline due to change in mobile architecture	Included the mobile architecture restructuring as part of the project timeline
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99