SYSTEM LIFE CYCLE MANAGEMENT GUIDANCE: PRACTICE PAPER PROJECT MANAGEMENT PLAN pptx

The Project Management Plan serves several important purposes in support of the system life cycle: considered and that key decisions are clearly documented; and individuals involved in

1

2

TABLE OF CONTENTS

2.3 Project Team Organization .e« «se 6 1 6 1 6 6 66111 °°

2.4 Project Budget ® Ằœ® eœ@Ằœ9% 9 9 6 9 6 6Ó @ 6 6Ó 6 @ 6Ó 6 9 6e 9 9 9 se 6 6ð 6e e@ €đ 6 6e 6

2.6 Applicable ProjeCt ApPFrOVAIS .‹ «sec 6 { 1 1 1 1 1 1 1 1 1 Ÿc 2.7 Benefit-Cost AnalySiS «« « e c6 6 6 6Ÿ S1 6 6 6 6 66661 °°

2.10 Procurement Approach «.e «se s c6 6 1 6 6 6 6 66 61 V6 66 6 n6

2.11 Configuration Management Plan .«e «sec {1 1 1 1 1 {6+

2,12 Documentation Standards .e sec 6 6 1 6 1S 6 1 1 6 11 1 6S

2.13 Security Approach cu «se 6 6 c6 6 6 6 6 602 6 6 606 6 66 6 116 6 666

2.14 ConverSion Approach ‹.« se sec c6 6 1 6 6 66 61 6 66 16666256

2.16 User Support Approach ĐA 0ê 66666 06662 06 6 06626 06s ©ee° se“

Development and Update of the Project Management

Plan ®e e ee099052926e09e20ee.eee9e0e629066eeseo9oeeeoeeecoeeeeeceeoeoeoedoseeeeeoeeoeoeoeoeesee

TABLE OF CONTENTS (Continued)

Page

EXHIBITS

System Life Cycle eeeoeevaevoeveeeoseeeveeuveeeseeevnevnseeseeeaes ae eae ed 20

Plan Topics eeeeeoeevoeeeeoeoev@aeseeseeeeveeeveevseeeoeveseeevesneve eee e enone 24

‘ Plan Topics eeuseeceveeeevesveeveeeneeveeeveevneeveseevneveeeveve ee eee eeananane ee 25

OSWER DIRECTIVE #2025.002

1 PRACTICE PAPER PURPOSE

life cycle

OSWER places great emphasis on the Project Management Plan

especially projects for systems that support more than a handful

the approach to the project are carefully considered and the

completing the project

The topics addressed in this practice paper include:

Plan;

Management Plan;

life cycle; and

to each other and to the other products of the system life

cycle

The Project Management Plan serves several important purposes

in support of the system life cycle:

considered and that key decisions are clearly documented;

and individuals involved in a system project, by providing

a single known source of information regarding the project

approach and the role of each organization/individual; and

o Provides a basis for measuring progress through the system

life cycle, and the potential impact of any changes to the

approach for conducting the project

OSWER DIRECTIvE #6

included in other formal system documentation '

2 STRUCTURE AND CONTENTS OF PROJECT MANAGEMENT PLAN

is discussed should be tailored to the individual project

Management Plan

2.1 Project Charter/Objectives

describing the objectives of the project and certain other key

Initiation Decision Paper:

o The information management problem to be solved,

o The scope of the problem in terms of OSWER programs and

organizations,

programmatic sponsor for the project

Parts 1 and 2 of this Guidance describe a specific sequence

2

Pere pp em ever a pte eos

EXHIBIT 2-1: OUTLINE OF PROJECT MANAGEMENT PLAN

TOPICS

Project Charter/Objectives

Life Cycle Adjustment

Project Team Organization Project Budget

Project Reviews/Quality Assurance

Applicable Project Approvals

Benefit-Cost Analysis

Methodologies and Tools Workplan

Procurement Approach Configuration Management Plan Documentation Standards

Security Approach Conversion Approach

Installation Approach

User Support Approach Maintenance Approach

the life cycle, such as by combining certain stages, or by

described in Parts 1 and 2 of this Guidance, and the reasons for

should be included in this section are:

© The consolidation of portions of two or more stages,

Development stage) during the Design stage,

different life cycle schedules for one or more modules,

portions of the system,

system,

including consolidation of System Decision Papers, and

2.3 Project Team Organization

This section describes how the project team will be organized in terms of the specific organizations and individuals

section of the Plan as a stand-alone document, distributing it to

individuals to improve project coordination

applicable techniques, and includes:

home organization, and any assignment of this individual

office) to accomplish his/her role as project manager;

OSWER DIRECTIVE #Söẽ

Identification of any supporting organization structures

systems affecting a designated program;

Shade

Specific contractor organizations should be identified |

assigned to the project, and key contractor personnel

person-by-person basis or, for very large projects, by

should be clearly identified

identification of any sub-teams (if applicable) and size and team leaders for each team;

multiple stewards if appropriate, for different types of data;

on the project team, but which will be informed of major

required system decision papers and other materials as

organizations,

National Data Processing Division - NCC and WIC,

organizations, and

o Identification of the members of the Change Control

that are expected to change throughout the life cycle

Paper entitled ‘Project Participation and Coordination’ provides

The level of commitment of Agency staff to the project, and their

Project Manager and each participant's supervisor

services)

