Risk Management for Major Tracking System

Risks Found

  1. Data Loss during editing.
  2. Legitimate faculty accounts.
  3. Course and Major information validity.
  4. Students being able to easily see what requirements they have/haven't met.

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 1, 4
People 2, 3, 4
Organizational 3
Tools  
Requirements 4
Estimation  

Risk analysis

Evaluate each risk


Risk Probability Effects
Data Loss during editing. Low Serious
Legitimate faculty accounts. Moderate Catastropic
Course and Major information validity. Low Catastropic


Risk management strategies

Decide how to manage each risk.


Risk Strategy
Data Loss during editing. Test, test, and test some more. Make sure that in each test case we present the system with, there is no data loss.
Legitimate faculty accounts. Make the faculty have to contact the administrator and give the administrator the ability to give faculty course/major editing privileges.
Course and Major information validity. Make sure that the faculty have documentation that explains how to edit the course/major information. There's also a possibility these features won't be added to the system.

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
Data Loss during editing. Make different changes to a profile on the Major Requirements website and then check the SQL database to make sure that the no data was lost after the different actions. Matt Kraly and Marcus Hartzler 2 100% 2012-04-15 2012-04-15 All the possibilities of data update were tested multiple times and everything is working.
Course and Major Information Validity Keep the courses in the database and the information on them current. Keep the requirements for every major current Matt Kraly 2 100% 2012-04-22 2012-04-15 The UG12 catalog was successfully uploaded into the database and all the Majors are currently up to date with the catalog.
Students being able to easily see what requirements they have/haven't met. Make sure that it is obvious which classes have been taken and scheduled and which ones are still needed to complete requirements. Marcus Hartzler 4 100% 2012-04-15 2012-04-10 Courses that have been taken are highlighted in green. Courses that have been scheduled are highlighted in yellow. Requirements that have been completely met are highlighted in green. Requirements that have been met based on the courses completed and scheduled are highlighted in yellow. The requirements that haven't been based on the courses completed and the courses scheduled are highlighted in red.
Legitimate faculty accounts. Make it so that faculty accounts must be given privileges by an administrator in order to edit major requirements or classes. Marcus 1 0% 2012-04-19   There is no functionality as far as editing course and major requirements information, so this isn't a risk.


Risk monitoring

Report on status of risk at least each week.

Risk Date Assessment Comments, Plans
Data Loss during editing. 2012-04-15 All data is being put into database correctly and no data is being lost.
Students being able to easily see what requirements they have/haven't met. 2012-04-17 Courses and requirements now are highlighted based on their status.
Course and Major Information Validity 2012-04-15 The UG12 catalog was successfully uploaded into the database.

-- MattKraly - 2012-04-10

Topic revision: r10 - 2012-05-30 - 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