IS480 Team wiki: 2012T1 Timber Werkz Risks

HOME

PROJECT OVERVIEW

PROJECT MANAGEMENT

DOCUMENTATION

Latest Events Notifications Progress

Project Description Stakeholders About Us

Schedule & Scope Milestones Metrics

Risks Framework Deliverables

Meeting Minutes Diagrams UI & Videos

Usability Tests Resources Learning Exp

<< MID-TERM WIKI          << FINAL WIKI

Risks & Mitigation

The following diagram shows the prioritised risks and mitigation table for the project.

S/N	Risk Description	Impact	Impact Level (High/Med/Low)	Likelihood (High/Med/Low)	Mitigation Strategy	Status
1	Project Management
1.1	Underestimation of Man Days for a Chapter	Project Schedule is delayed	High	High	Plan for buffer time for each sprint. In addition, Project Manager gets quick updates from developers regarding their status	Mitigation strategy in force
1.2 (New as at MidTerm)	Many issues might be raised during Usability Tests 1 and 2; time is required to rectify these issues	Project Schedule is delayed	Medium	High	A Response Plan Document is created to help us decided whether to implement a change based on priority, complexity and time needed to rectify the issues. View Response Plan (Artistes) & Response Plan (Casting Managers)	Mitigation strategy in force
2	Client Management
2.1	Change requests expected from client as Casting3 application is built from scratch	Change requests may affect the scope and schedule of the project	High	High	A Change Request Log is created to manage change requests more effectively.	Mitigation strategy in force
2.2	Clients do not know the exact requirements of the new application	Application may not serve the needs of the company effectively	High	Medium	Using Low fidelity prototype (UI mockups) to communicate and ensure that requirements are properly understood. helps to eliminate unnecessary wastage of time developing what may not be the clients' needs	Mitigation strategy in force
3	Team Management
3.1	Insufficient manpower during Milestone 1 as three members are overseas (summer studies and community service)	Possible delay in schedule. Members may be unaware of latest issues	Medium	Medium	Regular communication and updates of current happenings via meeting minutes in Google docs and messaging channels.	Risk eliminated
3.2	Conflict amongst team members in terms of working behviours and perspectives	Team's efficiency is compromised. Possible compromise in project quality and schedule	Medium	Low	Respect the views of other team members. If a conflict arise, conduct a meeting to "trash" out situations and resolve issues within the same day if possible.	Mitigation strategy in force
4	Technological Implementation
4.1	Members unfamiliar to technologies used (e.g. Yii framework, PHPUnit testing, and Youtube API).	Insufficient skilled members to value-add to the project	Medium	Medium	Organise knowledge sharing sessions amongst team members.	Mitigation strategy in force
4.2	Unsure if a particular feature can be developed with current technologies.	The extent where the application can value-add to the business might be affected	Medium	Medium	Develop Proof-Of-Concepts for such features (Search, Crop Photo).	Mitigation strategy in force
4.3	Project contains numerous documentation and different versions. Inefficent access to a particular document.	Accuracy of information used is compromised	Medium	Low	Use a collaborative file management software (e.g. Google Documents) to organise respective folders of the project. Consensus amongst team members to adhere to proper version labelling.	Risk eliminated