he®

"› =

OSWER places particular emphasis on effective monitoring

each funding source

for the project (i.e., Threshold Analysis)

who should conduct them (i.e., Threshold Analysis), are described

Approvals'.)

Specific information contained in this section includes:

For a Level I system, also designates the criteria that result in the Level I classification;

structured to reflect any adjustments to the system life cycle

individuals who will participate in each review;

project team;

results of reviews; and

OSWER DIRECTIVE

programmatic and technical findings and recommendations

and presentations, circulation of life cycle products to

validation and verification (IV&V), acceptance testing)

each phase of the life cycle

technique for determining the approval authority (i.e., Threshold

this section includes:

criteria that result in the Level I classification;

o Identification of the specific approvals to be obtained

structured to reflect any adjustments to the system life

cycle

appropriate) to the approval authority;

document the results of each requested approval;

System Life Cycle Management Guidance;

ee e.Cos

2.7 Benefit-Cost Analysis

Decision Paper as an initial rough estimate of project scale, and

Concept phase and is contained in the System Concept document

this section includes:

applicable;

measures of improvement if possible),

o System costs:

Implementation stage),

Total system life cycle costs;

identified assumptions

Of particular note, the costs documented in this section of

Analysis for project reviews and approvals

Each phase and stage of the life cycle should be conducted using

products (per the outlines contained in Part 2 of this Guidance)

Plan include:

requirements analysis (e.g., system prototyping),

structured analysis, application generators),

analysis),

III),

o File management and configuration management software tools (e.g., TIP Repository),

° Project management tools (e.g., TELLAPLAN, SUPERPROJECT)

individual selections of methodologies and tools includes:

o Training/other special support required, and

10

mie erent ee, ot DEWER Diricoiive Fist

preceding phase/stage

workplan describes the specific tasks for conducting the project,

very large, complex, or on a very tight schedule, the workplan is particularly important it identifies the ‘critical path' of

clearly allocate the resources provided in the Project Budget

the following information for each phase/stage:

appropriate;

activities/tasks to products;

reviews and approvals *;

activity/task *;

‘life cycle product *;

activities/tasks for other phases or stages *; and

into modules or work packages, it will be helpful to prepare a high level workplan integrating the project

each module *

OSWEP DIRECT:VE #9028.GDa

perform status reporting

2.10 Procurement Approach

This section summarizes the means to be used to acquire all

installed at needed locations, and to obtain support from other

needed

contracts:

software, communications or service),

other Agency offices:

Contract identification, Planned acquisition date, and

12

o Resources to be acquired through new procurements:

multiple projects/systems),

award),

tion(s) providing procurement assistance, and

Management Plan;

Administration):

Organization identification,

Planned start date for support,

agreement

for formal notification of upcoming procurement actions

tools used to identify, monitor and control the configuration of

và

Configuration Management Plan describes in detail how the project

contained in this section includes:

represented and individual members, and authority of the Board

