Project Management Plan Template

Project Management Plan
<Project Name>
Document ID:
Version:
Release Date:

www.simplilearn.com

Copyright Simplilearn

This document is the property of Simplilearn, and its contents are confidential to Simplilearn Reproduction of the materials contained herein, in part or full
in any form by anyone, without the permission of Simplilearn is prohibited.


Document Information

Author

Reviewer

Approver

Revision History

Date Version Section Changed Change Description Author

Strictly Confidential Version 1.0 Page 2 of 28


Index
Table of Contents

1 Purpose..........................................................................................................................6

2 Scope.............................................................................................................................6

3 Audience .......................................................................................................................7

4 References.....................................................................................................................7

5 Glossary ........................................................................................................................7

5.1 Acronyms...................................................................................................................7
5.1.1 Definitions ..........................................................................................................................7

6 Process..........................................................................................................................7

7 Open Issues – While Writing Document Only..........................................................8

8 Project Introduction......................................................................................................8

8.1 Project Overview........................................................................................................8
8.2 Project Description, Scope & Objectives...................................................................9
8.2.1 Project Description..............................................................................................................9
8.2.2 Project Scope...................................................................................................................10
8.2.3 Project Objectives.............................................................................................................10
8.3 Project Environment................................................................................................10
8.3.1 Development Environment................................................................................................10
8.3.2 Maintenance Environment................................................................................................10
8.4 Target Implementation Environment.......................................................................10
8.5 Project Deliverables.................................................................................................11
8.6 Client Contact Details..............................................................................................11
8.7 Reference Material..................................................................................................11
8.8 Project Terminology, Acronyms and Definitions......................................................12
8.9 Referred Project Database & Library......................................................................12

9 Project Organization...................................................................................................13

9.1 Organizational Structure .........................................................................................13
9.2 Organizational Structure.........................................................................................13
9.3 Problems faced in the Current System ...................................................................14


10 Project Control..........................................................................................................14

10.1 Project Management Goals...................................................................................14
10.2 Assumptions, Dependencies & Constraints .........................................................14
10.2.1 Assumptions ..................................................................................................................14
10.2.2 Dependencies.................................................................................................................15
10.2.3 Constraints......................................................................................................................15
10.3 Information Gathering & Project reporting.............................................................15
10.3.1 Reporting Mechanisms...................................................................................................15
10.3.2 Monitoring & Tracking.....................................................................................................16
10.3.3 Meetings.........................................................................................................................16
10.4 External Communication and Communication Protocol........................................17
10.5 Update of Project Plan...........................................................................................17
10.6 Risk Management Plan.........................................................................................17
10.7 Configuration Management...................................................................................18
10.7.1 Project Configuration Items and SCM Schedule.............................................................18
10.7.2 Naming Conventions.......................................................................................................19
10.7.3 Version Number Scheme................................................................................................19
10.7.4 Controlled Software libraries...........................................................................................19
10.7.5 Library backup strategy...................................................................................................20
10.7.6 Procedure for the storage of documents and magnetic media........................................20
10.7.7 Procedure for retrieval and reproduction of controlled items from the library..................20
10.8 Change Management Procedure..........................................................................20
10.9 Configuration Status reporting...............................................................................21
10.10 Project Audit Schedule........................................................................................21

11 Resource Plan...........................................................................................................23

11.1 Person Power........................................................................................................23
11.2 Training..................................................................................................................23
11.3 Hardware...............................................................................................................23
11.4 Software.................................................................................................................24
11.5 Other resources.....................................................................................................24
11.6 Budget....................................................................................................................24

12 Simplilearn Obligations............................................................................................24

12.1 Simplilearn Activities..............................................................................................24
12.2 Simplilearn Supplied product handling..................................................................25



13 Verification & Validation..........................................................................................25

13.1 Review Plan...........................................................................................................25
13.1.1 Artifact Review Strategy..................................................................................................25
13.1.2 Artifact Approval Strategy...............................................................................................26
13.1.3 Artifact Approval Criteria.................................................................................................26
13.2 Software Quality Assurance Plan..........................................................................26
13.2.1 Test Approval Strategy...................................................................................................26
13.3 Test Strategy Overview.........................................................................................27

