HeaderSIS.jpg

Difference between revisions of "Altitude Project Risk Management"

From IS480
Jump to navigation Jump to search
 
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
<div style="background: #FFF; padding: 15px; font-weight: bold; line-height: 1.2em; text-indent: 15px;letter-spacing:-0.1em;font-size:6em;text-align:center;padding 4px 4px 4px 4px;"><font color=#000>» team</font><font color= #f0ab00> altitude </font><font color="#aaa">: Risk Management</font></div>
+
{| style="background-color:#000;" width="100%"
 
+
|-
 +
!style="text-align:right; width:45%"|[[Image:Altitude_logo_black.jpg|650px]]
 +
!style="text-align:left"|
 +
<div style="background: #FFF; font-weight: bold; line-height: 1.2em; letter-spacing:-0.1em;font-size:6em;text-align:left;padding 4px 4px 4px 4px;background-color:#000"><font color="#aaa">risk management</font></div>
 +
|}
 
{| <!-- table start, define style here --> | style="background-color:#000;" width="100%" cellspacing="0px" cellpadding="12px" border="0"  
 
{| <!-- table start, define style here --> | style="background-color:#000;" width="100%" cellspacing="0px" cellpadding="12px" border="0"  
 
|-
 
|-

Latest revision as of 02:17, 26 July 2013

Altitude logo black.jpg
risk management
Overview Project Management Documentation

Schedule

Scope


Risk Mitigation
Altituderisklegend.png The following are risks that the team has identified pertaining to project delivery.

The Risk Analysis Plan includes steps taken by the team to avoid the risks. In addition, it also lists the support the team requires from the client side to reduce the possible risks.
S/N Risk Description Impact Impact Level
(High/Med/Low)
Likelihood
(High/Med/Low)
Category Mitigation Strategy Status

1

Project Management

1.1

  • Overestimation of tasks to be completed within sprint
  • Project Schedule is delayed

High

High

A

  • Schedule planning will be reviewed and adjusted based on Schedule Matrix
  • Plan buffer time for each sprint

Mitigation strategy
in force

1.2

  • Many issues may be raised during UAT
  • Project Schedule is delayed

High

High

A

  • A Change Management Log is created to help us decide whether to implement a change based on the value added the project, priority and time needed to rectify the issues.

Mitigation strategy
in force

1.3

  • Project documentation is scattered and contain many different versions. Members are unable to promptly refer to specific details
  • Accuracy of information used is compromised

Low

Medium

C

  • Use a collaborative software (e.g. Google Documents) to organise documenation. Consensus amongst team members to adhere to proper version labelling.

Risk Eliminated

2

Client Management

2.1

  • Unable to contact Client due to his overseas trip (e.g. Germany)
  • Client meeting will be affected and the project reporting progress might get slightly delayed

Medium

High

A

  • Find out client's schedule, pre-plan meetings around the client’s schedule

Establish alternative methods of communication with the client (eg. online meeting)

Mitigation strategy
in force

2.2

  • Major changes in client requirements
  • Change requests may affect the scope and schedule of the project

Low

High

B

  • Seek client agreement of Project Scope Document early in the project
  • Project Manager should oversee the project schedule and scope
  • Use the Change Management Log to manage client’s request

Mitigation strategy
in force

3

Team Management

3.1

  • Max may not be able to join the team should his IS480 grade not make the cut
  • Team organisation will be affected

High

Medium

A

  • Team to find another UX specialist

Risk eliminated

3.2

  • Conflict amongst team members due to different working styles
  • Project will get delayed

Medium

Low

C

  • Project Manager to organize a “Trashing Out” session for the team. Members to come to an understanding for the team to progress forward.

Mitigation strategy
in force

3.3

  • Underestimation of tasks assisgned to members
  • Member does not have the capabilities to finish the assigned tasks within the time frame, which lead to a spill over into other sprint

Medium

High

A

  • Member should approach others for help when they are unsure of their assigned tasks
  • Project progress have to be review by each member after every meeting

Mitigation strategy
in force

4

Technological Implementation

4.1

  • Members unfamiliar with technologies
  • Project iteration takes longer to completed which affects the project schedule to be delayed

Medium

Medium

B

  • Start to research the new technologies earlier before adoption
  • Organize knowledge sharing session among the team

Mitigation strategy
in force

4.2

  • Limited development resources (example: physical devices such as ipad)
  • Team’s progress will be affected and project schedule will be delayed

Medium

Medium

B

  • Discuss with client the possibility of obtaining physical devices
  • Discuss with school the possibility of loaning a mini-ipad for testing (subjected to availability

Mitigation strategy
in force

4.3

  • Version changes to technologies which our project is dependent on
  • Team’s progress will be affected and project schedule will be delayed

Medium

Medium

B

  • Communicate with client to be kept updated of technological updates

Mitigation strategy
in force