The purpose of the Project Initiation Documentation (PID) is to clearly define the project, in order to form the basis for its management and an assessment of its overall success. The PID gives the direction and scope of the project and (along with project stage plans) forms the base document.

The PID will provide controls to ensure the project is meeting expectations and to enable the desired benefits to be achieved subsequently, there needs to be a focus on the quality of the project’s product: a Joint School Computing Service recommendation. By agreeing acceptance criteria, this will prevent the project to be exposed to major risks such as acceptance disputes, rework, uncontrolled change, user dissatisfaction, etc.

Please find the following documents in the right sidebar:

• PID:
  This PID will act as the single source of reference about the project and therefore will be a ‘living’ document to continuously reflect the current plans, status and controls of the project.
• Project Brief:
  The Project definition, scope and objectives are described in the Project Brief. The purpose of the Project Brief is to lay-out the project information and understanding to define the scope, budget and timelines for the Joint School Computing Service (JSCS) Project. The Project Brief will ensure there is an agreed, commonly understood and well defined starting point.
• Project Organisation:
  The purpose of the Project Organisation Document is to clearly define and establish the project’s structure of accountability and responsibilities for the JSCS project.
  
• Risk Management:
  The purpose of implementing a risk management strategy is to identify, assess and control uncertainty and as a result of that, improve the ability of the project to succeed. The strategy is to describe how risk management will be embedded in the project management activities.
• Communications Strategy:
  The Communication Management Strategy addresses both internal and external communications and will contain details of how the project management team will send information to, and receive information from.

This project will follow a Change Management Procedure to effectively manage any change to the base lined project scope. A formal Project Change Request will need to be raised to the project after which an Impact Assessment will be carried out in order to identify the impact on the contractual agreements, project quality, timelines and budget.
Please find the Project Change Request and Impact Assessment Template in the right sidebar.