...
Section 1: To be Completed by the Requestor of the Corrective Action | |||||||||
Today's Date |
| ||||||||
ITSPRO Issue #: |
| ||||||||
Name of Requestor: | |||||||||
Email ID: | kzsamboky@ucsd.edu | ||||||||
Corrective Action Trigger: | Overdue tasks (95% of all tasks) | ||||||||
Current Impact on Project (in terms of schedule, cost, quality, resources, scope): | |||||||||
The project OTL and schedule is not clear. Our processes require the project team to:
| |||||||||
Suggestions for Correction: | |||||||||
| |||||||||
Person Responsible for Section 2: | |||||||||
Section 2: To be Completed by the Project Team | |||||||||
Email ID / User ID: Student Test | |||||||||
What is causing the problem/trigger to occur? | |||||||||
The team was in a discovery phase of the project and did not yet know what the correct OTL was. Since the OTL was not correct, they did not maintain it. | |||||||||
Describe the action(s) to correct the problem/trigger: | |||||||||
The team is beginning the work on a new OTL structure and creating the project RACI and plan to review with Kal the week of 09/07/20 after Kenny's return from vacation | |||||||||
Date of Response: | Corrective Action Completion Date: | ||||||||
Section 3: To be Completed by Approver of Recommended Actions | |||||||||
Approve or Reject Corrective Action Recommendations? Y/N | |||||||||
If Rejected, Additional Comments: | |||||||||
Name of Approver: | Approve/Reject Date: | ||||||||
Section 4: To be Completed after Verification | |||||||||
Have the Actions been Implemented? | |||||||||
Did the Actions Correct the Problem? | |||||||||
Verified and Closed Out by: | Verified Date: | ||||||||