HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2016T2 Codex Risk Management"

From IS480
Jump to navigation Jump to search
Line 64: Line 64:
 
! style="font-weight: bold;background: #27546E;color:#fff;" | Impact  
 
! style="font-weight: bold;background: #27546E;color:#fff;" | Impact  
 
! style="font-weight: bold;background: #27546E;color:#fff;" | Category  
 
! style="font-weight: bold;background: #27546E;color:#fff;" | Category  
! style="font-weight: bold;background: #027546E;color:#fff;" | Mitigation  
+
! style="font-weight: bold;background: #27546E;color:#fff;" | Mitigation  
 
|-
 
|-
 
| 1
 
| 1

Revision as of 13:48, 29 October 2015

Codex logo.png


Codex homelogo.png   HOME

 

Codex aboutus.png   ABOUT US

 

Codex projectoverview.png   PROJECT OVERVIEW

 

Codex projmgt.png   PROJECT MANAGEMENT

 

Codex doc.png   DOCUMENTATION

 


# Risk Type Risk Event Likelihood Impact Category Mitigation
1 Technical Risk Overall, the team is not familiar with the technologies/resources used for developing the project (i.e. PHP.) High High A We will conduct peer teaching and sharing to help each other.
2 Project Management Risk Team’s lack of experience might cause delays in the iterations due to underestimate or overestimate of a programming task. Medium High A Regular meetings to update on progress. If necessary, we will re-plan task(s) for the next iteration.
3 Client Management Risk Client has not fully decided upon the range of functions in her application as she is new to a e-commerce web application; may eventually lead to big scope changes. Medium Medium B Regular meet up with our client to update her on our current progress and ask for incremental feedbacks.
4 Client Management Risk Client has not host an e-commerce or a website before and is not IT savy, she may experience some difficulty with using our system. Medium Medium B We try to maintain simplicity in our design but we might compile a user guide for her future reference.
9 Resource Risk Unforeseeable problems with technology that could cause loss of data. Low High B Make sure that files are always updated in the dropbox, such that the loss of a local hard drive will not affect the project greatly.
10 Human Risk Team members become unavailable due to sickness or other unavoidable circumstances, as we have only 4 members. Low Medium C Code sharing session, so another coder can take over the coding task from the sick member.