Info Tech Project/Team Management
tiffanymac2001
Milestone5Example.pdf
To: CEO, CIO, Wellness Works Project Representative CC: Project team From: Patrick Connolly Subject: Project Planning, Risk Planning, and Risk Control Report Date: 6 Aug 2017
1. Project Scheduling Planning (Enter as many tasks as needed)
a. Immediate Task Completion
i. Task Name: Documentation and Current Mockup Layouts
1. Duration: increase from 18 days to 20 days
2. Old Dates: 10/19/17 to 12/1/17
3. New Dates: 10/24/17 to 11/20/17
ii. Task Name: Requirements Approved
1. Duration: 2 days
2. Old Dates: 9/2/17 to 9/4/17
3. New Dates: 11/20/17 to 11/22/17
iii. Task Name: Report file layout data mapping
1. Duration: 16 days
To: CEO, CIO, Wellness Works Project Representative CC: Project team From: Patrick Connolly Subject: Project Planning, Risk Planning, and Risk Control Report Date: 6 Aug 2017
1. Project Scheduling Planning (Enter as many tasks as needed)
a. Immediate Task Completion
i. Task Name: Documentation and Current Mockup Layouts
1. Duration: increase from 18 days to 20 days
2. Old Dates: 10/19/17 to 12/1/17
3. New Dates: 10/24/17 to 11/20/17
ii. Task Name: Requirements Approved
1. Duration: 2 days
2. Old Dates: 9/2/17 to 9/4/17
3. New Dates: 11/20/17 to 11/22/17
iii. Task Name: Report file layout data mapping
1. Duration: 16 days
To: CEO, CIO, Wellness Works Project Representative CC: Project team From: Patrick Connolly Subject: Project Planning, Risk Planning, and Risk Control Report Date: 6 Aug 2017
1. Project Scheduling Planning (Enter as many tasks as needed)
a. Immediate Task Completion
i. Task Name: Documentation and Current Mockup Layouts
1. Duration: increase from 18 days to 20 days
2. Old Dates: 10/19/17 to 12/1/17
3. New Dates: 10/24/17 to 11/20/17
ii. Task Name: Requirements Approved
1. Duration: 2 days
2. Old Dates: 9/2/17 to 9/4/17
3. New Dates: 11/20/17 to 11/22/17
iii. Task Name: Report file layout data mapping
1. Duration: 16 days
To: CEO, CIO, Wellness Works Project Representative CC: Project team From: Patrick Connolly Subject: Project Planning, Risk Planning, and Risk Control Report Date: 6 Aug 2017
1. Project Scheduling Planning (Enter as many tasks as needed)
a. Immediate Task Completion
i. Task Name: Documentation and Current Mockup Layouts
1. Duration: increase from 18 days to 20 days
2. Old Dates: 10/19/17 to 12/1/17
3. New Dates: 10/24/17 to 11/20/17
ii. Task Name: Requirements Approved
1. Duration: 2 days
2. Old Dates: 9/2/17 to 9/4/17
3. New Dates: 11/20/17 to 11/22/17
iii. Task Name: Report file layout data mapping
1. Duration: 16 days
docx.docx.pdf Saved to Dropbox • Jun 13, 2018 at 8;18 PM
2. Old Dates: 10/31/17 to 12/6/17
3. New Dates: 10/13/17 to 11/3/17
iiii. Task Name: Report UAT
1. Duration: 8 days
2. Old Dates: 12/13/17 to 12/22/17
3. New Dates: 11/6/17 to 11/30/17
v. Task Name: Reports Approved by Business Owner/Vendor
1. Duration: 2 days
2. Old Dates: 12/5/17 to 12/6/17
3. New Dates: 12/1/17 to 12/4/17
vi. Task Name: Testing Support
1. Duration: 8 days
2. Old Dates: 11/11/17 to 12/18/17
3. New Dates: 11/11/17 to 11/21/17
vii. Task Name: Remediation
1. Duration: 4 days
2. Old Dates: 11/17/17 to 11/22/17
3. New Dates: 11/22/17 to 11/27/17
viii. Task Name: Production Support
1. Duration: 14 days to 17 days
2. Old Dates: 11/23/17 to 12/12/17
3. New Dates: 11/28/17 to 12/20/17
ix. Task Name: Lessons Learned
1. Duration: 1 day
2. Old Dates: 12/27/17 to 12/31/17
3. New Dates: 12/22/17 to 12/27/17
2. Old Dates: 10/31/17 to 12/6/17
3. New Dates: 10/13/17 to 11/3/17
iiii. Task Name: Report UAT
1. Duration: 8 days
2. Old Dates: 12/13/17 to 12/22/17
3. New Dates: 11/6/17 to 11/30/17
v. Task Name: Reports Approved by Business Owner/Vendor
1. Duration: 2 days
2. Old Dates: 12/5/17 to 12/6/17
3. New Dates: 12/1/17 to 12/4/17
vi. Task Name: Testing Support
1. Duration: 8 days
2. Old Dates: 11/11/17 to 12/18/17
3. New Dates: 11/11/17 to 11/21/17
vii. Task Name: Remediation
1. Duration: 4 days
2. Old Dates: 11/17/17 to 11/22/17
3. New Dates: 11/22/17 to 11/27/17
viii. Task Name: Production Support
1. Duration: 14 days to 17 days
2. Old Dates: 11/23/17 to 12/12/17
3. New Dates: 11/28/17 to 12/20/17
ix. Task Name: Lessons Learned
1. Duration: 1 day
2. Old Dates: 12/27/17 to 12/31/17
3. New Dates: 12/22/17 to 12/27/17
2. Old Dates: 10/31/17 to 12/6/17
3. New Dates: 10/13/17 to 11/3/17
iiii. Task Name: Report UAT
1. Duration: 8 days
2. Old Dates: 12/13/17 to 12/22/17
3. New Dates: 11/6/17 to 11/30/17
v. Task Name: Reports Approved by Business Owner/Vendor
1. Duration: 2 days
2. Old Dates: 12/5/17 to 12/6/17
3. New Dates: 12/1/17 to 12/4/17
vi. Task Name: Testing Support
1. Duration: 8 days
2. Old Dates: 11/11/17 to 12/18/17
3. New Dates: 11/11/17 to 11/21/17
vii. Task Name: Remediation
1. Duration: 4 days
2. Old Dates: 11/17/17 to 11/22/17
3. New Dates: 11/22/17 to 11/27/17
viii. Task Name: Production Support
1. Duration: 14 days to 17 days
2. Old Dates: 11/23/17 to 12/12/17
3. New Dates: 11/28/17 to 12/20/17
ix. Task Name: Lessons Learned
1. Duration: 1 day
2. Old Dates: 12/27/17 to 12/31/17
3. New Dates: 12/22/17 to 12/27/17
2. Old Dates: 10/31/17 to 12/6/17
3. New Dates: 10/13/17 to 11/3/17
iiii. Task Name: Report UAT
1. Duration: 8 days
2. Old Dates: 12/13/17 to 12/22/17
3. New Dates: 11/6/17 to 11/30/17
v. Task Name: Reports Approved by Business Owner/Vendor
1. Duration: 2 days
2. Old Dates: 12/5/17 to 12/6/17
3. New Dates: 12/1/17 to 12/4/17
vi. Task Name: Testing Support
1. Duration: 8 days
2. Old Dates: 11/11/17 to 12/18/17
3. New Dates: 11/11/17 to 11/21/17
vii. Task Name: Remediation
1. Duration: 4 days
2. Old Dates: 11/17/17 to 11/22/17
3. New Dates: 11/22/17 to 11/27/17
viii. Task Name: Production Support
1. Duration: 14 days to 17 days
2. Old Dates: 11/23/17 to 12/12/17
3. New Dates: 11/28/17 to 12/20/17
ix. Task Name: Lessons Learned
1. Duration: 1 day
2. Old Dates: 12/27/17 to 12/31/17
3. New Dates: 12/22/17 to 12/27/17
2. Old Dates: 10/31/17 to 12/6/17
3. New Dates: 10/13/17 to 11/3/17
iiii. Task Name: Report UAT
1. Duration: 8 days
2. Old Dates: 12/13/17 to 12/22/17
3. New Dates: 11/6/17 to 11/30/17
v. Task Name: Reports Approved by Business Owner/Vendor
1. Duration: 2 days
2. Old Dates: 12/5/17 to 12/6/17
3. New Dates: 12/1/17 to 12/4/17
vi. Task Name: Testing Support
1. Duration: 8 days
2. Old Dates: 11/11/17 to 12/18/17
3. New Dates: 11/11/17 to 11/21/17
vii. Task Name: Remediation
1. Duration: 4 days
2. Old Dates: 11/17/17 to 11/22/17
3. New Dates: 11/22/17 to 11/27/17
viii. Task Name: Production Support
1. Duration: 14 days to 17 days
2. Old Dates: 11/23/17 to 12/12/17
3. New Dates: 11/28/17 to 12/20/17
ix. Task Name: Lessons Learned
1. Duration: 1 day
2. Old Dates: 12/27/17 to 12/31/17
3. New Dates: 12/22/17 to 12/27/17
2. Old Dates: 10/31/17 to 12/6/17
3. New Dates: 10/13/17 to 11/3/17
iiii. Task Name: Report UAT
1. Duration: 8 days
2. Old Dates: 12/13/17 to 12/22/17
3. New Dates: 11/6/17 to 11/30/17
v. Task Name: Reports Approved by Business Owner/Vendor
1. Duration: 2 days
2. Old Dates: 12/5/17 to 12/6/17
3. New Dates: 12/1/17 to 12/4/17
vi. Task Name: Testing Support
1. Duration: 8 days
2. Old Dates: 11/11/17 to 12/18/17
3. New Dates: 11/11/17 to 11/21/17
vii. Task Name: Remediation
1. Duration: 4 days
2. Old Dates: 11/17/17 to 11/22/17
3. New Dates: 11/22/17 to 11/27/17
viii. Task Name: Production Support
1. Duration: 14 days to 17 days
2. Old Dates: 11/23/17 to 12/12/17
3. New Dates: 11/28/17 to 12/20/17
ix. Task Name: Lessons Learned
1. Duration: 1 day
2. Old Dates: 12/27/17 to 12/31/17
3. New Dates: 12/22/17 to 12/27/17
x. Task Name: Lessons Learned
1. Duration: 4 days
2. Old Dates: 7/24/17 to
3. New Dates: 7/24/17 to 12/29/17
xi. Task Name: Technical Support for Dev Environment
1. Duration: 118 days to 114 days
2. Old Dates: 7/24/17 to 12/31/17
3. New Dates: 7/24/17 to 12/27/17
b. Concurrent Task Completion
i. Task Name: Define Business Rules:
1. Duration: increased from 32 to 33.67 days.
2. Old Dates: 7/1717 to 12/7/17
3. New Dates: 7/13/17 to 8/28/17
ii. Task Name: Data Mapping
1. Duration: increased from 22 Days to 32 days.
2. Old Dates: 9/28/17 to 11/30/17
3. New Dates: 8/29/17 to 10/11/17
iii. Task Name: Report mockups
1. Duration: increase from 8 days to 8.89 days
2. Old Dates: 10/17/17 to 11/29/17
3. New Dates: 10/11/17 to 10/24/17
iiii. Task Name: Project Manager
1. Duration: 92 days
x. Task Name: Lessons Learned
1. Duration: 4 days
2. Old Dates: 7/24/17 to
3. New Dates: 7/24/17 to 12/29/17
xi. Task Name: Technical Support for Dev Environment
1. Duration: 118 days to 114 days
2. Old Dates: 7/24/17 to 12/31/17
3. New Dates: 7/24/17 to 12/27/17
b. Concurrent Task Completion
i. Task Name: Define Business Rules:
1. Duration: increased from 32 to 33.67 days.
2. Old Dates: 7/1717 to 12/7/17
3. New Dates: 7/13/17 to 8/28/17
ii. Task Name: Data Mapping
1. Duration: increased from 22 Days to 32 days.
2. Old Dates: 9/28/17 to 11/30/17
3. New Dates: 8/29/17 to 10/11/17
iii. Task Name: Report mockups
1. Duration: increase from 8 days to 8.89 days
2. Old Dates: 10/17/17 to 11/29/17
3. New Dates: 10/11/17 to 10/24/17
iiii. Task Name: Project Manager
1. Duration: 92 days
x. Task Name: Lessons Learned
1. Duration: 4 days
2. Old Dates: 7/24/17 to
3. New Dates: 7/24/17 to 12/29/17
xi. Task Name: Technical Support for Dev Environment
1. Duration: 118 days to 114 days
2. Old Dates: 7/24/17 to 12/31/17
3. New Dates: 7/24/17 to 12/27/17
b. Concurrent Task Completion
i. Task Name: Define Business Rules:
1. Duration: increased from 32 to 33.67 days.
2. Old Dates: 7/1717 to 12/7/17
3. New Dates: 7/13/17 to 8/28/17
ii. Task Name: Data Mapping
1. Duration: increased from 22 Days to 32 days.
2. Old Dates: 9/28/17 to 11/30/17
3. New Dates: 8/29/17 to 10/11/17
iii. Task Name: Report mockups
1. Duration: increase from 8 days to 8.89 days
2. Old Dates: 10/17/17 to 11/29/17
3. New Dates: 10/11/17 to 10/24/17
iiii. Task Name: Project Manager
1. Duration: 92 days
x. Task Name: Lessons Learned
1. Duration: 4 days
2. Old Dates: 7/24/17 to
3. New Dates: 7/24/17 to 12/29/17
xi. Task Name: Technical Support for Dev Environment
1. Duration: 118 days to 114 days
2. Old Dates: 7/24/17 to 12/31/17
3. New Dates: 7/24/17 to 12/27/17
b. Concurrent Task Completion
i. Task Name: Define Business Rules:
1. Duration: increased from 32 to 33.67 days.
2. Old Dates: 7/1717 to 12/7/17
3. New Dates: 7/13/17 to 8/28/17
ii. Task Name: Data Mapping
1. Duration: increased from 22 Days to 32 days.
2. Old Dates: 9/28/17 to 11/30/17
3. New Dates: 8/29/17 to 10/11/17
iii. Task Name: Report mockups
1. Duration: increase from 8 days to 8.89 days
2. Old Dates: 10/17/17 to 11/29/17
3. New Dates: 10/11/17 to 10/24/17
iiii. Task Name: Project Manager
1. Duration: 92 days
x. Task Name: Lessons Learned
1. Duration: 4 days
2. Old Dates: 7/24/17 to
3. New Dates: 7/24/17 to 12/29/17
xi. Task Name: Technical Support for Dev Environment
1. Duration: 118 days to 114 days
2. Old Dates: 7/24/17 to 12/31/17
3. New Dates: 7/24/17 to 12/27/17
b. Concurrent Task Completion
i. Task Name: Define Business Rules:
1. Duration: increased from 32 to 33.67 days.
2. Old Dates: 7/1717 to 12/7/17
3. New Dates: 7/13/17 to 8/28/17
ii. Task Name: Data Mapping
1. Duration: increased from 22 Days to 32 days.
2. Old Dates: 9/28/17 to 11/30/17
3. New Dates: 8/29/17 to 10/11/17
iii. Task Name: Report mockups
1. Duration: increase from 8 days to 8.89 days
2. Old Dates: 10/17/17 to 11/29/17
3. New Dates: 10/11/17 to 10/24/17
iiii. Task Name: Project Manager
1. Duration: 92 days
x. Task Name: Lessons Learned
1. Duration: 4 days
2. Old Dates: 7/24/17 to
3. New Dates: 7/24/17 to 12/29/17
xi. Task Name: Technical Support for Dev Environment
1. Duration: 118 days to 114 days
2. Old Dates: 7/24/17 to 12/31/17
3. New Dates: 7/24/17 to 12/27/17
b. Concurrent Task Completion
i. Task Name: Define Business Rules:
1. Duration: increased from 32 to 33.67 days.
2. Old Dates: 7/1717 to 12/7/17
3. New Dates: 7/13/17 to 8/28/17
ii. Task Name: Data Mapping
1. Duration: increased from 22 Days to 32 days.
2. Old Dates: 9/28/17 to 11/30/17
3. New Dates: 8/29/17 to 10/11/17
iii. Task Name: Report mockups
1. Duration: increase from 8 days to 8.89 days
2. Old Dates: 10/17/17 to 11/29/17
3. New Dates: 10/11/17 to 10/24/17
iiii. Task Name: Project Manager
1. Duration: 92 days
2. Old Dates: 7/13/17 to 11/15/17
3. New Dates: 7/13/17 to 12/1/17
c. Rationale for Schedule Changes:
i. The project manager had some over lapping tasks. One of which was only 10% utilization but the others were at 100%. By decreasing the utilization of the other tasks to 90%, they can be done concurrently.
ii. There was a lot of unnecessary slack in the project schedule. I removed the slack and relevel the resources.
2. Risk Management Plan
a. Levels of Uncertainty (National Research Council, 2005, p. 41): For the most part, the level uncertainty on the project is low. The requirements for the vendor ingest and tables that they are going into have not changed. The exception is the requirements for the user reports. With the end users constantly changing the requirements for the reports, the level of uncertainty is high. To deal with the level of uncertainty, we will be implementing a change control board and all requests for changes will need to be approved by the board prior to being implemented.
b. High-level Threats: Since the completion date is a fixed date, we need to concentrate on those threats that have the possibility to impact that date.
i. The development environment: We are using a development environment that no one is familiar with. We are relying on the vendor to provide tech support but the vendor does not have the resources to provide the level of support that we need.
2. Old Dates: 7/13/17 to 11/15/17
3. New Dates: 7/13/17 to 12/1/17
c. Rationale for Schedule Changes:
i. The project manager had some over lapping tasks. One of which was only 10% utilization but the others were at 100%. By decreasing the utilization of the other tasks to 90%, they can be done concurrently.
ii. There was a lot of unnecessary slack in the project schedule. I removed the slack and relevel the resources.
2. Risk Management Plan
a. Levels of Uncertainty (National Research Council, 2005, p. 41): For the most part, the level uncertainty on the project is low. The requirements for the vendor ingest and tables that they are going into have not changed. The exception is the requirements for the user reports. With the end users constantly changing the requirements for the reports, the level of uncertainty is high. To deal with the level of uncertainty, we will be implementing a change control board and all requests for changes will need to be approved by the board prior to being implemented.
b. High-level Threats: Since the completion date is a fixed date, we need to concentrate on those threats that have the possibility to impact that date.
i. The development environment: We are using a development environment that no one is familiar with. We are relying on the vendor to provide tech support but the vendor does not have the resources to provide the level of support that we need.
2. Old Dates: 7/13/17 to 11/15/17
3. New Dates: 7/13/17 to 12/1/17
c. Rationale for Schedule Changes:
i. The project manager had some over lapping tasks. One of which was only 10% utilization but the others were at 100%. By decreasing the utilization of the other tasks to 90%, they can be done concurrently.
ii. There was a lot of unnecessary slack in the project schedule. I removed the slack and relevel the resources.
2. Risk Management Plan
a. Levels of Uncertainty (National Research Council, 2005, p. 41): For the most part, the level uncertainty on the project is low. The requirements for the vendor ingest and tables that they are going into have not changed. The exception is the requirements for the user reports. With the end users constantly changing the requirements for the reports, the level of uncertainty is high. To deal with the level of uncertainty, we will be implementing a change control board and all requests for changes will need to be approved by the board prior to being implemented.
b. High-level Threats: Since the completion date is a fixed date, we need to concentrate on those threats that have the possibility to impact that date.
i. The development environment: We are using a development environment that no one is familiar with. We are relying on the vendor to provide tech support but the vendor does not have the resources to provide the level of support that we need.
2. Old Dates: 7/13/17 to 11/15/17
3. New Dates: 7/13/17 to 12/1/17
c. Rationale for Schedule Changes:
i. The project manager had some over lapping tasks. One of which was only 10% utilization but the others were at 100%. By decreasing the utilization of the other tasks to 90%, they can be done concurrently.
ii. There was a lot of unnecessary slack in the project schedule. I removed the slack and relevel the resources.
2. Risk Management Plan
a. Levels of Uncertainty (National Research Council, 2005, p. 41): For the most part, the level uncertainty on the project is low. The requirements for the vendor ingest and tables that they are going into have not changed. The exception is the requirements for the user reports. With the end users constantly changing the requirements for the reports, the level of uncertainty is high. To deal with the level of uncertainty, we will be implementing a change control board and all requests for changes will need to be approved by the board prior to being implemented.
b. High-level Threats: Since the completion date is a fixed date, we need to concentrate on those threats that have the possibility to impact that date.
i. The development environment: We are using a development environment that no one is familiar with. We are relying on the vendor to provide tech support but the vendor does not have the resources to provide the level of support that we need.
ii. User reports: The requirements for the user reports are constantly changing. Each time the requirements change, it increases the time to complete the tasks.
c. Mitigation for each
i. The development environment: We are bringing on a consultant who is a subject matter expert to provide the technical support that we require.
ii. User reports: We will be implementing a change control board and all requests for changes will need to be approved by the board prior to being implemented.
3. IT 625 – Project Milestone 5 Sunday, August 6, 2017
4. Risk Control
Risk Calculator
Impact
Low Medium High
Probability Low 1 2 3
Medium 2 3 4
High 3 4 5
ii. User reports: The requirements for the user reports are constantly changing. Each time the requirements change, it increases the time to complete the tasks.
c. Mitigation for each
i. The development environment: We are bringing on a consultant who is a subject matter expert to provide the technical support that we require.
ii. User reports: We will be implementing a change control board and all requests for changes will need to be approved by the board prior to being implemented.
3. IT 625 – Project Milestone 5 Sunday, August 6, 2017
4. Risk Control
Risk Calculator
Impact
Low Medium High
Probability Low 1 2 3
Medium 2 3 4
High 3 4 5
ii. User reports: The requirements for the user reports are constantly changing. Each time the requirements change, it increases the time to complete the tasks.
c. Mitigation for each
i. The development environment: We are bringing on a consultant who is a subject matter expert to provide the technical support that we require.
ii. User reports: We will be implementing a change control board and all requests for changes will need to be approved by the board prior to being implemented.
3. IT 625 – Project Milestone 5 Sunday, August 6, 2017
4. Risk Control
Risk Calculator
Impact
Low Medium High
Probability Low 1 2 3
Medium 2 3 4
High 3 4 5
ii. User reports: The requirements for the user reports are constantly changing. Each time the requirements change, it increases the time to complete the tasks.
c. Mitigation for each
i. The development environment: We are bringing on a consultant who is a subject matter expert to provide the technical support that we require.
ii. User reports: We will be implementing a change control board and all requests for changes will need to be approved by the board prior to being implemented.
3. IT 625 – Project Milestone 5 Sunday, August 6, 2017
4. Risk Control
Risk Calculator
Impact
Low Medium High
Probability Low 1 2 3
Medium 2 3 4
High 3 4 5
ii. User reports: The requirements for the user reports are constantly changing. Each time the requirements change, it increases the time to complete the tasks.
c. Mitigation for each
i. The development environment: We are bringing on a consultant who is a subject matter expert to provide the technical support that we require.
ii. User reports: We will be implementing a change control board and all requests for changes will need to be approved by the board prior to being implemented.
3. IT 625 – Project Milestone 5 Sunday, August 6, 2017
4. Risk Control
Risk Calculator
Impact
Low Medium High
Probability Low 1 2 3
Medium 2 3 4
High 3 4 5
ii. User reports: The requirements for the user reports are constantly changing. Each time the requirements change, it increases the time to complete the tasks.
c. Mitigation for each
i. The development environment: We are bringing on a consultant who is a subject matter expert to provide the technical support that we require.
ii. User reports: We will be implementing a change control board and all requests for changes will need to be approved by the board prior to being implemented.
3. IT 625 – Project Milestone 5 Sunday, August 6, 2017
4. Risk Control
Risk Calculator
Impact
Low Medium High
Probability Low 1 2 3
Medium 2 3 4
High 3 4 5
RISK REGISTER Risk Identification Qualitative Rating Risk Response
Risk Risk Category Probability Impact
Risk Score
Risk Ranking
Risk Mitigation Trigger
Risk Owner
User reports requirements Schedule High High 5 1
Mitigate: implement CCB
Excessive amounts of change request
Project Manager
Development environment issues Technology Medium High 4 2
Mitigate: Open ticket with vendor
Not solved within 4 hours SME
Vendor data ingest problems Technology Low High 3 3
Mitigate: Contact vendor
Not solved within 24 hours SME
Teradata 14 database issues Technology Low High 3 4
Mitigate: Open ticket with vendor
Not solved within 4 hours SME
Loss of project team member Schedule Low Medium 2 5
Mitigate: High new member
Project Manager
IT 625 – Project Milestone 5 Sunday, August 6, 2017
References National Research Council. (2005). Chapter: 5 Risk Mitigation. In N. R. Council, The Owner's role in project risk management (pp. 41-90). Washington, DC: The National Academies Press. Retrieved from NAP.edu: https://www.nap.edu/read/11183/chapter/7
IT 625 – Project Milestone 5 Sunday, August 6, 2017
RISK REGISTER Risk Identification Qualitative Rating Risk Response
Risk Risk Category Probability Impact
Risk Score
Risk Ranking
Risk Mitigation Trigger
Risk Owner
User reports requirements Schedule High High 5 1
Mitigate: implement CCB
Excessive amounts of change request
Project Manager
Development environment issues Technology Medium High 4 2
Mitigate: Open ticket with vendor
Not solved within 4 hours SME
Vendor data ingest problems Technology Low High 3 3
Mitigate: Contact vendor
Not solved within 24 hours SME
Teradata 14 database issues Technology Low High 3 4
Mitigate: Open ticket with vendor
Not solved within 4 hours SME
Loss of project team member Schedule Low Medium 2 5
Mitigate: High new member
Project Manager
IT 625 – Project Milestone 5 Sunday, August 6, 2017
References National Research Council. (2005). Chapter: 5 Risk Mitigation. In N. R. Council, The Owner's role in project risk management (pp. 41-90). Washington, DC: The National Academies Press. Retrieved from NAP.edu: https://www.nap.edu/read/11183/chapter/7
IT 625 – Project Milestone 5 Sunday, August 6, 2017
RISK REGISTER Risk Identification Qualitative Rating Risk Response
Risk Risk Category Probability Impact
Risk Score
Risk Ranking
Risk Mitigation Trigger
Risk Owner
User reports requirements Schedule High High 5 1
Mitigate: implement CCB
Excessive amounts of change request
Project Manager
Development environment issues Technology Medium High 4 2
Mitigate: Open ticket with vendor
Not solved within 4 hours SME
Vendor data ingest problems Technology Low High 3 3
Mitigate: Contact vendor
Not solved within 24 hours SME
Teradata 14 database issues Technology Low High 3 4
Mitigate: Open ticket with vendor
Not solved within 4 hours SME
Loss of project team member Schedule Low Medium 2 5
Mitigate: High new member
Project Manager
IT 625 – Project Milestone 5 Sunday, August 6, 2017
References National Research Council. (2005). Chapter: 5 Risk Mitigation. In N. R. Council, The Owner's role in project risk management (pp. 41-90). Washington, DC: The National Academies Press. Retrieved from NAP.edu: https://www.nap.edu/read/11183/chapter/7
IT 625 – Project Milestone 5 Sunday, August 6, 2017
RISK REGISTER Risk Identification Qualitative Rating Risk Response
Risk Risk Category Probability Impact
Risk Score
Risk Ranking
Risk Mitigation Trigger
Risk Owner
User reports requirements Schedule High High 5 1
Mitigate: implement CCB
Excessive amounts of change request
Project Manager
Development environment issues Technology Medium High 4 2
Mitigate: Open ticket with vendor
Not solved within 4 hours SME
Vendor data ingest problems Technology Low High 3 3
Mitigate: Contact vendor
Not solved within 24 hours SME
Teradata 14 database issues Technology Low High 3 4
Mitigate: Open ticket with vendor
Not solved within 4 hours SME
Loss of project team member Schedule Low Medium 2 5
Mitigate: High new member
Project Manager
IT 625 – Project Milestone 5 Sunday, August 6, 2017
References National Research Council. (2005). Chapter: 5 Risk Mitigation. In N. R. Council, The Owner's role in project risk management (pp. 41-90). Washington, DC: The National Academies Press. Retrieved from NAP.edu: https://www.nap.edu/read/11183/chapter/7
IT 625 – Project Milestone 5 Sunday, August 6, 2017