14 Quality Recording Handling....................................................................................27

14.1 Review Record storage & Handling......................................................................27
15 Document reviews and approvals..........................................................................27

15.1 Document Reviewers.............................................................................................27
15.2 Additional recipients of the document ..................................................................28
15.3 Document Approvers.............................................................................................28



1 Purpose
<IMPORTANT: The comments in ORANGE colour and in ITALICS are meant for author’s
attention. Please delete all the comments, including this, before releasing the document.>
• What purpose does the document serve?
• Why is the document useful to people who will read it?
• Describe in this section the aims the author had in writing the document
• Are there any objectives specific to the project / document that need to be made clear to
facilitate the success of the project?
• It may be beneficial to take a look at the list below and add / delete objectives, as appropriate…
e.g. The objective of this document are to establish and identify:
• A complete plan for managing the project
• all tasks required to successfully complete the project
• project reporting mechanisms
• responsibilities
• risks
• etc etc
Prior to obtaining the approval of this document a formal review should take place to ensure the
completeness and correctness of the plan.
If, following approval of this document and the base-lining of requirements, amendments to the plan
are deemed necessary, changes may be introduced via the change management process.
An updated version of the document must be created to reflect the changes introduced.
• How will this document be used?
• Who uses it and how?
e.g. The document will be used for the following purposes:
• The Project Manager will use it in the plan, control and monitor later phases of the project
• The Simplilearn Project Manager will use it to identify his responsibilities
• The Simplilearn Users will use it to identify their involvement and responsibilities
• Simplilearn board will use it to understand the scope of the project and to monitor progress
against the plans
• The Project Office will use it to create a project plan

2 Scope
• What is the scope of the document?
• Are there any reasons to believe that not specifying something may cause confusion, or lead to
claims that it was “so obvious” that it need not be stated?

• Have there been any problems with the client, or areas of contention or confusion, that mean a
clear statement on the exclusions from the project or requirements should also be stated here?


• Ambiguities can be avoided by stating the scope here!
• Are there any similar requirements that are not part of this project, but which the user might think
are?
e.g. The scope of this document is the overall scope of the project Project Name, Project Code
1234.

3 Audience

