Risks

Back To Home

Risk No

 

 Priority Description Impact Probability Timeframe Mitigation Strategy
1  1 Team members are not expressing their concerns to one another; Team may not work together "harmoniously".  3 2  3  
2  1 The details of the architecture are not well defined and/or understood by all team members; May not create a successful prototype.  3  2 3   
3  3 We have a hard time making decisions in current team meetings, assigning tasks; Team members may not clearly understand what others are doing & what their tasks are.  2  2 2  
4  3 In the past, the client has changed the requirements (functionality) and the SRS is not yet signed; Functionality could change before or after SRS signature.  3  2  3  
5  5 We don't have experience in designing & building a layered architecture; Ultimate product may not be "the most elegant".  2  2  3  
6  6 We are not familiar with the technology that we're going to use for the Logic tier; May be unable to handle concurrency 
issues, cause system to perform in unacceptable ways.		  2  2  2  
7 7 There will be more than one developer of this product; May use "ad hoc" methods and spend more efforts than needed.         
8 8 The develop manager is not a permanent team member and there is not complete buy-in by the rest of team with his decisions; Team may not agree with/understand his decisions at start of next semester (when he's gone.)  2  2  2  

 
Risk No. Description Impact Probability Owner Mitigation Strategy Follow-up
1 Requirements not detailed enough leading to changes in future phases. 3 3 Team
  • Frequent communication with client
  • Documentation reviews.
    		•
    2 Blackboard architecture is unsuitable for the DE system 3 2 Team
  • Research on blackboard
  • Make prototype of system for client review
    		•
  • Robin is researching blackboard
    		•
    3 Heavy course workload results in team members being incapable of doing adequate research 2 2 Team
  • Plan tracking 

    • · Set out action item every week
  • Weekly task assignment evaluation and schedule monitoring
    		•
  • Having weekly for tracking (Wed meeing)
    		•
    4 Have problem setting up test environment due to limited knowledge in Oracle and hardware shortage. 2 2 Team
  • Communication with client
    		•
    5 Team members have limited knowledge in VB/Java, Oracle, and blackboard resulting in high learning curve and reduced project progress. 2 2 Team
  • Plan field research
    		•
    6 Communication with team members is not enough. 2 2 Team
  • Frequent team building
  • Plan team building

    •  

              3 : critical
            2 : marginal
            1 : negligible         3 : very possible (about 70 ~ 100%)
            2 : probable       (about 30 ~ 70%)
            1 : unlikely         (about 0 ~ 30%)