Difference between revisions of "AY1516 T2 Team Skulptors - Risk Management"
Jump to navigation
Jump to search
(Created page with "<!--Main Navigation--> <center> {|style="background-color:#ffffff; color:#000000; width="100%" cellspacing="0" cellpadding="10" border="0" | |style="font-size:90%; border-left...") |
|||
| Line 41: | Line 41: | ||
<table rules="all" width="90%" cellpadding="6" cellspacing="3" style="margin: 1em auto 1em auto; font-weight: normal; border-style: solid; align: center; border:1"> | <table rules="all" width="90%" cellpadding="6" cellspacing="3" style="margin: 1em auto 1em auto; font-weight: normal; border-style: solid; align: center; border:1"> | ||
<tr style="background-color:#E1F4FF;"><th width="27%">Risk Type & Description</th><th width="27%">Consequences</th><th width="6%">Likelihood</th><th width="6%">Impact</th><th width="6%">Level</th><th width="28%">Mitigation</th></tr> | <tr style="background-color:#E1F4FF;"><th width="27%">Risk Type & Description</th><th width="27%">Consequences</th><th width="6%">Likelihood</th><th width="6%">Impact</th><th width="6%">Level</th><th width="28%">Mitigation</th></tr> | ||
| − | <tr><td><b>Technical Risk</b><br/> | + | <tr><td><b>Technical Risk</b><br/><br/> |
Steep learning curve as team are unfamiliar with D3.JS and JMP.</td> | Steep learning curve as team are unfamiliar with D3.JS and JMP.</td> | ||
<td>Project may be delayed due to: | <td>Project may be delayed due to: | ||
| Line 50: | Line 50: | ||
* Start exploration of D3.JS and JMP. | * Start exploration of D3.JS and JMP. | ||
* Seek help from seniors who have experience with D3.JS and JMP to expedite learning. | * Seek help from seniors who have experience with D3.JS and JMP to expedite learning. | ||
| + | </td></tr> | ||
| + | <tr><td><b>Technical Risk</b><br/><br/> | ||
| + | Team members have not taken IS428 - Visual Analytics for Business Intelligence (VA) module.</td> | ||
| + | <td>Team may be unsure of the best practices of information graphics to present data in the language of graphics effectively, clearly and eloquently.</td> | ||
| + | <td align="center">High</td><td align="center">Medium</td><td align="center">A</td> | ||
| + | <td> | ||
| + | * Obtain and view past VA projects from its wiki page to have an overview of how data are displayed effectively. | ||
| + | * Seek help from peers who have taken VA. | ||
| + | </td></tr> | ||
| + | <tr><td><b>Client Management Risk</b><br/><br/> | ||
| + | Client may be making frequent changes to the project scope.</td> | ||
| + | <td>Project may be delayed due to frequent readjustment of project scope and expectation may lead to an over-run in project.</td> | ||
| + | <td align="center">Medium</td><td align="center">Medium</td><td align="center">B</td> | ||
| + | <td> | ||
| + | * Team to schedule regular meetings with clients to keep up to date with latest information. | ||
| + | </td></tr> | ||
| + | <tr><td><b>Project Management Risk</b><br/><br/> | ||
| + | There are certain features such as warehouse utilization tool, which the team are unsure of the time needed to complete it.</td> | ||
| + | <td>Project may be delayed due to incorrect estimation of time can lead to the feature not being completed on time.</td> | ||
| + | <td align="center">Medium</td><td align="center">Medium</td><td align="center">B</td> | ||
| + | <td> | ||
| + | * Team lead to ensure regular meetings to gather feedback from all members on the project’s progress. | ||
| + | * Team to ask client’s technical team on tips to approach such unfamiliar feature. | ||
</td></tr> | </td></tr> | ||
Revision as of 22:43, 10 January 2016
 HOME
|
 ABOUT US
|
 PROJECT OVERVIEW
|
 PROJECT MANAGEMENT
|
 DOCUMENTATION
|
| Project Schedule | Risk Management |
Risk Metric
| Likelihood | ||||
|---|---|---|---|---|
| Low | Medium | High | ||
| Imp a c t | High | B | A | A |
| Medium | C | B | A | |
| Low | C | C | A | |
Risk Assessment
| Risk Type & Description | Consequences | Likelihood | Impact | Level | Mitigation |
|---|---|---|---|---|---|
| Technical Risk Steep learning curve as team are unfamiliar with D3.JS and JMP. |
Project may be delayed due to:
|
High | High | A |
|
| Technical Risk Team members have not taken IS428 - Visual Analytics for Business Intelligence (VA) module. |
Team may be unsure of the best practices of information graphics to present data in the language of graphics effectively, clearly and eloquently. | High | Medium | A |
|
| Client Management Risk Client may be making frequent changes to the project scope. |
Project may be delayed due to frequent readjustment of project scope and expectation may lead to an over-run in project. | Medium | Medium | B |
|
| Project Management Risk There are certain features such as warehouse utilization tool, which the team are unsure of the time needed to complete it. |
Project may be delayed due to incorrect estimation of time can lead to the feature not being completed on time. | Medium | Medium | B |
|
