1.

PROJECT CHARTER

Project Title (ID):

Project Sponsor: Date Prepared:

Project Manager: Project Customer:

Project Purpose or Justification:

Project Description:

High-Level Requirements:

High-Level Risks:

1
Page1 of4
 1. PROJECTCHARTER

Project Objectives Success Criteria Person Approving

Scope:
Scope:

Time:

Cost:

Other:

Summary Milestones Due Date

1.MS1

2.MS2

3.MS3

2
Page2 of4
 1. PROJECT CHARTER

Estimated Budget:

Stakeholder(s) Role

Project Manager Authority Level

Staffing Proposals:

Budget Management and Variance:

3
Page3 of4
 1. PROJECT CHARTER

Technical Decisions:

Conflict Resolution:

Approvals:

Project Manager Signature Sponsor or Originator Signature

Project Manager Name Sponsor or Originator Name

Date Date

Page4 of4

4
 2. INTERNAL STAKEHOLDER REGISTER
Project
Title: Date Prepared:
Revision No:_______________________________

Date Revised:_________________________________________

Contact Information
Role in
Name Designation Project Requirements Remarks
(Contact
(Email)
No)

5
 3. EXTERNAL STAKEHOLDER REGISTER

Project Title: Date Prepared:

Contact Information Classification

Name Position Role Requirements Expectations Influence (Favorability
Mobile Index: A to E)
Email

6
 4. MILESTONE LIST

Project Title: Date Prepared:

Person
Milestone Milestone Description Type Due date Responsibl
e
1. MS1 Project Mgr

1(a). SMS1

1(b). SMS2

1(c). SMS3

2. MS2 Project Mgr

2(a).

2(b).

2(c).

3. MS3 Project Mgr

3(a).

3(b).

3(c).

Prepared By: Approved By:

Project Manager Project Sponsor

Refrence:

(1) Project Charter

(2) Activity List.
(3)
7
5. Gantt Chart

8
 6. ACTIVITY LIST
Project Title: Date Prepared:

ID Activity Description of Work Due Date Person

Responsible

1. MS1

1(a). SMS1

A1

A2

1(b). SMS2

1©.

2. MS2

2(a).

2(b).

2©.

Project Manager

Refrence:

(1) Milestone List.

(2) Network Diagram.

To: All Project Team Members & Activity Owners

Copy To: All Function (Vertical) Area Heads

For Kind Info : Project Sponsor

9
 7. NETWORK DIAGRAM

Project Title: Date Prepared:

Note:
1. At the Project Manager level, Network Diagram to cover all the Sub-Milestones.
2. Stakeholder responsible for each Sub-Milestone to make Network Diagram to cover all relevant
activities.
3. Critical Path & Optimum Schedule to be arrived at for each Network Diagram.
Reference:
(1) Milestone List & Activity List
(2) Action Plan & Schedules

10
 8. COMMUNICATIONS MANAGEMENT PLAN
Date
Project Title: Prepared:

Timing or Receiver/
Stakeholder Information Method Sender
Frequency s
Project Performance Report, Change Log,
Monthly(1st of ArmyHQs,
Customer Issue Log, Minutes of Review Meeting, Fax Mr Ramesh
Month) DGQA
etc….

DRDO

Note: 1. Each Stakeholder will have his own communication plan for his respective team to achieve the
respective Project Goals/Objectives.
2. Issue log and change log are also part of the information to be communicated to relevant
stakeholders at planned intervals.
Glossary of Terms or Acronyms

Attach relevant communication diagrams or flowcharts.

Project Manager
Reference:
(1) Internal& External Stakeholder Register& Project Mgt Plan.

Comunication to Stakeholders& Project Mgt Plan

11
 9. PROJECT MANAGEMENT PLAN
Project Title: Date Prepared:

Revision No: _____________________ Date Revised ____________________________

Project Life Cycle

Phase Key Deliverables

Concept / Marketing Phase(Inputs-RFI, RFQ, Technical Proposals / Specifications, Contract,

GSQR, Design Featrures, Requirements, Orders, etc.
Feasibility & Planning)

Design Phase (Prototype) PDR, CDR, Design / Manufacturing / Testing /Quality

Drawings / Documents, Standards, BOM, FOPM,
Prototytype, etc.

Production Phase(Manufacturing) Product, Equipment, System, etc…

Testing Phase (Evaluation) Test / Acceptance Reports, etc…

Installation Phase (FATS, SATS, etc.) Acceptance Certificates, etc…

Sales Realisation Phase (Payments Receipt) I Notes, Payments, etc…

Maintenance (after installation………) Warranty, AMC, Service, etc….

Project Management Processes and Tailoring Decisions

