Scribd
Upload
9 views

Checklist_for_Support_after_Project_Closure

The document is a checklist for ensuring adequate support and maintenance after a project's closure. It outlines key considerations such as involvement of IT support staff, vendor support availability, service level agreements, and training for help desk staff. Additionally, it emphasizes the importance of budgeting for software licenses, hardware capacity, and future upgrades.

Uploaded by

Salvaraju
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
9 views

Checklist_for_Support_after_Project_Closure

The document is a checklist for ensuring adequate support and maintenance after a project's closure. It outlines key considerations such as involvement of IT support staff, vendor support availability, service level agreements, and training for help desk staff. Additionally, it emphasizes the importance of budgeting for software licenses, hardware capacity, and future upgrades.

Uploaded by

Salvaraju
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 3

Checklist for Support after

Project Closure

Confidentiality Statement
This <document title> along with all attachments hereto shall be considered <company>’s
Proprietary/Confidential Information
gantthead.com Checklist for Support after Project Closure

Think about the following when considering support and maintenance for a project
solution after the project has finished.

Hard Question
 Has the project manager involved the necessary IT support staff from the project
start? Has s/he made staff members aware of the architecture they are to maintain?

 Does the vendor offer 24/7/365 support? Are the rates for such support
acceptable to the client?

 Are the approved service level agreements developed and in place for each
separate hardware and software item?

 Have the necessary software license fees per user been budgeted for on an
annual basis?

 Have the necessary hardware spares and accessories (having a short life cycle)
been ordered and placed into near-term storage?

 Does the necessary hardware capacity and storage exist for future expansion of
the system?

 Has sufficient bandwidth been allocated to handle calculated volumes of an


intended solution?

 Has the IT support staff been trained in supporting the technology? Can they
resolve technical issues, or are they able to contact the third-party suppliers for
detailed support?

 Has the help desk staff been trained to identify and log calls from users of the
solution?

 Has the project manager notified the help desk of the new solution and its
relevant business function?

 Is the help desk number clearly displayed on the relevant application or specific
website, so users know whom to contact?

 Has the help desk received an updated contact list of details of the relevant
internal staff, suppliers and contractors supporting the solution in any event of
downtime or failure?

 Has the necessary operational support staff been trained to the appropriate level
of support to correct any technical problems that might come up?

 Has the project manager provided the help desk with a script of possible
problems that users of the new solution could encounter?

 Has a formal service level agreement been developed and put into effect
between the organization and suppliers to maintain continued support and service?

©2007 gantthead.com 2
gantthead.com Checklist for Support after Project Closure

 What provisions have been made for future upgrades and enhancements?

©2007 gantthead.com 3

You might also like