Risk Management for Team N Project

Risks Found

  1. Possible Miscommunications With Stakeholders
  2. Miscommunications Present in Requirements Specifications
  3. Miscommunications Present in System Specifications
  4. Training System Does Not Fulfill Its Intended Purposes
  5. System May Not Adequately Address MVNU Policies
  6. System May Not Adequately Address Title IX Requirements
  7. System May Not Meet Standards To Legally Protect The University
  8. System Performance/Results Do Not Satisfy the Customer
  9. Time Estimates for Remaining Tasks Misjudged
  10. Current LIMRI System Not Properly Understood
  11. Additions to LIMRI System Not Properly Understood (Possible System Degradation/Unforseen Side Effects)
  12. Additions to LIMRI System Not Properly Documented (Future Understanding/System Improvement Impeded)
  13. Incorrect Data Representations (XML, Database, JESS Rules)
  14. LIMRI System Components Properly Working for Testing Data Representations
  15. Unnecessary Complexity Introduced to System (Future Management/Maintenance Problems/Hindered User Friendliness)
  16. System May Contain Logical Errors
  17. System to Properly Encode XML Data May Not Be Available
  18. System Data May Be Inconsistent

Risk Identification

For each of the risk found, classify each by type (some may be in more than one class)

Risk type Possible Risks
Technology  
People 1, 8, 10, 11, 12
Organizational 5, 6, 7
Tools 14, 17
Requirements 2, 3, 4
Estimation/Judgement 9, 13, 15, 16, 18

Risk analysis

Evaluate each risk


Risk Probability Effects

Possible Miscommunications With Stakeholders

Moderate Tolerable

Miscommunications Present in Requirements Specifications

Moderate Serious

Miscommunications Present in System Specifications

Moderate Serious

Training System Does Not Fulfill Its Intended Purposes

Low Catastropic

System May Not Adequately Address MVNU Policies

Low Insignificant

System May Not Adequately Address Title IX Requirements

Low Insignificant

System May Not Meet Standards to Legally Protect the University

Moderate Serious

System Performance/Results Do Not Satisfy the Customer

Moderate Serious

Time Estimates for Remaining Tasks Misjudged

High Serious

Current LIMRI System Not Properly Understood

Moderate Serious

Additions to LIMRI System Not Properly Understood (Possible System Degradation/Unforseen Side Effects)

Low Tolerable

Additions to LIMRI System Not Properly Documented (Future Understanding/System Improvement Impeded)

Moderate Serious

Incorrect Data Representations (XML, Database, JESS)

Low Tolerable

LIMRI System Components Not Properly Working for Testing Data Representations

Moderate Serious

Unnecessary Complexity Introduced into System (Future Management/Maintenance Problems/Hindered User Friendliness)

Moderate Tolerable

System May Contain Logical Errors

Moderate Serious

System to Properly Encode XML Data May Not Be Available

High Tolerable

System Data May Be Inconsistent

Moderate Serious


Risk management strategies

Decide how to manage each risk.