Knowledge Area Relevant Processes Tailoring Decisions

Integration

Scope

Time

Cost

Quality

Human Resources

Communication

Risk

Procurement

Stakeholders

12
 9. PROJECT MANAGEMENT PLAN
Process Tools and Techniques

Relevant Processes Tools and Techniques (Tailored)

13
Variances and Baseline Management

Scope Variance: Annexure-I Scope Baseline Management: Annexure-I

Schedule Variance: Annexure-II Schedule Baseline Management: Annexure-II

Cost Variance: Annexure-III Cost Baseline Management: Annexure-III

Project Reviews

Periodicity Attendees Agenda (Issues / Points)

Dialy/Weekly Within the Project Team

Fortnightly Within the Organisation

Monthly With the Project Sponsor

Quarterly With Major Stakeholders

Half Yearly With High Level Stakeholders

(Customer)

Yearly With High Level Stakeholders

(Customer)

Note: 1. Agenda to be decided by the Project Manager for all the review Meetings.
2. All Reviews with Decisions should be formally recorded and distributed to all
relevant stakeholders.

Prepared By: Approved By:

Project Manager Project Sponsor

Reference:

(1) Project Charter& All Subsidiary Plans

(2) All Subsidiary Plans

14
 10. QUALITY MANAGEMENT PLAN

Project Title: Date Prepared:

Revision No: _______________________ Date Revised ____________________________

Quality Rolesand Responsibilities

Role Responsibilities

1.Project Manager 1.

2. Product Design Manager 2.

3. Quality Manager 3.

4. Production Manager 4.

5.Testing Manager 5.

6. Purchase Manager 6.

7. Finance Manager 7.

8. Sales & Marketing 8.

9. Customer Support Manager 9.

10. HR Manager 10.

11. Services 11.

Quality Planning Approach: MQAP Document

1. Reference Standards:
2. Quality Flow Diagram/Charts:
3. Vendor Development Plan:
4. Test Plans:
5. Qualification Plans:
6. Acceptance Criteria:
7. Approving Agency:
8. Exceptions:
9. Adequacy Audit:
10. Amendment Methodology/Procedure:

15
 10. QUALITY MANAGEMENT PLAN

Quality Assurance Approach

1. Statistical Process Control (SPC) Methodology: (For All Functions / Departments)

2. Quality Audits:
(a) Internal Process Audits (By other Unit / SBU Auditor):
(b) Internal Product Audits (By other Unit / SBU Auditor):
(c) Customer Audits / Second Party (Process):
(d) Customer Audits / Second Party (Product):
(e) External / Independent / ThirdParty Audits (QMS Audit):
(f) Export Audits by C-QA (As Applicable):
3. Supplier Audits:
(NOTE:Periodicity of these Audits to be decided by the Project Team.)

Quality Control Approach

1. Product Performance
(a) Inspection Plan: (Training, Timing, Metrology, Instruments, Type of Tests, TMR, etc.)
(b) Sampling Plan:
(c) Calibration Plan:
(d) Vendor Acceptance Criteria:

2. Project Performance
(a) Cost Permormance Index (CPI):
(b) Schedule Permormance Index (SPI):

Quality Improvement Approach

1. TQM:
2. CAPA:
3. Cross Functional Teams:
4. Benchmarking:
5. Six Sigma Projects:
6. QCC:
7. Suggestion Scheme:
8. Recognition / Incentives / Awards:

Prepared By: Approved By:

Project Manager Project Sponsor

Reference:

(1) Project Management Plan

(2) Detailed Quality Plans

16
 11. RISK REGISTER

Project Title: Date Prepared:

Impact
Impact on (Scale1- Total
10) Score=
Probabili Response Plan
(Prob)
S ty S
Risk Risk L I Q * (Sum (Mitigation Responsible
A S c
ID Statement E E M (Scale1- u C of the Plan) Party
F c h four
N G A 10) a o
E o e impact
V A G li s
p d
T
L E t t Scores
Y e ul )
y
e
1 A y - y - Must have a plan

2 B - - - - 5 5 5 4 5 95

3 C 105 Priority I in B,C & D

4 D 55

Note:
1. For each risk statement, fill up Impact on ENV / SAFETY / LEGAL / IMAGE,
Probability, Impact on scope, quality, schedule, cost, and TOTAL SCORE columns.
2. Mitigation Plans are mandatory for all the Risks identified.
3. The document number detailing the mitigation plan is tobeentered in Response
Plan column.
4. For risks, where there is impact on ENV / SAFETY / LEGAL/ IMAGE, the Risk owner
for the mitigation plan is the Project Sponsor and it has to have the Response /
Mitigation Plan Mandatorily.
5. The risks are prioritized, based on the Total Score.
6. Cut off score is to be decided.
7. Risk owner for the mitigation plan for risks more than cut off score is Project
Manager.
8. Risk owner for other risks is process owner decided at the Sub mile stone level.