• Include the likely audience of the Requirements [add to or delete from the following list, as
appropriate
The intended audience of this document is:
• Simplilearn Program Manager
• Simplilearn CEO
• Simplilearn Project Manager
• Project Office

4 References
< References>

5 Glossary

5.1 Acronyms

Acronym Description

5.1.1 Definitions

Term Definition

6 Process
• What is the agreed process for developing this document and obtaining its approval?
• What are the steps if change is required?
1. The Project Manager drafts this document.

2. Draft versions (numbered incrementally from version 0.1) will be written for informal review and
circulated to participants in the requirements analysis phase.



3. A formal review will be made of version 1.0D1 of the document. “D1” will indicate that it is the
first draft of the final version. If amendments are made before approval, then the number must
incremented for version control purposes.

4. When all parties agree that all necessary and relevant information is recorded in the document,
version 1.0 will be distributed for approval by the Simplilearn Program Manager, Project
Manager. This version will represent the baseline project plan.

5. Changes to plan will result in the document being updated, given an incremental version
number (e.g. version 1.1) and approved once again. Changes to the document must be clearly
marked in the margin and summarized in the document history.

6. The document, once approved, will be stored in an appropriately named project folder.
• All contributors are working towards the success of the project

7 Open Issues – While Writing Document Only

• This is an author aid whilst writing the document
• Are there any points that still need to be cleared up?
• Is there any information that is outstanding, which needs to be provided?
• A more complete open issue log with status, due completion date, name of person assigned to
resolve the issue may be kept elsewhere, if deemed appropriate.

The following open issues must be clarified prior to the requirements being deemed complete:

ISSUE ID RAISED BY DATE DESCRIPTION OF OPEN ISSUE

8 Project Introduction

8.1 Project Overview

• Fill in the table below, so that the gaps (the white boxes) are completed
• Enter an “x” into the relevant “Project Type” and “Commercial Terms” boxes
• Do not leave blanks
The table below provides an overview of the project:



PROJECT ID
PROJECT NAME
CLIENT ORGANIZATION (NAME & ADDRESS)
CLIENT CONTACT (NAME & ADDRESS)
PROJECT TYPE [ ] Full Development
[ ] Part Development
[ ] Migration
[ ] Enhancement
[ ] Maintenance/ Support
[ ] Any Other ________________
APPLICATION AREA DESCRIPTION
(E.G., INDUSTRY AND FUNCTIONAL AREAS)
PLATFORM/ TECHNOLOGY DESCRIPTION
(OPERATING SYSTEM, DATABASE, LANGUAGE, FRONT-
END, ETC.)
COMMERCIAL TERMS [ ] Time & Material
[ ] Turn Key
[ ] Internally sponsored
START DATE
END DATE
TOTAL ESTIMATED CALENDAR DAYS % VARIANCE THRESHOLD
TOTAL ESTIMATED SIZE % VARIANCE THRESHOLD
TOTAL ESTIMATED EFFORT % VARIANCE THRESHOLD
TOTAL BUDGET % VARIANCE THRESHOLD

Explicit corrective actions will be identified and tracked once the thresholds are crossed.

8.2 Project Description, Scope & Objectives

• Briefly describe the project and what it is, in terms of type of project (e.g. full development or
migration)
• What is the nature of the work being undertaken?
• Provide a reference to the proposal and contract
• What are the objectives of the project?
• What are the characteristics of the project?
• What is the scope of the project?

• What is excluded from scope?
• Where can further details be found?
This section provides a summary over of the project in text:

8.2.1 Project Description

Add text here….
e.g. This project is a full development project to develop a set of processes and guidelines for
software development by Simplilearn.



8.2.2 Project Scope

Add text here….
e.g. The scope of this project to develop the processes and support documentation that will be used
by Simplilearn when developing software.

The scope does not include documentation for any of the potential software development
methodologies other than the waterfall method.

The proposal and contract for this project may be referred to for additional detail (see above,
Reference Documents).

The service levels being worked to in this project are described in the document XYZ.

8.2.3 Project Objectives
Add text here….
e.g. This objective of this project is to deliver a fully documented set of processes for the development
lifecycle, plus support documentation, in a clearly comprehensible format and style.

8.3 Project Environment

• Describe the development environment (in terms of hardware configuration, operating systems
and other software systems)
• Describe the maintenance environment (in terms of hardware configuration, operating systems
and other software systems)
This section describes the environment, in terms of combination of hardware, software and operating
system

8.3.1 Development Environment
Add text here….
e.g. The x system will be running on a x hardware with an x v1.0 operating system.

8.3.2 Maintenance Environment

Add text here….
e.g. The x system will be running on a x hardware with an x v1.0 operating system

8.4 Target Implementation Environment

• Describe the environment where the system will be finally installed and operated
• Which hardware will be used?
• Which Operating System (with version numbers)?
• Which other software systems will be run concurrently?


• Add a diagram of the environment if it is likely to add value and clarity
Add text / diagrams here…
e.g. The software to be developed will be implemented in an environment running on x hardware with
an x v1.0 operating system, and will be running concurrently with x.

8.5 Project Deliverables

• Under deliverable specify the items to be delivered as part of the project (typical deliverables
are Requirements Analysis document, High-Level Design document, Source-code, User and
Operations Manual, etc.). All artifacts to be delivered in the project must be listed here.
• How and to where will they be delivered? (Media and Location)
• How many will be delivered?
• When will they be delivered? (see committed date)
The following table shows a complete list of deliverable to delivered as part of this project:

# DELIVERABLE MEDIA & LOCATION QTY PLAN ACTUAL
DATE DATE

8.6 Client Contact Details

• Provide the:
• Client name
• contact persons for this project and their roles
• the address, phone, fax and e-mails to contact them
The client for this project is <Client Name>.

The key single point of contact for this project at <Client> is:
PROJECT MANAGER
LOCATION
TELEPHONE NUMBER
MOBILE TELEPHONE NUMBER
FAX NUMBER
E-MAIL ADDRESS

If the Simplilearn SPOC cannot be reached the contact person is:
DEPUTY PROJECT MANAGER
LOCATION
TELEPHONE NUMBER
MOBILE TELEPHONE NUMBER
FAX NUMBER
E-MAIL ADDRESS

8.7 Reference Material



• List all documents and other information sources referenced in this plan (state version number
and location)
• Examples of documents referred to are; Project CM Plan, Requirements Analysis document,
User and Operations Manual, Contract, Proposals, Project's Defined Process.
• What is the title?
• Where is it located?
• Who is the author?
• Is it just for information?
• If it is referenced later in the document what reference ID will it have?
• Enter them into the table below.
The table below references all information sources used in establishing this Project Management
Plan:

REF_ID TITLE AUTHOR LOCATION
1 The Title ABD Folder

8.8 Project Terminology, Acronyms and Definitions

• What terms have you used in writing this document that may not be immediately
understandable to all of the intended readers?
• Have you used technical terms that may need to be explained (defined) to other people?
• Are there any acronyms that need to be written in full, to ensure they are understood?
• It is easier to include any terms that you feel may need to be explained pro-actively than to wait
for somebody to ask – or worse; to have the project fail because there was a misunderstanding
over the terms used!
• Add all such terms in the table below

The following table includes all acronyms and terminology to be used in the project, along with an
explanation in non-technical terms:

TERM EXPLANATION
PM Project Manager
SPOC Single Point of Contact

8.9 Referred Project Database & Library

• List the documents and data used from the Project Database and Library.
• Fill out the table below
The following table includes all items referenced from the project database and library, along with a
description of how it was used:



# PROJECT AND DOCUMENT REFERENCED FROM THE PROJECT HOW THE DOCUMENT WAS USEFUL IN PROJECT
DATABASE AND LIBRARY PLANNING

9 Project Organization

9.1 Organizational Structure

This section outlines the organization of the project.
• Describe the project organization structure
• Describe the internal management structure
• What are the organizational boundaries?
• What are the communication interfaces
• Describe / show reporting relationships
• Define individual responsibilities for the various project elements
• If the project has a maintenance component, also specify the maintenance team composition
and organization for the maintenance activities.
• Describes the roles and responsibilities for each team member
• Add a org-diagram for clarity, if possible
Add text here…eg:
The organizational structure of the project is…
The internal management structure is…
Simplilearn team members will report only to the Simplilearn Project Manager. <Client> team
members will report only to the <Client> Project Manager.
The single point of contact between Simplilearn and <Client> is over the Project Managers.

9.2 Organizational Structure

• Identify the person fulfilling a particular role.
• Typical roles are project manager, analysts/ designers, programmers, configuration controller,
PQE, etc.
The following table identifies all the roles required for the project and the individuals who are
responsible for the role and activities.



ROLE RESPONSIBLE PERSON BACK-UP PERSON

9.3 Problems faced in the Current System

• Describe the administrative and managerial boundaries between the project and external
entities.
• Examples of external entities are client, the Quality Group, Business Development Group, etc.?
• Fill out the table below
The table below describes the administrative and managerial boundaries between the project and
external entities:

EXTERNAL ENTITY RELATIONSHIP/ RESPONSIBILITIES FOR PROJECT

10 Project Control

10.1 Project Management Goals

• Describe the goals and relative priorities among quality, schedules, requirements, and budget
for the project
• Typical goals are completion within time and cost, and meeting required quality.
Add text…
e.g. The project must be completed in time and cost, while meeting the required quality.
The quality of the project will be measured by x.

10.2 Assumptions, Dependencies & Constraints

• State the assumptions on which the project is based
• State the external events the project is dependent on (e.g. specify major events like acquisition
of required software/ hardware, recruitment etc., which are critical to the success of the project )
• State the constraints under which the project is to be executed.

10.2.1 Assumptions

The project is based on the following assumptions:



# DESCRIPTION OF ASSUMPTION VALIDATION PHASE IMPACT OF POSSIBLE
VIOLATION

10.2.2 Dependencies

The project has the following dependencies:

# Item to be Provided Provided Acceptance Planned Actual
provided By To Criteria Date Date

DEPENDENCY ID DESCRIPTION OF DEPENDENCY

10.2.3 Constraints

The following constraints exist:

# DESCRIPTION OF CONSTRAINT VALIDATION PHASE IMPACT OF POSSIBLE
VIOLATION

10.3 Information Gathering & Project reporting

• Identify the implications on security of the required changes
• Outline and describe the required level of security
• If appropriate, describe any specific tools that need to be present in order to achieve the desired
level of security. These can include firewalls, proxy servers, or monitoring devices
• What would be the potential impact of a security breakdown?
• What are examples of typical misuse?
Add text here…

10.3.1 Reporting Mechanisms

• Describe the reporting mechanism and report formats for the Project Manager to gather
information from project team members.
• Define the reporting to be done by the Project Manager to the Group Manager and the client.


• Include/ refer to reporting to be done for configuration management and quality assurance
activities.
• For each reporting requirement define:
• Who has to generate the report
• The recipients of the report
• Format and contents of the report
• Frequency of the reporting
• Mode of reporting (on-line/ hardcopy).
• Define how the Project Manager shall use the information to update the project status – this
may be on a Gantt chart/ spreadsheet, or table or using a project management software
package, etc
• Describe how the Project Manager will use the updated project information to understand the
current status and re-plan the project.
Add text here…

The following reports will be created during the course of the project:
REPORT TYPE GENERATED BY GIVEN TO FORMAT & METHOD FREQUENCY
CONTENT
Weekly PM <Client> Predefined PPT Online Weekly
Status Report Format
• Project
Status
• Key
Activities
• Next Steps

10.3.2 Monitoring & Tracking

• Include the reporting required for monitoring and tracking maintenance activities.
• This can include meetings and the use of client call reports, change request status and time
sheets as input.

10.3.3 Meetings

• Define the meetings that shall be held as part of project management. For each meeting, define:
• Attendees
• Coordinator
• Typical topics to be discussed
• Frequency
• Location
The following regular meetings will be held as part of the project:



MEETING TYPE ATTENDEES CO-ORDINATOR TOPICS TO FREQUENCY LOCATION
DISCUSS
Weekly All PM Progress Weekly Simplilearn
Progress Simplilearn Problems
/Team Team Issues
Meeting members Next Steps

10.4 External Communication and Communication Protocol

• List all Communication between Simplilearn and <Client>, plus the responsible people
The following table lists all agreed communication between Simplilearn and <Client> and the
responsible people:
e.g.:
TYPE OF COMMUNICATION SIMPLILEARN PERSON RESPONSIBLE <CLIENT> PERSON RESPONSIBLE
Regular project status
Technical clarifications
User requirements clarifications
Commercial issues
Escalated issues
…..
.....

10.5 Update of Project Plan

• Define the process to be used to review the updated plan, and any authorization for a new plan.
• For cases where the changed plan involves a slippage in cost or schedule, define the process
used to obtain management approval and document it.
E.g. The process to review an update of the project plan is as follows:
1. X
2. Y
3. Z
The authorization process of a new version of the project plan is as follows:
1. X
2. Y
3. Z

If slippage to the project timeline or cost escalation is involved due to a change in the plan then this
must be reported to X and Y in the form of X & Y, stating the reasons why and why it is unavoidable.

10.6 Risk Management Plan

• Identify and assess risk factors (such as contractual risk, technological risk, risk due to size and
complexity of the project, risk in recruitment, training and risks in achieving client acceptance of
the project)
• For all the risks that are identified and being planned for tabulate the risks, their probability,
severity, possible actions to mitigate the risk, the priority, etc.



• Define the frequency for monitoring the risks and performing fresh risk analysis. Define the
threshold for initiating contingency action, and for escalation to senior management and client
• Create a link to the Risk Management Plan spreadsheet
The following risks have been identified and logged, along with contingency plans:

10.7 Configuration Management

10.7.1 Project Configuration Items and SCM Schedule

• List by phase the items that will be produced in the project
• Under Baseline state the version number that will be taken as the baseline
• Under Configuration items list all items to be produced as critical to the project success
• Phase – list the project phase wherein the item is produced
• Under acceptance criteria list what needs to be done to accept the item (e.g. review, review and
approval)
• Under approval authority list who approves
• Under planned and actual date, list the dates the items are planned and then produced
The following items are required to be produced in this project:
BASELINE CONFIGRATION ITEM PHASE ACCEPTANCE APPROVAL PLANNED ACTUAL
CRITERIA AUTHORITY DATE DATE
CUSTOMER SUPPLIED ITEMS
V1.0 • Business User Planning Review PM
Requirements
• Functional
Requirements
• Technical
Requirements

PROJECT SPECIFIC ITEMS
V1.0 Functional design Pre-Project Approval Client
Specifications, (Not for LLD
LLD Specification
Specifications, s)
Prototype
V1.0 Code Planning Fully Tested PM/QM
Code

V1.0 Functional design Design Approval Client
Specifications, (Not for LLD
LLD Specification
Specifications, s)
Prototype
V1.0 Code Developmen Fully Tested PM/QM
t Code



BASELINE CONFIGRATION ITEM PHASE ACCEPTANCE APPROVAL PLANNED ACTUAL
CRITERIA AUTHORITY DATE DATE
V1.0 SIT Test Plan Testing
ST Test Plan
Acceptance Test
Plan
V1.0 Handover
V1.0 Project Closure Project
Report Closure

10.7.2 Naming Conventions

• Specify the naming conventions to be applied for all documents in the project
• Specify the naming convention to be applied for all technical items to be produced in the project
The following naming conventions have been adopted:
CONFIGURATION ITEM NAMING CONVENTION

10.7.3 Version Number Scheme

• Specify the numbering conventions to be applied for all documents in the project
• Specify the numbering conventions to be applied for all technical items to be produced in the
project
The following numbering conventions for configuration items have been adopted:
• Version Number of configured items will start from 1.0
• Each change to a component of a CI increases Version Number by 10%, i.e. 0.1
• When Version Number of the component exceeds 0.9 then the version increases to next higher,
i.e. 2.0
• Within each CI if the components change by over 50% then the CI Version Number changes by
1.0.
• Work in progress version is 0.1.

10.7.4 Controlled Software libraries

• Specify the software libraries required for project success
• To identify the purpose of each of the libraries
• To define the location of each of the libraries
• To specify the restrictions (i.e. Create, Read, Update, Delete) of each of the libraries
The following numbering conventions for configuration items have been adopted:

# Name Type Purpose Location Access Person
Restriction Responsible
1. Dynamic Dynamic code, items Promon Read/Write for SCM
under Database. all
development
2. Control Controlled Item Under Promon Read All, Write QM



Review Database PSM, QM,SCM
3. Static Static Final Product Promon Read All, SCM
Database Write
SCM,PSM

10.7.5 Library backup strategy

• Specify Library and how it will be backed up (under Back-up Nature)
• State the Frequency of the Back-up
• State the Back-up media
• State the location of the Backed-up media
• State how long it will be retained (under retention period)
The following library back-up conventions have been defined:
LIBRARY BACKUP BACKUP BACKUP BACKUP LOCATION RETENTION PERIOD
NATURE FREQUENCY MEDIA
ssb-kkj-vseg1: Complete Daily Tape 15 days
Volume

Details of actual backups taken for the project will be recorded in the Backup Register.

10.7.6 Procedure for the storage of documents and magnetic media

• What magnetic media will be used?
• Why will they be used (e.g., what will be stored on them?)
• How will storage take place?
• Where will they be stored?
The following storage of documents and magnetic media has been identified as being necessary:

10.7.7 Procedure for retrieval and reproduction of controlled items from the library

• Who has access to the libraries?
• What needs to be done to take a document out of the library? (list the steps involved)
The following process has been identified for the retrieval and reproduction of items from the library:

10.8 Change Management Procedure

• What is the Change Management Procedure?
• What steps are involved in getting a change through from a request to rejection or
implementation?
• What categories of change request exist?


The process for assessing and implementing changes to the baselined plan is as follows:

1. The desired change must be entered into PBN as a “Change Request”

2. The Simplilearn PM will allocate the change request to a project team member for
assessment.

3. The change request plus impact analysis will be presented to the Simplilearn PM, CCB

4. A decision will be taken as to whether the change can be accepted or not.

5. The project scope will be amended as appropriate and the changes tracked in this document.

The following Change Request categories exist:
• Nice to Have (the lowest priority category)

• Medium

• Vital (the highest priority category)

The response time to assessing change is as follows:
CATEGORY OF CHANGE RESPONSE TIME
Nice to Have > 8 hours
Medium > 4 hours < 8 hours
Vital < 4 hours

10.9 Configuration Status reporting

• List the Configuration Reports that will be produced
• List who will provide them under “From”
• List who will receive them under “To”
• How frequently are they produced?
• In what format are they produced?
• What procedure will they be produced in?
The Configuration Status Reporting for the Project is as follows:

REPORT FROM TO FREQUENCY FORMAT PROCEDURE
Configuration Status Report SCM PSM/SPM Monthly
Configuration Audit Report QM PSM Monthly

10.10Project Audit Schedule

• When will the project be audited?
• Enter how many audits are planned in the first column
The internal audit schedule for the project is as follows:



# PLANNED DATE ACTUAL DATE NO OF NON-CONFORMANCE(S)
1.
2.
3.



11 Resource Plan

11.1 Person Power

• Specify the number of and type of personnel required for project execution
• Specify activity, start date, duration of needs, and the methods for obtaining, retaining and phasing
out of personnel
• Ensure that these are included in the Work-breakdown, Estimates and Schedules
The following personnel are required to execute the project:

Phase Period Planned Actual
PSM TL TM Total PSM TL TM Total
Planning 1 8+1 29 39 1 8+1 29 39
Design 1 8+1 29 39 1 8+1 29 39
Development 1 8+1 29 39 1 8+1 29 39
Testing
Acceptance
Handover
Project Close
Out

11.2 Training

• Describe the training requirements
• What is the training schedule for the project specific training
• The HR Group will need to be involved for this part of the plan
• Ensure that these are included in the Work-breakdown, Estimates and Schedules.
The following training requirements have been identified:
NAME SKILLS SKILLS TRAINING TRAINING PLANNED ACTUAL
REQUIRED REQUIRED REQUIRED MODE DATE DATE
DATE

11.3 Hardware

• Specify the hardware platform and the quantities to be used for development and for final
installation.
• Specify the source for the hardware – this could be purchase, client supplied hardware, hardware
from other projects, etc.
• Identify the critical hardware resources (if any).



The following hardware requirements have been identified:

Add text here…

11.4 Software

• Specify the software platform and the quantities to be used for development and for final
installation. (This should include compilers, operating systems, editors, utilities, RDBMS, project
management tools, configuration management tools, project quality assurance tools, testing tools,
coding standards checkers, etc.)
• Specify the source for the software– this could be purchase, client supplied software, available
software from other projects, etc.
• Identify the critical software resources (if any).
The following software resource requirements have been identified:

Add text here…

11.5 Other resources

• Specify other resources that will be required for the project (These could include expert consultants,
books, magazines, cell-phones, pagers, manuals, etc.)
The following resource requirements have been identified:

Add text here…

11.6 Budget

• Specify the itemized budget for the project in money terms
• In addition to the manpower effort, training, hardware and software, include the cost related to items
like travel, communication, etc
• Specify the budget by phase of the project
The following monetary resource requirements have been identified:

Add text here…

12 Simplilearn Obligations

12.1 Simplilearn Activities

• Specify the activities that the client is obliged to perform as per the contract or later agreements, the
basis for identifying such action, the manner of monitoring these and the way of coordinating with
the client to ensure these.


• Specify how a delay by the client will be handled (due escalation to Group Manager and equivalent
levels from the client organization, etc.), especially where a delay by the client impacts the cost/
schedule/ quality.
• Specify the responsibility for managing the activities related to coordinating client obligations,
follow-up and record-keeping, escalation, etc.
The following actions are required from <Client> for the successful execution of the project:
• X
• Y
• Z

12.2 Simplilearn Supplied product handling

• Provide the list of client supplied artifacts and involvements in the project, and how it will be
ensured that:
• The artifacts are available as per schedule
• The artifacts received are of the required quality and perform the intended function, and if not, the
client is informed and suitable corrective action taken
• The artifacts are maintained separately and are traceable
• The artifacts are handled as per contractual requirement at the end of the project.
• Specify the version control mechanism to be used, and the specific responsibility for these
products.
The following artifacts have been identified as requiring <Client> action:....
Add text here

13 Verification & Validation

13.1 Review Plan

13.1.1 Artifact Review Strategy

• Identify the artifacts needing to be reviewed
• Identify the review type required (formal, informal)
• When and how will the review take place
• Who will be involved in the review?
The following reviews of artifacts have been identified during the course of the project:
ARTIFACT NAME REVIEW TYPE PLANNED REVIEW ACTUAL REVIEW REVIEWER(S)
DATE DATE



ARTIFACT NAME REVIEW TYPE PLANNED REVIEW ACTUAL REVIEW REVIEWER(S)
DATE DATE

13.1.2 Artifact Approval Strategy

• Identify the artifacts needing to be approved
• Identify the approval type required (e.g. sign-off)
• When and how will the review take place
• Who will be involved in the review?
The following approval of artifacts have been identified during the course of the project:
ARTIFACT NAME APPROVAL TYPE PLANNED ACTUAL APPROVAL APPROVER(S)
APPROVAL DATE DATE

13.1.3 Artifact Approval Criteria

• Identify the artifacts the will be approved
• Identify the factors by which their acceptability can be measured, under approval criteria
The following approval criteria have been identified for each of the artifacts:
ARTIFACT NAME APPROVAL CRITERIA

13.2 Software Quality Assurance Plan

13.2.1 Test Approval Strategy

• Identify the Test Phases in the project
• Identify the Critical Success Factors
• When should the Test Phase come to an end
• When did it come to an end?
• Who approves the test phase as complete?
The following test strategy will be in place for the project:
TEST PHASE NAME CRITICAL SUCCESS PLANNED ACTUAL APPROVER(S)
FACTORS APPROVAL DATE APPROVAL DATE



TEST PHASE NAME CRITICAL SUCCESS PLANNED ACTUAL APPROVER(S)
FACTORS APPROVAL DATE APPROVAL DATE

13.3 Test Strategy Overview

• Test
• Include the strategy for various types of testing (such as unit, integration, system and acceptance).
• Also specify how different aspects like load, stress, usability, maintainability will be tested.
• Who will perform the testing
• When will the testing take place
Refer to the Test Plan for additional details.

14 Quality Recording Handling

14.1 Review Record storage & Handling

• Specify how the review records generated during the reviews will be stored and retrieved
• How will the data be analyzed for feedback to the project?
• Specify the frequency of review record analysis
• Who is (the person(s)) responsible for it?
• What tools and techniques to be used?
• Specify how the feedback obtained by such analysis will be used back within the project and the
responsibility for this.

15 Document reviews and approvals

15.1 Document Reviewers

• Who has received a copy of the document for review and why?

NAME ROLE DATE REASON
Krishna Kumar Program Review for accuracy & completeness with a view to
Manager approval
Simplilearn
Project Manager
<Client> Project
Manager



15.2 Additional recipients of the document

• Apart from the reviewers, who has received a copy of the document and why?

NAME ROLE DATE REASON

15.3 Document Approvers

• Who has received a copy of the document for approval? Did they review it first?
Signing-off the document approves the Project Management Plan as being complete and accurate.
By signing below I acknowledge that I have read the entire contents of this document and accept the
document in this form as reasonably representing all issues, goals, and tasks intended for the scope of
this project. Optionally I may attach modifications to the document and only apply my initials to indicate
that this document needs revisions before it will represent final delivery.

NAME ROLE DATE SIGNATURE OF APPROVAL


Project Management Plan Template

More Related Content

What's hot

Viewers also liked

Similar to Project Management Plan Template

More from Simplilearn

Recently uploaded

In this document

Project Management Plan Template