Project Plan Post 3 of 7: Risk Analysis and Success Plan

Risk	Probability (1-5)	Severity (1-5)	Score (P x S)	Action to Reduce/Manage Risk
Staffing: Loss of key project staff	2	3	6	Ensure technical implementation and design are well-documented so that alternative staff can take over.
Technical: Failure of hardware or supporting software	1	3	3	Use of operationally hosted/managed servers and replaceable virtual server hosting where possible; maintain good communication with staff managing servers.
Legal: IPR	1	1	1	No IPR difficulties are anticipated as the project is undertaking technical development based on code written and owned by the LSE Project Team and already covered by Creative Commons license.
Organisational: Difficulty in recruiting sufficient numbers to join test user panels	2	4	8	Local staff with existing relationships with potential user panel members are engaged with the project. Budget allows for some incentives for participation.
Organisational: User testing is held up by unpredicted delays in technical development	1	5	5	First stages of user testing are on concepts/language only. Subsequent stages are dependent only on implementation of HTML 'controls' - not fully functioning webservices.
Technical: tools fail to provide minimum required functionality	1	5	5	Development entirely in-house with no external dependencies; Development work will be organised to be as incremental as possible
Technical: tools developed prove impossible to integrate with other services	1	5	5	The design of the tools developed will use standards and mechanisms already proven to integrate with a wide variety of services