IRM-5231-19 A
PROJEC
T
MANAGEMENT PLA
N
PCN 186 523119 00
DEPARTMENT OF THE NAV
Y
HEADQUARTERS UNITED STATES MARINE CORP
S
WASHINGTON, D
.C
. 20380-000
1
From
: Commandant of the Marine Corp
s
Subj
:
INFORMATION RESOURCES MANAGEMENT
(IRM) PROJECT
MANAGEMEN
T
PLA
N
Ref
:
(a) MCO P5231
.1
A
(b) MCO 5271
.
1
(C)
MCO P5600
.3
1
Encl
: (1) IRM-5231-19
A
1.
PURPOSE
.
To provide guidance and instructions on th
e
development of Project Management Plans as required by referenc
e
(a)
.
2.
CANCELLATION
.
IRM-5231-19
.
3.
SUMMARY OF REVISION
.
This revision adds a discussion o
f
project management tools and techniques, expands the conten
t
description, adds a figure to describe the relationship of al
l
project tasks and documentation, and adds appendixes o
n
acronyms, abbreviations, and references
.
4.
AUTHORITY
.
This standard is published under the authorit
y
of reference (b)
.
5.
APPLICABILITY
.
The guidance contained in this publicatio
n
is applicable to all Marine Corps personnel responsible for th
e
preparation of a Project Management Plan in support of Automate
d
Information System (AIS) projects managed per reference (a)
.
This standard is applicable to the Marine Corps Reserve
.
6.
DISTRIBUTION
.
This technical publication will b
e
distributed as indicated
. Appropriate activities will receiv
e
updated individual activity Table of Allowances fo
r
Publications
. Requests for changes in allowance should b
e
submitted per reference (c)
.
7.
SCOPE
a.
Compliance
.
Compliance with the provisions of thi
s
publication is required unless a specific waiver is authorized
.
b.
Waivers
.
Waivers to the provisions of this publicatio
n
will be authorized only by CMC (CC) on a case by case basis
.
IN REPLY
REFER
1
0
5231/19 A
CCIS-4
5
APR 2 1 19S9
5231/19 A
CCIS-4
5
APR 2 1 198
9
Subj
: INFORMATION RESOURCES MANAGEMENT (IRM) PROJECT MANAGEMEN
T
PLA N
8.
RECOMMENDATIONS
.
Recommendations concerning the contents o
f
this technical publication should be forwarded to CMC (CCI) vi
a
the appropriate chain of command
. All recommended changes wil
l
be reviewed upon receipt and implemented if appropriate
.
9.
SPONSOR
.
The sponsor of this technical publication is CM
C
(CCI)
.
R
. L
. PHILLIP
S
Brigadier General, U
. S
. Marine Corp
s
Director, Command, Control, Communication
s
and Computer (C4) Divisio
n
DISTRIBUTION
:
LI
P
L1
Q
L1
R
7000006
(1
)
7000007
(2
)
7000012
(2
)
7000014
(2
)
7000015
(2
)
7000017
(1
)
7000019
(1
)
7000020
(1
)
7000029
(40
)
7000031
(10
)
7000045
(1
)
7000050
(10
)
7000051
(4
)
7000062
(2
)
7000066
(2
)
7000067
(1
)
7000070
(1
)
7000071
(20
)
7000072
(10
)
7000093
(2
)
7000142
(1
)
7000148
(4)
Copy to
: 8145001
2
UNITED STATES MARINE CORP
S
Information Resources Management (IRM
)
Standards and Guidelines Progra
m
Project Management Pla
n
IRM-5231-19
A
APR 2 1
1989
ENCL (1)
PROJECT MANAGEMENT PLA
N
IRM-5231-19
A
RECORD OF CHANGE
S
Log completed change action as indicated
.
Chang
e
Number
Date o
f
Change
Dat
e
Received
Dat
e
Entered
Signature of Perso
n
Entering Change
ii
i
PROJECT MANAGEMENT PLA
N
IRM-5231-19
A
PUBLICATION TABLE OF CONTENTS
Paragrap
h
Page
Chapter
1
GENERA
L
S
ection 1
. INTRODUCTION
1
.1
.
1-
3
Section 2
. SCOPE
1
.2
.
1-
3
Section 3
. APPROACH
1
.3
.
1-
4
Chapter
2
CONTENT AND FORMA
T
Section 1
.
DOCUMENTATION STANDARDS
2
.1
.
2-
3
Section 2
. DOCUMENTATION DEPENDENCIES
2
.2
.
2-
3
APPENDIXE
S
A.
REFERENCES
A-
1
B.
PROJECT
MANAGEMENT
PLAN TABLE OF CONTENTS
B-
1
C.
PROJECT
MANAGEMENT
PLAN CONTENT DESCRIPTION
.
C-
1
D.
ACRONYMS
AND
ABBREVIATIONS
D-
1
v
PROJECT MANAGEMENT PLA
N
IRM-5231-19
A
LIST OF FIGURE
S
Figure
s
1-01
Responsibility/Task Matri
x
1-02
Work Breakdown Structur
e
1-03
Activity Precedence Diagra
m
1-04
PERT Networ
k
1-05
Gantt Char
t
2-01
Precedence Relationship
s
vii
PROJECT MANAGEMENT PLA
N
IRM-5231-19
A
Chapter Table of Content
s
Chapter
1
GENERAL
Paragraph
Pag
e
Section
1
.
INTRODUCTION
1
.1
.
1-
3
Section 2
.
SCOPE
1
.2
.
1-
3
Contents
1
.2
.1
.
1-
3
Section 3
.
APPROACH
1
.3
.
1-
4
General
.
.
. .
. .
. .
.
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
.
1
.3
.1
.
1-
4
Tools and Techniques
1
.3
.2
.
1-
4
Approval
1
.3 .3
.
1-4
PROJECT MANAGEMENT PLA
N
IRM-5231-19
A
Chapter 1
.
GENERA
L
1
.1
.
INTRODUCTION
.
This Project Management Plan (PMP) standar
d
provides guidance for developing a plan to accomplish th
e
procurement or the design, development, and deployment o
f
automated information systems (AIS's)
. The PMP
developed
usin g
this standard will
provide
the plans, procedures, schedules
,
documentation requirements, and evaluation criteria for al
l
activities necessary to execute and control an AIS project
.
Appendix A provides a list of references associated with lif
e
cycle management and AIS development
.
1
.2
.
SCOPE
.
The PMP is part of the planning process initiate
d
by the Project Manager (PM) as the first step in the Concept
s
Development Phase of the project life cycle
. At specific point
s
in the life cycle, the PMP is revised to reflect any addition
s
or changes such as
:
a.
purchase of new hardware or software
,
b.
changes in requirements or constraints, and/o
r
c.
installation of telecommunications equipment
.
1
.2 .1
.
Contents
.
Appendixes B and C describe PMP format an
d
content requirements
. The format for project deliverable
s
(e
.g
., the PMP) is guided by IRM-5320-02 (Project Deliverabl
e
Style Manual)
. In brief, a PMP shall contain the followin
g
items
:
a.
The purpose of the PMP
.
b.
A brief description and statement of purpose of th
e
system being developed or acquired
.
c.
Organizational responsibilities and relationships
.
d.
A description of all the developmental and projec
t
management tools that will be used to manage the project
.
e.
Descriptions of all tasks to be performed
.
f.
Time Schedules for accomplishing those tasks
.
g.
Resources required to support the development effort
.
h.
A list of support plans to be developed
.
PROJECT MANAGEMENT PLA
N
IRM-5231-19 A
1
.3
.
APPROAC
H
1 .3 .1
.
General
.
The PMP serves as a guide to direct an AI
S
project through its life cycle in an efficient manner
. Due t
o
the dynamics of AIS acquisition and development, the PMP must b
e
refined throughout the life of the project
.
1 .3
.2
.
Tools and Techniques
,
.
This standard provides guidanc
e
regarding the planning data to be considered when developing th
e
initial PMP
. This data should be reflected in and controlled b
y
some form of planning and tracking vehicle
. Figures 1-0
1
through 1-05 are samples of planning charts which may be use
d
for this purpose
. Any appropriate alternative methods which ar
e
found to be effective as
planning and tracking vehicles may b
e
used
.
a.
Figure 1-01, Responsibility/Task Matrix
.
This matri
x
is used to identify the tasks that each member of the projec
t
team are responsible for performing
.
b.
Figure 1-02, Work Breakdown Structure (WBS)
.
A WB
S
defines work from the highest level to the lowest level o
f
detail necessary to describe the project tasks to b
e
accomplished
. Individual project tasks are identified b
y
breaking down the high level work packages into the lower leve
l
work packages
. A WBS not only identifies work packages but-als
o
the start date, duration, and expected completion date of eac
h
work package
.
c.
Figure 1-03, Activity Precedence Diagram (APD)
.
An AP
D
describes the planned sequential relationship of projec
t
activities as defined in the WBS
.
d.
Figure 1-04, PERT Network
.
A Program Evaluation Revie
w
Technique (PERT) Network is a project management tool used t
o
identify the precedence and duration of project events (i
.e
. ,
milestones) and activities as defined in the WBS
.
e.
Figure 1-05, Gantt Chart
.
A Gantt
Chart
is a projec
t
management tool used to graphically display the planned schedul
e
of activities, events, and deliverables
. A Gantt Char
t
identifies the planned start date, duration, and completion dat
e
for each task
.
1
.3 .3
.
Ap
proval
.
The initial PMP shall be presented to th
e
functional manager or steering group for approval
. Essentia
l
items from the PMP (and its updates) will be included in th
e
System Decision Papers (SDP's) submitted to the approva
l
authority at the conclusion of each phase of the project lif
e
cycle
. In this way, the approval authority is approving th
e
contents of the PMP
.
Responsibility/Task Matri
x
IMPLEMENTATIO
N
TEA
M
BILLE
T
RESPONSIBILITIES
/
TASKS
TAS
K
ID
IMPLEMEN
-
TATIO
N
TEA
M
LEADER
COMPUTE
R
SYSTE
M
ANALYST
FUNC
-
TIONA
L
SYSTE
M
ANALYST
COMPUTE
R
PROGRAM
-
NCR
USE
R
COMMAND
FUNC
-
TIONA
L
USER
SIT
E
O
P
PERSON
-
NEL
DAT
A
BAS
E
MANAGER
DAT
A
BAS
E
ADMINIS
-
TRATOR
SIT
E
DAT
A
BAS
E
ADMINIS
-
TRATOR
D
A
RE
P
IDENTIFY POINT OF CONTACT
3
.1
P
CREATE TRAINING SCHEDULE
3
.2
p
ARRANGE SITE TRAINING
3
.3
p
X
CONDUCT SITE TRAINING
3
.4
p
X
X X
X
IDENTIFY BRIEFING ATTENDEES
4
.1
p
X
ARRANGE BRIEFING FACILITIES
4
.2
p
X
CONDUCT BRIEFING
5J
P
X X X X X
X
X
CONDUCT IMPLEMENTATION
5
.2
p
X
X
X X X X X
X
PROJECT MANAGEMENT PLA
N
IRM
—
5231
— 19
A
Work Breakdown Structur
e
The Work Breakdown Structure (WBS) defines the work to be performed from the highest level to th
e
lowest level of detail necessary to describe the tasks to be accomplised
. It is the breakdown that define
s
the individual work to be performed
. An example of a WBS for a task is
:
198 3
JUL
AUG
SEP
OCT
NOV
DEC
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OC
T
301 0
GENERAL DESIGN SPEC
S
FIN MGM
T
SCREENS
3210
DDS
315
0
CODE & TES
T
FIN MGM
T
EDITS
3220
DOS
325
0
CODE & TES
T
WEEKLY IDB
3320
335
0
DS&D7
DDS
CODE & TES
T
MILSTRI
P
MILSTRAP
345
0
CONTRACTS
1_342
0
DDS
CODE & TES
T
MISC TRANS
1352
0
DDS
3550
CODE & TEST
FIGURE 1
— 0 2
Work Breakdown Structur
e
PROJECT MANAGEMENT PLAN
,
IRM
—
5231—19
A
FIGURE 1—0
3
Activity
Precedence Diagra
m
Activity Precedence Diagra
m
The Activity Precedence Diagram (APD) is the mechanism by which the planned sequence of events i
s
first addressed
. Each WBS member is shown on the diagram as a discrete event, connected from the lef
t
to all other WBS members which must precede it
. An example is
:
438
2
Publis
h
Documentatio
n
Users Manual
s
Computer OPN
S
4381
P
T
Revie
w
Implementatio
n
Pla
n
PM
4383
4385
438
6
Verity
/
Prepar
e
Sit
e
HWS/S
W
PM
Live Tes
t
Paralle
l
Processin
g
PM
Use
r
Acceptanc
e
Repor
t
P
M
438
4
J
Use
r
Trainin
g
PT
1
—
7
PROJECT MANAGEMENT PLA
N
IRM-5231-19
A
FIGURE 1-0
4
PERT Networ
k
PERT Networ
k
A PERT network is a tool for planning and tracking event
s
and activities with regard to the duration of activitie
s
and the precedence of other events and activities
. Th
e
chart represents the network of activities required t
o
implement a system or subsystem
. Events are represente
d
by circles
. Activities are represented by the line
s
connecting the circles
.
Start/En
d
Activity
Description Duration
Date
s
Identify point of contact
1
da
ya
b
Create training schedule
4
day
s
c
Arrange site training
2
day
s
d
Conduct site training
9
day
s
e
Identify brief attendees
1
day
f
Arrange brief facility
2
day
s
g
Conduct brief
1
day
h
Conduct implementation
9
days
1-8
PROJECT MANAGEMENT PLA
N
IRM—52 31
—
19
A
Gantt Char
t
The Gantt chart is the mechanism by which the planned schedule of events and deliverables is derived fo
r
the tasks
. Preliminary estimates of the manpower and duration of each WBS member are used with th
e
Activity Precedence Diagram to develop a schedule for each lower level WBS member
. An example is
:
WORK PRACTICE
NOVEMBER 1
2
WEEK
1
NOVEMBER 1
9
WEEK 2
NOVEMBER 2
6
WEEK 3
DECEMBER
3
WEEK 4
DECEMBER 1
0
WEEK
5
438
1
Revie
w
Implementatio
n
Pla
n
Publis
h
Documentatio
n
Users Manua
l
Verity
/
Prepar
e
Site HW/S
W
Use
r
Trainin
g
Live Tes
t
Paralle
l
Processin
g
Use
r
Acceptanc
e
Report
FIGURE 1—0
5
Gantt Char
t
PROJECT MANAGEMENT PLA
N
IRM-5231-19
A
Chapter Table of Content
s
Chapter
2
CONTENT AND FORMAT
Paragraph
Pag
e
Section 1
.
DOCUMENTATION STANDARDS
2
.1
.
2-
3
Project Tasks/Schedule
2
.1 .1
.
2-
3
Level of Detail
2
.1
.2
.
2-
3
Evaluation Criteria
2
.1
.3
.
2-
3
Section 2
.
DOCUMENTATION DEPENDENCIES
2
.2
.
2-3
PROJECT MANAGEMENT PLA
N
IRM-5231-19
A
Chapter
2
CONTENT AND FORMA
T
2
.1
.
DOCUMENTATION STANDARDS
.
The Project Management Pla
n
(PMP) shall be developed in accordance with the criteri
a
described in the following paragraphs
.
2
.1 .1
.
Project Tasks/Schedule
.
In documenting projec
t
activities and events via the PMP, the project manager shall us
e
the table of contents described in Appendix B and the conten
t
descriptions described in Appendix C
. Project support plan
s
will be included as appendixes to the PMP
.
2
.1
.2
.
Level of Detail
.
The project schedule should identif
y
all major activities and events and should become progressivel
y
more detailed as the project moves through the life cycle
. Tas
k
lists and work package descriptions should be detailed enough t
o
permit adequate monitoring of progress
.
2
.1 .3
.
Evaluation Criteria
.
When evaluating the PMP fo
r
completeness and accuracy, the reviewer must, as a minimum
,
ensure that the following requirements are met
.
a.
All sections and paragraphs in Appendix B, "Projec
t
Management Plan Table of Contents", are addressed
.
b.
The title of any section or paragraph deemed no
t
appropriate is listed as "not applicable"
.
c.
The content of all sections and paragraphs is complete
d
per Appendix C, "Project Management Plan Content Description"
.
d.
The purpose and scope of the plan is consistent wit
h
the intent of this standard
.
e.
The control, status accounting, and auditing function
s
conform to accepted methodologies
.
f.
The plan is comprehensive, definitive, and feasible
.
2
.2
.
DOCUMENTATION DEPENDENCIES
.
The documentation governed b
y
this standard may rely on the content of other projec
t
deliverables and/or standards
. Figure 2-01, "Precedenc
e
Relationship", shows those project deliverables, reviews
,
baselines, and milestones which have an impact on or must b
e
reflected in the PMP
. Appendix D provides a list of acronym
s
and abbreviations that will be useful in reading figure 2-01
.
PROJECT MANAGEMENT PLA
N
IRM-5231-19 A
I
SYSTE
M
DEVELOPMEN
T
LCY PHASES
I
C
S510
5
ANALYSI
S
PROJEC
T
INITIATION
I
CONCEP
T
DEVELOPMENT
DEFINITION AND DESIGN
DEVELOPMENT
-
DEFINITION
-
GENERA
L
DESIGN
DETAILE
D
DESIGN
CODE
-
TESTING
INTEGRATION AN
D
ACCEPTANCE
II'LEY
-
ENTATIO
N
LCW SDP
SD
P
-
1
r-
:
:
—1
i
---)
PM
CSp ecifics
tions
YENS
-
J
I
----
Y
1
0
~~~~
---
~
SGC
+
---) RS -
Updat
e
IS
pD dat
é
RS
D
0
J
L
SIT
->
SAT
IIL"LEY
-
(Functional
E
-
TATIO
N
I
TRAIN
-
Requirements)
ING
SDY
UNI T
f ica-
>
EA
FRD
)
.
GDS
->
.
DDS
-)
CODE
-)
.
PC A
Speci
.
-
tions
-
-
EA
FC A
-~
-
USE
R
TEST
~-
P I E
0 Y
V
SP
A
Initiat
e
-) UY
Update
>-
Finalize
T L
L
E
0
PLANS
I
—>
•
—
~
CIL'
DBP L
TP
>
>
COY Y A
->• IP
- ~
`)
DBC
->-
~--
>
PYP
)
pdat
e
u
E
T
N
I
finaliz
e
—)QA
.
~`-
--
T
o
T
P
->
1
ADP
>-
->
EA A N
TR
P
~-
—
>
Update
T
--
PIL'
—
u
1
->•
TRP
TSP
>-
0
—
-
•—
>
UY
Y
PIE'
)
-
Update
1 P
L
___
)
OA PHASE
1 2 3
-)±
DBC
4
ANALYSIS
r
--~
—
—
—
REVIEWS
SRB
PDB CDR SIR
SIR
SE
E
, 1
f I ~
BASELINE
CONCEPT
FUNCTIONAL
ALLO-
PRODUCT
OPERA
-
CITED
TIONA
L
MILESTONE
10
1
2
3 1
FIGURE 2-0
1
Precedence Relationshi
p
2-
4
PROJECT MANAGEMENT PLA
N
IRM-5231-19
A
Appendix
A
REFERENCE
S
1.
MCO P5231
.1A Life Cycle Management of Automated Informatio
n
Systems (LCM-AIS) Project
s
2.
Department of Defense Standard 7935 (DOD-STD-7935) Automate
d
Data Systems (ADS) Documentation
.
3.
Systems Development Methodology (SDM) Overview (IRM-5231-01
)
4.
SDM - Developer Perspective (IRM-5231-02)
PROJECT MANAGEMENT PLAN
,
IRM-5231-19 A
Appendix
B
PROJECT MANAGEMENT PLAN TABLE OF CONTENT
S
Project Management Pla
n
SECTION
1
.
1
.
1
1
.
2
1
.
3
1
.
4
SECTION 2
.
2
.
1
2
.
2
2
.3
Introductio
n
Purpos
e
Project Descriptio
n
Reference
s
Terms and Abbreviation
s
Project Managemen
t
Responsibilitie
s
Project Organizatio
n
Project Control
s
Tasks and Schedul
e
Task
s
Life Cycle Tasks and Milestone
s
Quality Assurance (QA) Inspections, Audit
s
and Review
s
3
.1
.3
Configuration Management (CM) Audits
,
Reviews, and Baseline
s
Trainin
g
Schedul e
Level of Detai
l
Schedule Technique
s
SECTION 4
.
Resource Requirement
s
4
.1
Manpowe
r
4
.2
Fundin
g
SECTION 5
.
Acquisition Strateg
y
SECTION 3
.
3
.
1
3
.1
.
1
3
.1
.
2
3
.1
.
4
3
.
2
3
.2
.
1
3
.2
.
2
SECTION 6
.
Support Plans
PROJECT MANAGEMENT PLA
N
IRM-5231-19 A
Appendix
C
PROJECT MANAGEMENT PLAN CONTENT DESCRIPTIO
N
SECTION 1
.
INTRODUCTIO
N
This section shall present the objectives of the Projec
t
Management Plan (PMP) and other general information about th
e
system being acquired or developed
.
1
.1
PURPOS
E
This paragraph shall contain the purpose of the PMP
. Th
e
following is an example of what might appear here
:
"This document provides plans, procedures, schedules
,
documentation requirements, and evaluation criteria for al
l
activities necessary to administer and control the AIS projec
t
described below
.
"
1
.2
PROJECT DESCRIPTIO
N
This paragraph shall provide background information about th
e
system being acquired or developed
.
1
.3
REFERENCE
S
This paragraph shall provide a brief summary of reference
s
(documents and meetings) that are applicable to the acquisition
,
design, development, deployment, operation and maintenance o
f
the system
.
1
.4
TERMS AND
ABBREVIATION
S
This paragraph shall contain any terms and abbreviations tha
t
are unique to this document
.
SECTION 2
.
PROJECT MANAGEMEN
T
2 .1
RESPONSIBILITIE
S
This paragraph shall describe the location of the projec
t
management team/office in the overall organization and outlin
e
the relationships and responsibilities of all levels o
f
management
.
2
.2
PROJECT
ORGANIZATIO
N
This paragraph shall describe the composition an
d
responsibilities of the project team/office
. This paragrap
h
should reference the responsibility/task matrix established i
n
conjunction with paragraph 3
.1 below
.
PROJECT MANAGEMENT PLA
N
IRM-5231-19
A
2
.3
PROJECT CONTROLS
This paragraph shall describe the developmental and projec
t
tools that will be used to control the project (e
.g
., automate
d
cost estimators or project schedulers)
.
SECTION 3
.
TASKS AND
SCHEDUL
E
Development of a Project Management Plan (PMP) is the firs
t
action taken by the project manager following his/he
r
appointment and chartering
. One of the most important function
s
of the PMP is to list the remainder of the actions the projec
t
manager plans to take during the life of the project
.
3
.1
TASK
S
This paragraph shall contain a set of project task lists usin
g
the categories discussed below
. These tasks should then b
e
incorporated in a responsibility/task matrix per figure 1-01
.
3
.1 .1
Life Cycle Activities and Milestone
s
This paragraph shall provide a list of life cycle managemen
t
(LCM) activities and milestones as described in the curren
t
version of MCO P5231
.1
. The activities should be grouped by LC
M
phase and shall include such things as determination an
d
analysis of requirements, budgeting for project activities
,
acquisition or design and development of hardware and software
,
and development of supporting documentation and projec
t
deliverables
. This paragraph shall indicate that each LCM phas
e
ends with the submission of a System Decision Paper (SDP) to th
e
project approval authority and that approval of the SD
P
constitutes achievement of an LCM milestone
.
3
.1
.2
Ouality Assurance Inspections, Audits, and Review
s
This paragraph shall provide a list of the inspections, audits
,
and reviews to be performed by project quality assurance (QA
)
personnel
. Depending on the size and complexity of the project
,
a separate QA Plan may be required
. See IRM-5231-10 (QA Plan
)
for details regarding QA
.
a.
An inspection is a formal evaluation of a projec
t
deliverable to determine conformance to predetermined qualit
y
requirements
. This paragraph shall list all such planne
d
inspections
.
b.
An audit is an independent assessment of compliance wit
h
software requirements, specifications, baselines, standar
d
procedures, instructions, codes, contractual and licensin
g
requirements, and production configurations
. QA audits normall
y
occur at the end of each life cycle phase
. This paragraph shal
l
list all such planned audits
.
PROJECT MANAGEMENT PLA
N
IRM-5231-19
A
c
. A review is an evaluation of software products regardin
g
form and technical content
. It is conducted by projec
t
management for the purpose of detecting and correctin
g
deficiencies
. This paragraph shall list all such planne
d
reviews
.
3
.1
.3
Configuration Management Audits, Reviews, and Baseline
s
This paragraph shall provide a list of the audits and reviews t
o
be performed by project configuration management (CM
)
personnel
. This paragraph will also include a list of C
M
baselines that will be established during the life of the AI
S
project as a result of CM reviews
. Depending on the size an
d
complexity of the project, a separate CM Plan may be required
.
See IRM-5231-09 (CM Plan) for details regarding CM
.
a
. The following CM audits will normally be listed
.
(1)
Functional Configuration Audit (FCA) - a forma
l
audit to validate that the development of the configuration ite
m
being audited has been completed satisfactorily, has achieve
d
specified performance and functional characteristics, an
d
complies with operation and support documentation
.
(2)
Physical Configuration Audit (PCA) - a technica
l
examination
of a designated configuration item to determine it
s
conformance to the technical documentation definition
.
b
. The following CM reviews will normally be listed
.
(1)
Systems Requirements Review (SRR) - a review o
f
the system requirements specifications and preliminary suppor
t
plans to determine if the functional requirements are complete
,
feasible, verifiable, and testable
. Successful completion o
f
this review results in the establishment of the
Functiona
l
Baseline
.
(2)
Preliminary Design Review (PDR) - a revie
w
conducted upon completion of the general design to evaluate th
e
progress, technical adequacy, quality, and testability of th
e
selected design approach
.
(3)
Critical Design Review (CDR) - a review performe
d
at the conclusion of the design phase to determine th
e
acceptability of the detailed design, the performance and tes
t
characteristics of the design solution, and the adequacy of th
e
operation and support documentation
. Successful completion o
f
this review results in the establishment of the Allocate
d
Baseline
.
PROJECT MANAGEMENT PLA
N
IRM-5231-19
A
(4)
Systems Integration Review (SIR) - a revie
w
performed during the development phase to determine if th
e
system is ready for acceptance testing
. Successful completio
n
results in the establishment of the
Product Baseline
.
(5)
Systems
Acceptance Review (SAR) -
a revie
w
performed at the conclusion of the development phase t
o
determine if the system functions properly, satisfies th
e
requirements, has complete and accurate documentation, and i
s
ready for implementation
. Successful completion results in th
e
establishment of the Operational Baseline
.
3
.1 .4
Trainin
g
This paragraph will provide a summary of the
training
require d
for the project team/office to become knowledgeable in thing
s
such as project management or system development techniques
.
3
.2
SCHEDUL
E
3 .2
.1
Level of Detai
l
The initial schedule should provide as much detail as possibl
e
for the Concepts Development Phase but may be general fo
r
subsequent phases
. The schedule for subsequent phases shoul
d
become more detailed with each update of the PMP
.
3
.2 .2
Scheduling Technique
s
Using the techniques described in figures 1-02 through 1-05, o
r
other
. appropriate techniques, schedule the tasks in paragrap
h
3
.1 above
.
a.
Organize the project tasks into logical and manageabl
e
jobs and assign target and projected start and end dates fo
r
each task and major milestone (i
.e
., develop a Work Breakdow
n
Structure per figure 1-02, a Gantt Chart per figure 1-05, or us
e
another appropriate technique)
.
b.
Determine and display the dependencies between projec
t
tasks as well as the estimated time required to accomplish th
e
tasks (i
.e
., develop an Activity Precedence Diagram per figur
e
1-03,
a
PERT Network per figure 1-04, or use another appropriat
e
technique)
.
c.
Develop a project team training schedule
.
d.
Assign responsibility for each project task (i
.e
.
,
develop a Responsibility/Task Matrix per figure 1-01 or us
e
another appropriate technique)
.
PROJECT MANAGEMENT PLA
N
IRM-5231-19
A
SECTION 4
.
RESOURCE REQUIREMENT
S
Estimate required resources (i
.e
., dollars and man-hours) pe
r
work package
.
4
.1
MANPOWE
R
This paragraph will provide
a summary of
target
and
projecte
d
manpower requirements (i
.e
., manhours) for the tasks an
d
schedule described in section 3
.
4
.2
FUNDIN
G
This paragraph will provide a summary of target and projecte
d
funding (i
.e
., required funds and allocated funds) for the task
s
and schedules described in section 3
.
SECTION 5
.
ACQUISITION STRATEG
Y
This section will contain an acquisition strategy that provide
s
a funding profile to support the project as well as a
n
assessment of the impact of attaining only a portion of the AIS
.
The Economic Analysis can provide supporting data
.
SECTION 6
.
SUPPORT PLAN
S
The following support plans will be added to the PMP a
s
appendixes
:
a
.
Configuration Management Plan
(CM Plan)
(IRM-5231-09
)
b
.
Quality Assurance Plan
(QA
Plan)
(IRM-5231-10
)
c
.
Test Plan
(TP)
(IRM-5231-14
)
d
.
Telecommunication Support Plan
(TSP)
(IRM-5231-05
)
e
.
ADPE Support Plan
(ADP)
(IRM-5231-12
)
f
.
Implementation Plan
(IP)
(IRM-5231-16
)
g
.
Training Support Plan
(TRP)
(IRM-5231-15)
The CM and QA Plans shall be completed during the Concept
s
Development Phase and updated in subsequent phases
. Preliminar
y
versions of the remaining support plans will be prepared durin
g
the Concepts Development Phase with the formal versions bein
g
completed during the design phase
. These plans will be update
d
as
appropriate
.
PROJECT MANAGEMENT PLA
N
IRM-5231-19
A
APPENDIX
D
ACRONYMS AND ABBREVIATION
S
ADP - ADPE Support Pla
n
AIS - Automated Information Syste
m
CDR - Critical Design Revie
w
CM - Configuration Managemen
t
CMP - Configuration Management Pla
n
COM - Computer Operators Manua
l
DBC - Data Base Conversion Pla
n
DBP - Data Base Pla
n
DD - Data Dictionar
y
DDS - Detail Design Specificatio
n
EA - Economic Analysi
s
FCA - Functional Configuration Audi
t
FRD - Functional Requirements Definitio
n
GDS - General Design Specificatio
n
IP - Implementation Pla
n
IRM - Information Resources Managemen
t
LCM - Life Cycle Managemen
t
MENS - Mission Elements Need Statemen
t
PCA - Physical Configuration Audi
t
PDR - Preliminary Design Revie
w
PGM - Program Manage
r
PIE - Post Implementation Evaluatio
n
PM - Project Manage
r
PMC - Project Manager Charte
r
PMP - Project Management Pla
n
PS - Programming Standar
d
QA - Quality Assuranc
e
QAP - Quality Assurance Pla
n
RS - Requirements Statemen
t
SAR - Systems Acceptance Revie
w
SAT - Systems Acceptance Tes
t
SDM - System Development Methodolog
y
SDP - System Decision Pape
r
SER - Systems Effectiveness Revie
w
SGC - Steering Group Committe
e
SIR - Systems Integration Revie
w
SIT - Systems Integration Tes
t
SRR - Systems Requirements Revie
w
TP - Test Pla
n
TRP - Training Support Pla
n
TSP - Telecommunications Support Pla
n
UM - Users Manual
COMMENTS/REVISION
S
Technical publications under the Information Resource
s
Management (IRM) Standards and Guidelines Program (MCO 5271
.1
)
are reviewed annually
. Your comments and/or recommendations ar
e
strongly encouraged
.
IRM Tech Pub Name
:
Project Management Plan
IRM-5231-19A
(Number)
Date of Tech Pub
:
COMMENTS/RECOMMENDATIONS
:
Name/Rank
:
(Optional
)
Unit
:
(Optional
)
Mail to
: Commandant of the Marine Corps (Code CCIS
)
Headquarters, United States Marine Corp
s
Washington, D
.C
.
20380-0001