HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2013T2 Five&AHalfMen Project Management risk"

From IS480
Jump to navigation Jump to search
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">
Adoption of SCRUM Methodology by team for further flexibility in development of final product; includes establishing a close communication with client and periodic revision of product backlog thereafter.
+
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

Five&ahalfLogo.png


Home   Project Overview   Project Management   Documentation   The Team
Schedule Risks Metrics Resources Learning Outcomes


Project Risks

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.
2. Mitigation Plan:
• Continuously revise Product Backlog with updated estimations,
• Maintain close communication with adviser and supervisor for advise

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.
2. PM will observe member’s progress closely and discuss with team whether to:
• push or drop function,
• use alternative technologies or,
• reallocate tasks to developers

Resource

Unexpected limitations in resources required by team from clients may result in
• Expansion of scope,
• Inability to meet client’s requirements
• Project Timeline delays

Moderate

High

B

1. Consult adviser & supervisor on alternative work arounds
2. Maintain close communication with sponsor 3. Drop or add functionality once communicated and approved by stakeholders