17
 Revised
Revised Impact Revise
Impact (Scale1- d
10) Score= Comments
Revised
S (Prob) Describe whether the risk is
Risk Risk L I Probabili S
Q * (Sum totally avoided, or remaining
ID Statement A ty(Scale1 S c
E E M u C of the with lower impact, etc.
F -10) c h
N G A a o four
E o e
V A G li s impact
T p d
L E t t Scores)
Y e ul
y
e
.

Prepared By:
Approved By:

Project Manager
Project Sponsor

Reference:

(1) Project Charter

(2) All Subsidiary Plans

18
 12. ISSUE LOG

Project Title: Date Prepared:

Issue ID Date Raised Category Issue Impact on Urgency

by Objectives

Note: 1. Objectives means scope, time, cost, and others(as identified in the project charter)
2.Issues can be raised by the project team members or the stakeholders

Issue ID Responsible Party Actions Due Date Status Date Comm

Resolved ents

3. The project manager is the custodian of this document and nesponsible for resolving every issue
either directly or by sub delegation.
4. Issue log is an input to manage Communications process and it is conveyed to all relevant
stakeholders at planned inervals.

Project Manager
Reference:

1. Project Charter and Stakeholder Register

2. Comunication to Stakeholders &Cost / Schedule / Risk /Quality Management
Plan
19
 13. PROJECT PERFORMANCE REPORT

Project Title: Date Prepared:

Project Manager: Sponsor:

Accomplishments for This Reporting Period

1.

2.

3.

4.

5.

6.

Accomplishments Planned but Not Completed This Reporting Period

1.

2.

3.

4.

Root Cause of Variances

20
 13. PROJECT PERFORMANCE REPORT

Impact to Upcoming Milestones or Project Due Date

Planned Corrective or Preventive Action

Funds Spent This Reporting Period

Root Cause of Variances

21
 13. PROJECT PERFORMANCE REPORT

Impact to Overall Budget or Contingency Funds

Planned Corrective or Preventive Action

Accomplishments Planned for Next Reporting Period

1.

2.

3.

4.

Costs Planned for Next Reporting Period

22
 13. PROJECT PERFORMANCE REPORT

New Risks Identified

Risk

Issues

Issue

Comments

Note: This report will be prepared by the Project Manager with inputs from Persons responsible for
each Sub Milestone using the same template.
2. The final Project Report to be prepared by the Project Manager at the end of the Project.

Signature: _______________
Name: __________________
Role: ___________________

Reference:
(1) Project Management Plan (PMP)
(2) Communication to Stakeholders & PMP
23
 14. LESSONS LEARNED

Project Title: Date Prepared:

Project Performance Analysis

What Can Be
What Worked Well
Improved

Requirements definition and

A1 A2
management

Scope definition and management B1 B2

Schedule development and control C1 C2

Cost estimating and control D1 D2

Quality planning and control E1 E2

Human resource availability, team

F1 F2
development, and performance

Communication management G1 G2

Stakeholder management H1 H2

Reporting I1 I2

Risk management J1 J2

Procurement planning and

K1 K2
management

Process improvement information L1 L2

Product-specific information M1 M2

Other N1 N2

24
 14. LESSONS LEARNED
Risks and Issues

Risk Risk or Issue

Response Comments
ID Description

Quality Defects

Defect Description Resolution Comments

Vendor Management

Issue Resolution Comments

Vendor

Other

Areas of Exceptional Performance Areas for Improvement

25
Note: This should be a detailed record, self-explanatory to any other Project Manager referring to it in
future.

Project Manager: _______________

Name: ________________________

Reference:
(1) Final Project Report &Project Management Plan (PMP)
(2) Project Closure, Communication to Stakeholders & KMS

26
 15. PROJECT CLOSE-OUT

ProjectTitle: Date Prepared: ProjectManager:

Project Description

Performance Summary

Project Objectives Completion Criteria How Met

Scope

Quality

Time

Cost

Notes: 1. Project Manager is responsible till the revenue is realized from the customer (No Sundry
Debtors).
2. Ensure all the project objectives have been met. Close all purchase / sub-contract orders,
Prepare the Lessons Learnt,
Release the leftover material s as “free stock”, Release all Other resources (Infrastructure,
Equipment & HR). Thereafter,
Prepare the Interim Project Closure Report.

Prepared By:
Approved By:

Project Manager Project Sponsor

Reference:

(1) Accepted Deliverables, Lessons Learnt, PMP

(2) Final Financial Report &Project Closure
27