Risk Strategy
Possible Miscommunications With Stakeholders
After the content has been properly created for the system, have it displayed and run through by the stakeholders to identify any potential problems.
Miscommunications Present in Requirements Specifications
After the content has been properly created for the system, have it displayed and run through by the stakeholders to identify any potential problems, that may exist in the requirements specification that need to be changed.
Miscommunications Present in System Specifications
After the content has been properly created for the system, have it displayed and run through by the stakeholders to identify any potential problems, that may exist in the system specification that need to be changed.
Training System Does Not Fulfill Its Intended Purposes
After the content has been properly created for the system, have it displayed and run through by the stakeholders to identify areas that must be modified for the system to be acceptable for its outlined goals.
System May Not Adequately Address MVNU Policies
After the content has been properly created for the system, have it displayed and run through by the stakeholders to identify areas that must be modified for the content to adequately present and train users regarding MVNU Policies.
System May Not Adequately Address Title IX Requirements
After the content has been properly created for the system, have it displayed and run through by the stakeholders to identify areas that must be modified for the content to adequately present and train users regarding Title IX and/or the topics it contains.
System May Not Meet Standards to Legally Protect the University
After the answers to questions can be properly stored in a database using current content, determine what will be needed for that information to viable legal protection for the University.
System Performance/Results Do Not Satisfy the Customer
After the user has seen system progress up to the point of displaying training material and storing question answers, determine what areas of presentation/information storage must be changed for the system to be acceptable.
Time Estimates for Remaining Tasks Misjudged
Because the conversion of content to XML directly by manual typing may be error prone and time consuming, work with the team creating the ITEM creation tool so it may possibly be leveraged to complete content converstion to XML in a timely manner, while still achieving other overall system goals.
Current LIMRI System Not Properly Understood
Review the current system progress, practices and component specifications with original LIMRI System Designers as each piece is examined for areas in which it may need to be added to or modified. Leverage documentation so far in this communication process.
Additions to LIMRI System Not Properly Understood (Possible System Degradation/Unforseen Side Effects)
This hinges on a correct understanding of the LIMRI System in the initially and then moving forward to make the necessary additions to accomodate the differences between the Marriage Inventory Material and the Sexual Harassement Training Material.
Additions to LIMRI System Not Properly Documented (Future Understanding/System Improvement Impeded)
Properly comment and document areas of the original LIMRI System as each component/function/data-representation is evaluated and changes made so it does not degrade to overall system, as it is being continually worked on by other teams as well.
Incorrect Data Representations (XML, Database, JESS)
Confirm all possible data-representations with LIMRI domain experts, then move forward to add necessary changes to display the content, store answers and interact dynamically. Testing in these areas for faults or inconsistencies will hopefully reveal any weaknesses in the current data representations/designs.
LIMRI System Components Properly Working for Testing Data Representations
Keep in touch and up to date with developers working on LIMRI components that are essential and required for the Sexual Harassment Training to be properly integrated into the system and function properly.
Unnecessary Complexity Introduced to System (Future Management/Maintenance Problems/Hindered User Friendliness)
Once the system is being viewed by end users and stakeholders, identify any unnecessary abstractions or unutilized changes/features introduced and use proper judgement to remove any that degrade the system's code quality while providing little or no benefit.
System May Contain Logical Errors
Thorough testing by end users not familiar with the system design or development, and followed by testing of the system by users who may be aware of possible ways the system can be broken. (Black-Box then White-Box Testing)
System to Properly Encode XML Data May Not Be Available
Stay in communication, and aid where possible, the team developing the ITEM XML generator. In order to ensure the proper functionality is available to create training, explanation and question items that will be utilized by the Sexual Harassment Training System that differ from the original Marriage Inventory Requirements.
System Data May Be Inconsistent
Thorough inspection and tests will be needed to determine if all dependencies and data orginization/presentation follows the proper flow. This will likely need to be carried out by team members familiar with the inner workings of dependencies and question/training/explanation item formats in order for inconsistencies in dependency references to be spotted.

Risk Reduction Assignments

Assign Team members to address risks

Specific Assignments of activities to address top risks

Risk Assigned Task Team Member(s) Hours Alloc % Done Finish Goal Date Done Current Status/Outcome
Possible Miscommunications With Stakeholders       0%      
Miscommunications Present in Requirements Specifications       0%      
Miscommunications Present in System Specifications       0%      
Training System Does Not Fulfill Its Intended Purposes       0%      
System May Not Adequately Address MVNU Policies       0%      
System May Not Adequately Address Title IX Requirements       0%      
System May Not Meet Standards to Legally Protect the University       0%      
System Performance/Results Do Not Satisfy the Customer       0%      
Time Estimates for Remaining Tasks Misjudged       0%      
Current LIMRI System Not Properly Understood       0%      
Additions to LIMRI System Not Properly Understood (Possible System Degradation/Unforseen Side Effects)       0%      
Additions to LIMRI System Not Properly Understood (Possible System Degradation/Unforseen Side Effects)       0%      
Additions to LIMRI System Not Properly Documented (Future Understanding/System Improvement Impeded)       0%      
Incorrect Data Representations (XML, Database, JESS)       0%      
LIMRI System Components Properly Working for Testing Data Representations       0%      
Unnecessary Complexity Introduced to System (Future Management/Maintenance Problems/Hindered User Friendliness)       0%      
System May Contain Logical Errors       0%      
System to Properly Encode XML Data May Not Be Available       0%      
System Data May Be Inconsistent       0%      


Risk monitoring

Report on status of risk at least each week.

-- ZacharyBennett - 2012-04-10

Topic revision: r3 - 2012-05-21 - JimSkon
 
This site is powered by the TWiki collaboration platformCopyright &© by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback