Different sets of Artifacts produced as part of Project Management Framework

Below are the sets of Artifacts that would be produced part of Project Management Framework. 

Level 1: 

Lessons Learnt: This is a project repository for lessons learnt from this project which can be used to help future projects. 

PID PowerPoint version: This document sets out the project goal, objectives, scope, work stream deliverables, organization, Governance, management process and communication in order to form the basis for its delivery and the assessment of overall success. 

Project Charter: This document outlines the purpose of the project, the way the project will be structured and how it will be successfully implemented, and sets out the initial business case for the project. 

Project Initiation Document: This document sets out the project goal, objectives, scope, work stream deliverables, organization, Governance, management process and communication in order to form the basis for its delivery and the assessment of overall success. 

Roadmap: This document is the source file, in Excel, for the Roadmap to copy and paste in the PID, the SC Pack, the WG Pack, and any other. 

Transition Checklist: This document enables the Project Manager to identify and track all Artefacts that will be delivered for this project. It also supports the Project Management Assurance Standard applicable to the project. 

Level 2: 

Benefits Register: This document records the expected benefits applicable to the project and tracks their realisation over time. 

Project Plan: This document is used to plan tasks/activities and identify and track milestones. Progress reporting is performed against this plan. 

Costs and Resources: This document provides the summary and the detail of all costs and resources required to deliver the project. 

CRAID Log: This document provides a tool for the Project Manager and the Project Team to record, update and track all project-related Actions, Risks, Issues, Assumptions, Dependencies and Change requests. 

Communication Plan: This document defines the communication requirements for the project: what communication items will need to be created/maintained and how and when information will be distributed. 

Stakeholder Table: This document is a Stakeholder management tool and is associated with PCP05 Communication Plan. 

Status Report: This document provides a template for reporting progress and highlights risks, issues and key dependencies. 

Steering Committee Pack: This document forms the input pack to the Steering Committee meeting. 

Working Group Pack: This document forms the input pack to the Working Group meeting. 

Level 3: 

Post Implementation Review Document: The purpose of this document is to capture feedback, validate the effectiveness of project approach and delivery, and provide some foundation to document the lessons learnt. 

PIR Questionnaire: Artefact to support the Post Implementation Review process. 
Business Requirements Document The purpose of this document is to provide a clear, complete and concise definition of the business requirements (the ‘what’). 

Requirements Traceability Matrix: This document is a tool for the project manager and the project team to trace information pertaining to the progress (execution) and the delivery (implementation) of the solution. 

Testing Strategy: The purpose of this document is to identify the activities, deliverables and responsible parties to carry out and approve test(s). 

Implementation Strategy and Plan: The purpose of this document is to detail the strategy to be employed for the Implementation for the project. 

Go Live Readiness Checklist: The purpose of this document is to enable the Project Manager to document whether all the necessary tasks required prior to Go Live have been completed. 

BAU Handover Document: The purpose of this document is to document all outstanding project tasks, actions, issues and Benefit tracking for that are handed over to the production team, as well as to present the BAU support model. 

Implementation Communication: Copy and paste this text in an email and send to all relevant project and BAU resources - attach the BAU Handover document.