EPLC_Project_Mgmt_Plan_v . .doc

<Project Name> Project Management Plan

Version: 1.0 Error! Unknown document property name.

Food and Drug Administration

<Project Name & Release Version #> Enterprise Performance Life Cycle Project Management Plan Document Version Number: <1.0> Document Version Date: <mm/dd/yyyy> Notes to the Author

[This document is a template of a Project Management Plan document for a project. The template includes instructions to the author, boilerplate text, and fields that should be replaced with the values specific to the project.

· Blue italicized text enclosed in square brackets ([text]) provides instructions to the document author, or describes the intent, assumptions and context for content included in this document.

· Blue italicized text enclosed in angle brackets (<text>) indicates a field that should be replaced with information specific to a particular project.

· Text and tables in black are provided as boilerplate examples of wording and formats that may be used or modified as appropriate to a specific project. These are offered only as suggestions to assist in developing project documents; they are not mandatory formats.

When using this template, the following steps are recommended:

1. Replace all text enclosed in angle brackets (e.g., <Project Name>) with the correct field document values. These angle brackets appear in both the body of the document and in headers and footers. To customize fields in Microsoft Word (which display a gray background when selected) select File->Properties->Summary and fill in the appropriate fields within the Summary and Custom tabs.

After clicking OK to close the dialog box, update all fields throughout the document selecting Edit>Select All (or Ctrl-A) and pressing F9. Or you can update each field individually by clicking on it and pressing F9.

These actions must be done separately for any fields contained with the document’s Header and Footer.

2. Modify boilerplate text as appropriate for the specific project.

3. To add any new sections to the document, ensure that the appropriate header and body text styles are maintained. Styles used for the Section Headings are Heading 1, Heading 2 and Heading 3. Style used for boilerplate text is Body Text.

4. To update the Table of Contents, right-click on it and select “Update field” and choose the option - “Update entire table”.

5. Before submission of the first draft of this document, delete this instruction section “Notes to the Author” and all instructions to the author throughout the entire document.

VERSION HISTORY

[Provide information on how the development and distribution of the Project Management Plan will be controlled and tracked. Use the table below to provide the version number, the author implementing the version, the date of the version, the name of the person approving the version, the date that particular version was approved, and a brief description of the reason for creating the revised version.]

By Revision

Date Approved

By Approval

Date Description of and

Reason for

Change

Table of Contents 41.0 Introduction

41.1 Purpose of Project Management Plan

41.2 Project Characterization

42.0 Executive Summary of Project Charter

43.0 Assumptions/Constraints

44.0 Scope Management

44.1 Work Breakdown Structure

54.2 Deployment Plan

54.3 Change Control Management

55.0 Schedule/Time Management

55.1 Milestones

56.0 Cost/Budget Management

67.0 Quality Management

68.0 Staffing Management

68.1 Project Team Training

69.0 Communications Management

69.1 Communication Matrix

610.0 Risk Management

710.1 Risk Log

711.0 Configuration Management Plan

712.0 Independent Verification and Validation Plan (IV&V)

713.0 Requirements Management Plan

714.0 Records Management Plan

715.0 Acquisition Strategy

716.0 Compliance-Related Planning

817.0 Security Approach

9APPENDIX A: Project Management Plan Approval

10APPENDIX B: REFERENCES

11APPENDIX C: KEY TERMS

1.0 Introduction

1.1 Purpose of Project Management Plan

[Provide the purpose of the Project Management Plan (PMP)]

The intended audience of the <Project Name> PMP is all project stakeholders including the project sponsor, senior leadership and the project team.

1.2 Project Characterization

[Characterize the project by identifying the following key project attributes: FDA Strategic Goals, FDA Enterprise Architecture Business Segment(s), FDA Program(s), IT Investment (s), and IT Systems that are associated with this project. If needed, contact your EA representative for assistance with this section.]

FDA Strategic Goals: [Identify the specific FDA strategic goals to which this project aligns]

FDA Enterprise Architecture Segment: [Identify the FDA Segment Enterprise Architecture that this Project supports]

FDA Programs: [Identify the program(s) that this project impacts] FDA IT Investments: [Identify the specific investment(s) in the FDA Portfolio Management Tool that are funding this project] FDA IT Systems: [Identify any IT systems that will be impacted by this project]

2.0 Executive Summary of Project Charter

[Provide an executive summary of the approved project charter. Provide a reference to the approved Project Charter. Elaborate on any sections within the Project Charter that need further detail contained within the PMP.]

3.0 Assumptions/Constraints

[This section of the Project Management Plan describes the assumptions on which the project is based and the constraints on project factors such as the schedule, budget, resources, software to be reused, acquired software to be incorporated, technology to be employed, and product interfaces to other products.]

4.0 Scope Management

[This section of the Project Management Plan describes the project scope in terms of organizations, business functions and the architecture (business systems and technology) involved in or impacted by the project, and what is not included within the scope of the project.]

4.1 Work Breakdown Structure

[This subsection of the Project Management Plan specifies the various work activities to be performed in the project. A work breakdown structure should be used to depict the work activities and the relationships among work activities. Work activities should be decomposed to a level that exposes all project risk factors and allows accurate estimate of resource requirements and schedule duration for each work activity. Work packages should be used to specify, for each work activity, factors such as the necessary resources, estimated duration, work products to be produced, acceptance criteria for the work products, and predecessor and successor work activities. The level of decomposition for different work activities in the work breakdown structure may be different depending on factors such as the quality of the requirements, familiarity of the work, and the technology to be used. Insert the project’s work breakdown structure or provide a reference to where it is stored. An EPLC WBS Template and Template Style documents are available in the EPLC eRoom.]

4.2 Deployment Plan

[This section should discuss the approach for rolling out the application to the end users. Include information on topics such as; phased deployment versus immediate full deployment, conducting environment assessments, developing memorandums of understandings, hardware/software installation, data conversion, and.]

4.3 Change Control Management

[An EPLC Change Management Plan Template is available in the EPLC eRoom to assist in filling out this section.]

5.0 Schedule/Time Management

[Example of schedule management approach: Establish a baseline within the first two weeks of the project and monitor progress against the baseline on a weekly basis. The Project Manager will be responsible for ensuring the project schedule is updated with the latest information. For variances greater than 10%, the project may be required to formally re-baseline per CPIC and/or EVM requirements.]

5.1 Milestones

The table below lists the milestones for this project, along with their estimated completion timeframe.

[Add additional rows as necessary]

6.0 Cost/Budget Management

[This section should specify the control mechanisms to be used to measure the cost of work completed, compare planned cost to budgeted cost, and implement corrective action when actual cost does not conform to budgeted cost. The intervals at which cost reporting will be done and the methods and tools that will be used to manage the budget should be in this section. A mechanism such as earned value tracking should be used to report the budget and schedule plan, schedule progress, and the cost of work completed.]

7.0 Quality Management

[This section of the Project Management Plan specifies the mechanisms to be used to measure and control the quality of the work processes and the resulting work products/deliverables. An EPLC Quality Management Plan Template is available in the EPLC eRoom to assist in filling out this section.]

8.0 Staffing Management

[This section of the Project Management Plan specifies the number of staff required by skill level, the project phases in which the numbers of personnel and types of skills are needed, and the duration of need. In addition, this subsection should specify the sources of staff personnel; for example by internal transfer, new hire, or contracted. Resource Gantt charts, resource histograms, spreadsheets, and tables may be used to depict the staffing plan by skill level, by project phase, and by aggregations of skill levels and project phases. An EPLC Staffing Management Template is available in the EPLC eRoom to assist in filling out this section. ]

8.1 Project Team Training

[This subsection of the Project Management Plan specifies the training needed to ensure that necessary skill levels in sufficient numbers are available to successfully conduct the project. The training schedule should include the types of training to be provided, numbers of personnel to be trained, entry and exit criteria for training, and the training method; for example, lectures, consultations, mentoring, or computer-assisted training. The training should include both technical and managerial skills.]

9.0 Communications Management

[This section should define all of the project’s stakeholders and the communication mechanisms that will be used to keep them informed.. An EPLC Communications Management Template is available in the EPLC eRoom to assist in filling out this section.]

9.1 Communication Matrix

10.0 Risk Management

[This section of the Project Management Plan should define the methods and techniques used to successfully identify and manage the project risks. Insert the project’s risk management plan or provide a reference to where it is stored. An EPLC Risk Management Template is available in the EPLC eRoom to assist in filling out this section.]

10.1 RISK Log

[A Project Risk Log should be maintained as a separate, working document that is constantly updated as new risks surface. It is recommended that the project’s Risk Log be reviewed at each project’s status meetings. . Provide a reference to where it is stored. An EPLC Risk Management Log template is available in the EPLC eRoom to assist in filling out this section .]

11.0 Configuration Management Plan

[This section of the Project Management Plan refers to the configuration management process and should define the practices and configuration management tools used to implement these practices. An EPLC Configuration Management Template is available in the EPLC eRoom to assist in filling out this section.]

12.0 Independent Verification and Validation Plan (IV&V)

[This section of the Project Management Plan refers to the project’s independent verification and validation plan. An EPLC IV&V Plan Template is available in the EPLC eRoom to assist in filling out this section.]

13.0 Requirements Management Plan

[The Requirements Management plan is used to document the necessary information required to effectively track and manage project requirements from definition, through traceability, to delivery. An EPLC Requirements Plan Template is available in the EPLC eRoom to assist in filling out this section .]

14.0 Records Management Plan

[The Records Management Plan is used to track and manage the process to identify, classify, archive, and destroy records.]

15.0 Acquisition Strategy

[The creation of the Acquisition Plan is the first of several that are needed to request a contract for goods or services. The information contained within the Acquisition Plan will vary depending upon the type of goods or services to be procured. If the section does not apply to the project, insert “Not Applicable” under the heading. An EPLC Acquisition Strategy Template is available in the EPLC eRoom to assist in filling out this section.]

16.0 Compliance-Related Planning

[Insert a list of compliance related processes the project must adhere to and how the project will track adherence. Compliance related processes may include:

· Capital Planning and Investment Control (CPIC)

· Security (including the C&A process)

· Enterprise Architecture

· Section 508 Compliance

· Records Management

· Privacy Impact Assessment (PIA)

17.0 Security Approach

[This section of the Project Management Plan specifies how the project team will ensure that proper security compliance is addressed for the project .Items to address should include whether a new or separate C&A will be required for the project . An EPLC Security Approach Template is available in the EPLC eRoom to assist in filling out this section.]

APPENDIX A: Project Management Plan Approval The undersigned acknowledge that they have reviewed the <Project Name> Project Management Plan and agree with the information presented within this document. Changes to this Project Management Plan will be coordinated with, and approved by, the undersigned, or their designated representatives.

Signature:

Date:

Print Name:

Title:

APPENDIX B: REFERENCES

[Insert the name, version number, description, and physical location of any documents referenced in this document. Add rows to the table as necessary.]

The following table summarizes the documents referenced in this document.

APPENDIX C: KEY TERMS

The following table provides definitions and explanations for terms and acronyms relevant to the content presented within this document.

Template Version 2.1 (Last Modified on Aug. 7, 2009)

PAGE

Revision Date: Error! Unknown document property name.

EPLC_Project_Management_Plan_Template.doc