This describes the process for a vITM to review a project after work has been completed.

vITMs and vITM Manager (Senior IT Manager) after projects are completed by project team.

vITMs

Completion of this review will lead to the project being deemed complete and closed.

Output records will depend on work performed and items reviewed. The end goal is a message to the Project Manager that the project is successfully completed and can be closed.

1. Prerequisites: A completed project with proper documentation showing major milestones have been completed and that the project completed meets the specifications of the original project scope of work. Any deviations from the original project scope of work must be detailed clearly to vITM prior to this review.

2. Project Manager will notify the vITM in the Teams Project Channel that project work is complete. This will indicate to the vITM to start this review.

   - The expectation is that this review should be completed within 1 business day of Project Manager’s notification of project completion. If more time is needed, a “by-when” date must be provided to the project manager setting the expected completion date of the review within that 1 business day timeframe. If vITM is on vacation or out on leave, business days start at the date the vITM returns to work.

3. Review the original scope of work and completed scope of work and any change orders or deviations and answer the following questions:

   - Is there anything that was not executed and not explained?

   - Was the project completed as indicated in the original scope of work (SOW)?

   - Were the stated goals of the project completed?

   - If the original SOW was modified was the change sufficient to meet the client’s needs?

   - Is there any outstanding work that still must be completed? Is that work documented and in another form such as a ticket or planner task for the vITM or vCIO?

   - Are there any concerns with the way the project was completed?

   - Is the client happy with the project and the way in which the project was completed?

   - Did any concerns arise from the client during the project? Were those concerns addressed?

   - Is there sufficient confirmation of billing, financial change adjustments, and client or system owner responsibility for those cost changes?

   - Is there any licensing that needs to be trued up to match the post project needs?

   - Is there any systems that now need to be retired or additional projects needed that are out of the scope of this project but are necessary after the completion of this project. (Such as systems or databases that may need to be decommissioned, etc). Have those projects or tasks been assigned or added to the client roadmap?

4. Does the evidence presented to the vITM and in the evidence folder show the following?

   - Necessary changes to monitoring or alerting were completed and all new devise are now monitored correctly.

   - All decommissioned items have been removed from monitoring.

   - Updated network diagrams

   - Updated KBs or CI documentation

   - Successful backups

   - Passwords documented in 1Password

5. If each of these above items can be confirmed, vITM is to let the Project Manager know that they project can be closed.

6. If concerns exist, vITM should contact the Project Manager, present the concerns or findings and work to resolve any challenges until Project Manager and vITM are satisfied that project is completed.

7. The Project Manager will close out the project.

1. Create a relationship back to related process. Note: Please add KB relationships to core process, process, SOPs or other WIs on the right.