PROJECT DOCUMENT DELIVERABLES
Deliverable
Project Charter
Project Work Plan
Weekly Status Report
Quality Management Plan
Test Strategy Guidance
Test Summary Report for each level of
Testing (i.e. unit, System, Systems
Integration, Performance, UAT)
QA/Testing Status Reports
Staff Skills and Training Requirements
Communication Plan
Knowledge Transfer Plan
Implementation Plan/Schedule
Risk Management Plan
Configuration Management Plan
Problem Resolution Plan
Training Plan
User Documentation
Post-Implementation Review Plan
Go-Live Plan
Project Exit Report
Description
Statement of scope, objectives and participants in a project. Provides preliminary delineation of roles and
responsibilities, outlining the project objectives, identifying the main stakeholders, and defining the authority
of the project manager. It serves as a reference of authority for the future of the project.
According to the Project Management Body of Knowledge, a project work plan is “...a formal, approved
document used to guide both project execution and project control. The primary uses of the project plan are
to document planning assumptions and decisions, facilitate communication among stakeholders, and
document approved scope, cost, and schedule baselines. A project plan may be summarized or detailed”
(PMBOK, 2000 Edition).
Provides updates on how a project is progressing against the project work plan.
Defines the acceptable level of quality and describes how the project will ensure this level of quality in its
deliverables and work processes.
An outline that describes the testing portion of the software development cycle. It is created to inform project
managers, testers, and developers about some key issues of the testing process.
A detail of all the important information to come out of the testing procedure, including an assessment of
how well the testing was performed, an assessment of the quality of the system, any incidents that occurred,
and a record of what testing was done and how long it took to be used in future test planning.
Tracks the important project issues and how they’re being addressed, pending work and milestone analysis. It
also reports on the systematic monitoring and evaluation of the various aspects of a project to ensure that
standards of quality are being met.
Document to describe full time equivalent staff members required and training that might be necessary.
Document that describes the methods for gathering, distributing, and storing various types of information;
provides a production schedule showing when each type of information will be produced; details methods
for accessing information between scheduled communications; and incorporates procedures for updating
and refining the communication plan..
Organizes, creates, captures and distributes knowledge and ensures its availability for future users.
Describes the activities to be completed in order to prepare for implementation.
Describes the risk management activities (approach to problem analysis which weighs risk in a situation by
using risk probabilities to give a more accurate understanding of the risks involved) to be performed.
A discipline applying technical and administrative direction and surveillance to: identifying and documenting
the functional and physical characteristics of a configuration item; controlling changes to those
characteristics; recording and reporting change processing and implementation status; and verifying
compliance with specified requirements.
Describes the process used to report, analyze, and resolve problems that occur during the project.
Identify key training requirements for all personnel.
Documentation describing the way in which a system or component is to be
used to obtain desired results
Assessment and review of the completed working solution.
A step-by-step, minute-by-minute execution plan of the activities required to implement the new Production
system. This will also include a back-out plan.
The results of the project and the experiences gathered during the project, which can be differentiated for
different target groups. Enclosures to the final reports are the “As is”-project management documentation and
the agreements for the post-project-phase.
 EXAMPLE PROJECT MILESTONES

No.
Milestone description Planned date Expected date Actual Date G/A/R

1 Site Survey Completed July 1, 2013 July 1, 2013

2 Project Start-Up Completed July 1, 2013 July 1, 2013

3 Project Plan Completed July 1, 2013 July 1, 2013

4 Base AMT Installation and Configuration August 1, 2013 August 1, 2013

5 System Test Planning and Preparations August 1, 2013 August 1, 2013

6 System Test Planning and Preparations September 1, 2013 September 1, 2013

7 Migrated Software Installation 2 (Code & Data) October 1, 2013 October 1, 2013

8 System Testing Started (Includes Unit Testing) October 1, 2013 October 1, 2013

9 Production Infrastructure installed and configured January 1, 2014 January 1, 2014

10 Load & Performance Testing Start January 1, 2014 January 1, 2014

11 Dress Rehearsal 1 Completed February 1, 2014 February 1, 2014

12 Accpetance Testing Start February 1, 2014 February 1, 2014

13 Load & Performance Testing Completed April 1, 2014 April 1, 2014

14 System Testing Completed May 1, 2014 May 1, 2014

15 Developer Envrionments Setup Completed May 1, 2014 May 1, 2014

16 Dress Rehearsal 2 Completed June 1, 2014 June 1, 2014

17 Developer Training Completed June 1, 2014 June 1, 2014

18 Accpetance Testing Completed June 1, 2014 June 1, 2014

19 Operational Readiness Plan Agreed July 1, 2014 July 1, 2014

20 Operational Readiness Plan Implemented July 1, 2014 July 1, 2014

21 Go Live July 1, 2014 July 1, 2014

22 After Care Completed July 31, 2014 July 31, 2014

23 Exit & Evaluation Completed July 31, 2014 July 31, 2014

Asysco offers proven, turnkey technology solutions and expertise for

Gramsbergerstraat 79 / 7742 VG Coevorden / NL delivering high quality transformation and modernization without failure.
+31 (0)524 51 53 86 This transformation enables organizations to reduce cost while increasing
flexibility, facilitating streamlined business process integration and
1424 Piedmont Dr E, Ste. 100 / Tallahassee, FL 32308 / USA innovation. Asysco was founded in 1979 and has offices in Coevorden the
(866) 241 - 3301 Netherlands and Florida, USA. Our motto: ‘Unlocking Your Legacy Value’
expresses our confidence that legacy transformation projects make a lot of
www.asysco.com sense, the risks can be well managed, and the resulting value is simply
outstanding.

201505_PD_USprint