Difference between revisions of "IS480 Team wiki: 2013T2 Five&AHalfMen Project Management risk"
Snseah.2011 (talk | contribs) |
Snseah.2011 (talk | contribs) |
||
Line 133: | Line 133: | ||
<!--Resource:Mitigation--> | <!--Resource:Mitigation--> | ||
||<font style="font-family:Calibri;letter-spacing: 0.0em; font-size:16px; text-align:center"> | ||<font style="font-family:Calibri;letter-spacing: 0.0em; font-size:16px; text-align:center"> | ||
− | + | 1. Consult adviser & supervisor on alternative work arounds <br> | |
+ | 2. Maintain close communication with sponsor | ||
+ | 3. Drop or add functionality once communicated and approved by stakeholders | ||
|} | |} |
Revision as of 19:46, 27 October 2013
Home | Project Overview | Project Management | Documentation | The Team |
Schedule | Risks | Metrics | Resources | Learning Outcomes |
---|
Risk Type | Risk Description | Likelihood | Impact | Category | Mitigation |
---|---|---|---|---|---|
Project Management |
Technology used in bulk of project scope is uncharted by the team, this may cause higher possibility (& greater difficulty) in estimating each task to be scheduled. |
High |
High |
A |
1. Adopted SCRUM Methodology; Sprint planning based on team’s periodic velocity, factors in team members’ academic workload & unexpected changes in project scope as well. |
Technicality Depth |
Most of the technology and tools to be used are relatively new to the team. If the learning curve becomes too steep, there would be delays in expected deadlines. |
Moderate |
High |
B |
1. Members are to research comprehensively and consult experts on the new technologies.
|
Resource |
Unexpected limitations in resources required by team from clients may result in
|
Moderate |
High |
B |
1. Consult adviser & supervisor on alternative work arounds |