° System baselines (identification/index of configuration items),

o Software control procedures

can be maintained as a stand-alone document that is referenced in the Project Management Plan

practice of configuration management, and explains in more detail the content of the Configuration Management Plan

2.12 Documentation Standards

documentation

adopted from other organizations, such as the Federal Information

as a model for the current project

2.13 Security Approach

requirements and security features of the system It is included

in the Project Management Plan to provide an overview of security

14

OSWER DIRECTIVE #&

this section at a summary level includes:

confidential or sensitive information,

applicable),

o Data base security measures,

outputs), and

2.14 Conversion Approach

and review the Project Workplan and other sections of the Project

at a summary level includes:

systems;

be converted:

-~ Source and location of data,

Anticipated data quality problems,

C23.00 6

sees Cn memes

Tố

procedures and software

2.15 Installation Approach

included in the Project Management Plan to provide an overview of

summary level includes:

be separately installed items;

location;

each location:

Installation date, Special conditions (if any),

installation, and

support the installation;

data bases synchronization for system modules/components installed at multiple locations

2.16 User Support Approach

in the Project Management Plan to provide an overview of the user

16

O8WER DEGTHME 85085.02A

Specific information presented in this section at a summary level

includes:

and ongoing user support;

and for each session:

retrieval, system administration, etc.),

one-on-one training), and

training;

o Identification of other training activities/materials,

such as tutorials, computer-based training, etc

Approach needed to prepare and review the Project Workplan and

information presented in this section includes:

performing software maintenance for each system module;

o Identification of organizations responsible for

any customized portions of the package;

maintaining each interface with other automated systems

maintenance and enhancements) at each location where the

system is installed; and

installation schedule for each release

be specifically referenced by the Maintenance Plan

2.18 Operations Approach

organizations with system operations responsibilities are clearly

information presented in this section includes:

update, and reporting for each module of the system;

where the system is installed;

maintenance of data tables) for each facility where the system is installed; and

administration functions

regarding system operations: details of operating procedures are

Me®

18

documented in the Operation Manual and User Manual Organiza-

referenced by the Operations Plan

3 DEVELOPMENT AND UPDATE OF THE PROJECT MANAGEMENT PLAN

Management Plan

Project Management Pian_and for keeping it current—throughout the

other individuals as appropriate

separate binder

Life Cycle

system life cycle, including a subset of topics at the end of the

of the Project Management Plan through the system life cycle

At the end of the Initiation phase, the plan should contain

the Project Management Plan contains some basic information about

Plan are:

pertinent programmatic mission, and a preliminary view

OSWER DI2EC FiVE 2025.022 EXHIBIT 3-1: EVOLUTION OF PROJECT MANAGEMENT PLAN

Life Cycle Adjustment

Project Team Organization

Project Budget

Project Reviews/Quality Assurance

Applicable Project Approvals

deVeer le oe

section also identifies the project sponsor

Life Cycle Adjustment - Includes any adjustments to the

performed during the Definition stage might be included in.the Concept phase

the intended use of contractor support

to conduct the Concept phase, and includes a preliminary order of magnitude preliminary estimate of the aggregate

stage (e.g., whether the aggregate cost should be viewed

millions of dollars, and commensurate EPA workyears)

preliminary threshold level for the project based on the

‘threshold analysis' should be conducted is described in

project and a scheduled dates for completion of the Initiation phase and Concept phase reviews

about the problem, identifies the approval authority (in terms of specific organization(s) and individual(s)) for -the Initiation and Concept phases of the project

statement of the expected benefits and the organizations

benefits is not essential in the Initiation phase

Concept phase

Concept stage, noting for each task who will perform the

OSWER DIREDCTiVE #8028.02a

the Concept stage

The Concept phase adds considerable new information to the Project Management Plan, introducing most of the remaining topics

through the remainder of the system life cycle

Plan is updated and refined as necessary, based on the results of

Project Management Plan, with the Workplan and Project Budget the

significantly change any part of the Project Management Plan, the

purposes and to support the post-implementation evaluation of the system

provide the information requested by the OIG much more easily and ensure that the information provided is accurate

of the Project Management Plan history is retained, a copy of the

22