Difference between revisions of "IS480 Team wiki: 2012T1 Timber Werkz Risks"
Jump to navigation
Jump to search
(28 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
<!--Navigation Bar--> | <!--Navigation Bar--> | ||
− | {| style="background-color:#FFFFFF; color:#000000 padding: | + | {| style="background-color:#FFFFFF; color:#000000 padding: 0px 0 0 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" align="center" border="0" font face="Calibri" | |
+ | | style="padding:0.6em; font-size:110%; background-color:#ffffff; border-bottom:2px solid #632E00; text-align:center; " width="10%" | [[IS480_Team_wiki:_2012T1_Timber_Werkz|<font color="#c93756"><b>HOME</b><font>]] | ||
+ | | style=" border-bottom:2px solid #632E00; background:none;" width="2%" | | ||
+ | | style="padding:0.6em; font-size:110%; background-color:#ffffff; border-bottom:2px solid #632E00; text-align:center; color:#000000" width="12%" |<font color="#c93756"><b>PROJECT OVERVIEW</b><font> | ||
+ | | style="border-bottom:2px solid #632E00; background:none;" width="2%" | | ||
+ | | style="border-bottom:2px solid #632E00; background:none;" width="2%" | | ||
+ | | style="padding:0.6em; font-size:110%; background-color:#ffffff; border-bottom:2px solid #632E00; text-align:center; color:#000000" width="24%" |<font color="#c93756"><b>PROJECT MANAGEMENT</b><font> | ||
+ | | style="border-bottom:2px solid #632E00; background:none;" width="2%" | | ||
+ | | style="padding:0.6em; font-size:110%; background-color:#ffffff; border-bottom:2px solid #632E00; text-align:center; color:#000000" width="24%" |<font color="#c93756"><b>DOCUMENTATION</b><font> | ||
+ | | style="border-bottom:2px solid #632E00; background:none;" width="2%" | | ||
− | | | + | |} |
− | |||
− | | style=" | + | {| style="background-color:#FFFFFF; color:#000000 padding: 2px 0 0 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" align="center" border="0" font face="Calibri" | |
− | |||
− | | style="padding:0.6em; font-size: | + | | style="padding:0 .6em; font-size:100%; background-color:#ffffff; border-bottom:2px solid #806517; text-align:left; " width="10%" | |
− | | style="border-bottom:2px solid # | + | *[[IS480_Team_wiki:_2012T1_Timber_Werkz#Latest_Events|<font color="#0040FF" face="">'''Latest Events'''</font>]] |
+ | *[[IS480_Team_wiki:_2012T1_Timber_Werkz#Notifications |<font color="#0040FF" face="">'''Notifications'''</font>]] | ||
+ | *[[IS480_Team_wiki:_2012T1_Timber_Werkz#Project_Progress |<font color="#0040FF" face="">'''Progress'''</font>]] | ||
+ | | style="border-bottom:2px solid #806517;background:none;" width="2%" | | ||
− | | style="padding:0 .6em | + | | style="padding:0.6em; font-size:100%; background-color:#ffffff; border-bottom:2px solid #806517; text-align:left; color:#000000" width="12%" | |
− | | style="border-bottom:2px solid # | + | *[[IS480_Team_wiki:_2012T1_Timber_Werkz_ProjectOverview|<font color="#0040FF" face="">'''Project Description'''</font>]] |
+ | *[[IS480_Team_wiki:_2012T1_Timber_Werkz_ProjectStakeholders|<font color="#0040FF" face="">'''Stakeholders'''</font>]] | ||
+ | *[[IS480_Team_wiki:_2012T1_Timber_Werkz_IntroducingTW|<font color="#0040FF" face="">'''About Us'''</font>]] | ||
+ | | style="border-bottom:2px solid #806517; background:none;" width="2%" | | ||
− | | style="padding:0.6em; font-size: | + | | style="padding:0.6em; font-size:100%; background-color:#ffffff; border-bottom:2px solid #806517; text-align:left; color:#000000" width="12%" | |
− | | style="border-bottom:2px solid # | + | *[[IS480_Team_wiki:_2012T1_Timber_Werkz_ProjectManagement|<font color="#0040FF" face="">'''Schedule & Scope'''</font>]] |
+ | *[[IS480_Team_wiki:_2012T1_Timber_Werkz_Milestones|<font color="#0040FF" face="">'''Milestones'''</font>]] | ||
+ | *[[IS480_Team_wiki:_2012T1_Timber_Werkz_Metrics|<font color="#0040FF" face="">'''Metrics'''</font>]] | ||
+ | | style="border-bottom:2px solid #806517; background:none;" width="2%" | | ||
− | | style="padding:0.6em; font-size: | + | | style="padding:0.6em; font-size:100%; background-color:#ffffff; border-bottom:2px solid #806517; text-align:left; color:#000000" width="12%" | |
+ | *[[IS480_Team_wiki:_2012T1_Timber_Werkz_Risks|<font color="#0040FF" face="">'''Risks'''</font>]] | ||
+ | *[[IS480_Team_wiki:_2012T1_Timber_Werkz_ProjectFramework|<font color="#0040FF" face="">'''Framework'''</font>]] | ||
+ | *[[IS480_Team_wiki:_2012T1_Timber_Werkz_Deliverables |<font color="#0040FF" face="">'''Deliverables'''</font>]] | ||
+ | | style="border-bottom:2px solid #806517; background:none;" width="2%" | | ||
− | | style="padding:0.6em; font-size: | + | | style="padding:0.6em; font-size:100%; background-color:#ffffff; border-bottom:2px solid #806517; text-align:left; color:#000000" width="12%" | |
+ | *[[IS480_Team_wiki:_2012T1_Timber_Werkz_ProjectDocumentation|<font color="#0040FF" face="">'''Meeting Minutes'''</font>]] | ||
+ | *[[IS480_Team_wiki:_2012T1_Timber_Werkz_TechDiagrams |<font color="#0040FF" face="">'''Diagrams'''</font>]] | ||
+ | *[[IS480_Team_wiki:_2012T1_Timber_Werkz_UI |<font color="#0040FF" face="">'''UI & Videos'''</font>]] | ||
+ | | style="border-bottom:2px solid #806517;background:none;" width="2%" | | ||
+ | | style="padding:0.6em; font-size:100%; background-color:#ffffff; border-bottom:2px solid #806517; text-align:left; color:#000000" width="12%" | | ||
+ | *[[IS480_Team_wiki:_2012T1_Timber_Werkz_UsabilityTest |<font color="#0040FF" face="">'''Usability Tests'''</font>]] | ||
+ | *[[IS480_Team_wiki:_2012T1_Timber_Werkz_ProjectResources |<font color="#0040FF" face="">'''Resources'''</font>]] | ||
+ | *[[IS480_Team_wiki:_2012T1_Timber_Werkz_LearningExp |<font color="#0040FF" face="">'''Learning Exp'''</font>]] | ||
|} | |} | ||
+ | <br> | ||
+ | <big>[[IS480_Team_wiki:_2012T1_Timber_Werkz_MidTerm_Wiki|<font color="#4D268F" face=""><ins>'''<< MID-TERM WIKI'''</ins></font>]]</big> <big>[[IS480_Team_wiki:_2012T1_Timber_Werkz_Final_Wiki|<font color="#D00303" face=""><ins>'''<< FINAL WIKI'''</ins></font>]]</big> | ||
+ | <br><br> | ||
+ | <!--body--> | ||
+ | ==<font color="#c93756">'''Risks & Mitigation'''</font>== | ||
+ | <p>The following diagram shows the prioritised risks and mitigation table for the project.</p> | ||
+ | <br> | ||
+ | {| class="wikitable" style="text-align: center; height:80px" | ||
+ | |+ | ||
+ | |- | ||
+ | ! scope="col" width="50" style="background-color:#D31601"| <font color="#ffffff">S/N</font> | ||
+ | ! scope="col" width="350" style="background-color:#D31601"| <font color="#ffffff">Risk Description</font> | ||
+ | ! scope="col" width="250" style="background-color:#D31601"| <font color="#ffffff">Impact</font> | ||
+ | ! scope="col" width="120" style="background-color:#D31601"| <font color="#ffffff">Impact Level <br> (High/Med/Low)</font> | ||
+ | ! scope="col" width="120" style="background-color:#D31601"| <font color="#ffffff">Likelihood <br> (High/Med/Low)</font> | ||
+ | ! scope="col" width="500" style="background-color:#D31601"| <font color="#ffffff">Mitigation Strategy</font> | ||
+ | ! scope="col" width="100" style="background-color:#D31601"| <font color="#ffffff">Status</font> | ||
+ | |- | ||
− | + | !scope="row" style="background-color:#FAFDC3"| | |
+ | '''1''' | ||
+ | |colspan="6" height:100px; style="background-color:#FAFDC3; text-align: left;"| | ||
+ | '''Project Management''' | ||
+ | |- | ||
− | | style=" | + | ! scope="row" | |
+ | '''1.1''' | ||
+ | |style="text-align: left;"| | ||
+ | *Underestimation of Man Days for a Chapter | ||
+ | |style="text-align: left;"| | ||
+ | *Project Schedule is delayed | ||
+ | |style="text-align: center;"| | ||
+ | High | ||
+ | |style="text-align: center;"| | ||
+ | High | ||
+ | |style="text-align: left;"| | ||
+ | *Plan for buffer time for each sprint. In addition, Project Manager gets quick updates from developers regarding their status | ||
+ | |style="text-align: center; color:#D31601"| | ||
+ | '''Mitigation strategy <br> in force''' | ||
+ | |- | ||
− | | style=" | + | ! scope="row" | |
+ | '''1.2<br>(New <br>as at MidTerm)''' | ||
+ | |style="text-align: left;"| | ||
+ | *Many issues might be raised during Usability Tests 1 and 2; time is required to rectify these issues | ||
+ | |style="text-align: left;"| | ||
+ | *Project Schedule is delayed | ||
+ | |style="text-align: center;"| | ||
+ | Medium | ||
+ | |style="text-align: center;"| | ||
+ | High | ||
+ | |style="text-align: left;"| | ||
+ | *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 [https://docs.google.com/spreadsheet/ccc?key=0AskT4ENrBtHIdDNkOVdVWllrM0tyX3BqMHdCRkh1akE#gid=1 Response Plan (Artistes)] & [https://docs.google.com/spreadsheet/ccc?key=0AskT4ENrBtHIdGhOVUFnTk1TQmFxVHpiOVdySWVQdnc#gid=0 Response Plan (Casting Managers)] | ||
+ | |style="text-align: center; color:#D31601"| | ||
+ | '''Mitigation strategy <br> in force''' | ||
+ | |- | ||
− | | style=" | + | !scope="row" style="background-color:#FAFDC3"| |
+ | '''2''' | ||
+ | |colspan="6" height:100px; style="background-color:#FAFDC3; text-align: left;"| | ||
+ | '''Client Management''' | ||
+ | |- | ||
+ | ! scope="row" | | ||
+ | '''2.1''' | ||
+ | |style="text-align: left;"| | ||
+ | *Change requests expected from client as Casting3 application is built from scratch | ||
+ | |style="text-align: left;"| | ||
+ | *Change requests may affect the scope and schedule of the project | ||
+ | |style="text-align: center;"| | ||
+ | High | ||
+ | |style="text-align: center;"| | ||
+ | High | ||
+ | |style="text-align: left;"| | ||
+ | *A [https://docs.google.com/spreadsheet/ccc?key=0AuNjOu2GtpU7dFB0TmhtSkJSRzNPWlA4eE1FaWloMkE#gid=15 Change Request Log] is created to manage change requests more effectively. | ||
+ | |style="text-align: center; color:#D31601"| | ||
+ | '''Mitigation strategy <br> in force''' | ||
− | | style=" | + | |- |
+ | ! scope="row" | | ||
+ | '''2.2''' | ||
+ | |style="text-align: left;"| | ||
+ | *Clients do not know the exact requirements of the new application | ||
+ | |style="text-align: left;"| | ||
+ | *Application may not serve the needs of the company effectively | ||
+ | |style="text-align: center;"| | ||
+ | High | ||
+ | |style="text-align: center;"| | ||
+ | Medium | ||
+ | |style="text-align: left;"| | ||
+ | *Using [http://bit.ly/prototype_1 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 | ||
+ | |style="text-align: center; color:#D31601"| | ||
+ | '''Mitigation strategy <br> in force''' | ||
+ | |- | ||
+ | |- | ||
− | + | !scope="row" style="background-color:#FAFDC3"| | |
+ | '''3''' | ||
+ | |colspan="6" height:100px; style="background-color:#FAFDC3; text-align: left;"| | ||
+ | '''Team Management''' | ||
+ | |- | ||
− | | | + | ! scope="row" | |
+ | '''3.1''' | ||
+ | |style="text-align: left;"| | ||
+ | *Insufficient manpower during Milestone 1 as three members are overseas (summer studies and community service) | ||
+ | |style="text-align: left;"| | ||
+ | *Possible delay in schedule. Members may be unaware of latest issues | ||
+ | |style="text-align: center;"| | ||
+ | Medium | ||
+ | |style="text-align: center;"| | ||
+ | Medium | ||
+ | |style="text-align: left;"| | ||
+ | *Regular communication and updates of current happenings via meeting minutes in Google docs and messaging channels. | ||
+ | |style="text-align: center; color:#008000"| | ||
+ | '''Risk eliminated''' | ||
+ | |- | ||
− | + | ! scope="row" | | |
− | + | '''3.2''' | |
− | ---- | + | |style="text-align: left;"| |
− | + | *Conflict amongst team members in terms of working behviours and perspectives | |
− | + | |style="text-align: left;"| | |
− | + | *Team's efficiency is compromised. Possible compromise in project quality and schedule | |
− | + | |style="text-align: center;"| | |
+ | Medium | ||
+ | |style="text-align: center;"| | ||
+ | Low | ||
+ | |style="text-align: left;"| | ||
+ | *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. | ||
+ | |style="text-align: center; color:#D31601"| | ||
+ | '''Mitigation strategy <br> in force''' | ||
|- | |- | ||
− | ! scope=" | + | |
− | + | !scope="row" style="background-color:#FAFDC3"| | |
− | + | '''4''' | |
+ | |colspan="6" height:100px; style="background-color:#FAFDC3; text-align: left;"| | ||
+ | '''Technological Implementation''' | ||
|- | |- | ||
− | ! scope="row" | ''' | + | |
+ | ! scope="row" | | ||
+ | '''4.1''' | ||
|style="text-align: left;"| | |style="text-align: left;"| | ||
− | + | *Members unfamiliar to technologies used (e.g. Yii framework, PHPUnit testing, and Youtube API). | |
− | + | |style="text-align: left;"| | |
+ | *Insufficient skilled members to value-add to the project | ||
+ | |style="text-align: center;"| | ||
+ | Medium | ||
+ | |style="text-align: center;"| | ||
+ | Medium | ||
|style="text-align: left;"| | |style="text-align: left;"| | ||
− | + | *Organise knowledge sharing sessions amongst team members. | |
+ | |style="text-align: center; color:#D31601"| | ||
+ | '''Mitigation strategy <br> in force''' | ||
|- | |- | ||
− | ! scope="row" | | + | ! scope="row" | |
+ | '''4.2''' | ||
|style="text-align: left;"| | |style="text-align: left;"| | ||
− | + | *Unsure if a particular feature can be developed with current technologies. | |
− | + | |style="text-align: left;"| | |
+ | *The extent where the application can value-add to the business might be affected | ||
+ | |style="text-align: center;"| | ||
+ | Medium | ||
+ | |style="text-align: center;"| | ||
+ | Medium | ||
|style="text-align: left;"| | |style="text-align: left;"| | ||
− | + | *Develop Proof-Of-Concepts for such features (Search, Crop Photo). | |
+ | |style="text-align: center; color:#D31601"| | ||
+ | '''Mitigation strategy <br> in force''' | ||
|- | |- | ||
− | ! scope="row" | | + | |
+ | ! scope="row" | | ||
+ | '''4.3''' | ||
|style="text-align: left;"| | |style="text-align: left;"| | ||
− | + | *Project contains numerous documentation and different versions. Inefficent access to a particular document. | |
− | + | |style="text-align: left;"| | |
+ | *Accuracy of information used is compromised | ||
+ | |style="text-align: center;"| | ||
+ | Medium | ||
+ | |style="text-align: center;"| | ||
+ | Low | ||
|style="text-align: left;"| | |style="text-align: left;"| | ||
− | + | *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. | |
− | + | |style="text-align: center; color:#008000"| | |
+ | '''Risk eliminated''' | ||
|} | |} |
Latest revision as of 11:55, 27 November 2012
HOME | PROJECT OVERVIEW | PROJECT MANAGEMENT | DOCUMENTATION |
<< 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 |
|
|
High |
High |
|
Mitigation strategy |
1.2 |
|
|
Medium |
High |
|
Mitigation strategy |
2 |
Client Management | |||||
2.1 |
|
|
High |
High |
|
Mitigation strategy |
2.2 |
|
|
High |
Medium |
|
Mitigation strategy |
3 |
Team Management | |||||
3.1 |
|
|
Medium |
Medium |
|
Risk eliminated |
3.2 |
|
|
Medium |
Low |
|
Mitigation strategy |
4 |
Technological Implementation | |||||
4.1 |
|
|
Medium |
Medium |
|
Mitigation strategy |
4.2 |
|
|
Medium |
Medium |
|
Mitigation strategy |
4.3 |
|
|
Medium |
Low |
|
Risk eliminated |