PROJECT PLAN SUMMARY
<PROJECT NAME>
<AGENCY NAME>
<Date>
<PROJECT NAME> Project Plan Summary
CONTACTS
Agency Project Manager:
Agency Project Sponsor:
Phone:
Phone:
Email:
Email:
[NOTE TO THE AUTHOR]
This template is provided as a basic guide based on best practices and may be revised as needed for the project.
The template includes instructions to the author 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.
Red text enclosed in angle brackets <text> indicates a field that should be replaced with information specific to a particular project.
When using this template, it is recommended that you follow these steps:

Replace all text enclosed in angle brackets (e.g., <Project Name>) with the correct values.

To add any new sections to the document, ensure that the appropriate header, body text styles, and section numbering schemes
are maintained.

To update the Table of Contents, right-click and select “Update field” and choose the option- “Update entire table”

Before submission of the first draft of this document, delete this “Notes to the Author” page and all instructions to the author, which
appear throughout the document as blue italicized text enclosed in square brackets.]
This template provides an overview of the standard content regarded as best practice for most projects. This template is provided as an
example, and is not required for any project.
Many of the sections included may not be required or necessary for smaller projects. Project Managers should consult their governance
authorities and Risk & Complexity Category to determine what deliverables are required for the project. If an agency elects to use this
template, it may be tailored, customized, and detailed to meet the needs and complexity of the project.
Although the template is presented here as a single document, any, or all, of these planning sections can be created as a separate
document(s) or artifact.
Additional templates are referenced in this document. The use of these templates is also not required, but the templates are provided
for the agency to use or amend if desired.
<AGENCY NAME>
Page 1 of 8
<PROJECT NAME> Project Plan Summary
SIGNATURE AND ACCEPTANCE PAGE
[Please include signatories that are appropriate for your project. At a minimum, this will include the Project Sponsor
and the Project Manager. It may also include, but is not limited to, the Business Analyst, Technical Lead, lead subject
matter experts, other team members, and stakeholders.]
I have reviewed this Project Management Plan (PMP) and agree that the content of the document is accurate
and clearly describes the project management methodology for the project.
Date:
Signature:
Print Name:
Title:
Agency:
Role:
Signature:
Project Sponsor
Date:
Print Name:
Title:
Agency:
Role:
Signature:
Date:
Print Name:
Title:
Agency:
Role:
Signature:
Date:
Print Name:
Title:
Agency:
Role:
Signature:
Date:
Print Name:
Title:
Agency:
Role:
<AGENCY NAME>
Page 2 of 8
<PROJECT NAME> Project Plan Summary
TABLE OF CONTENTS
SIGNATURE AND ACCEPTANCE PAGE ........................................................................................................................... 2
1.0
EXECUTIVE SUMMARY ...................................................................................................................................... 4
2.0
PROJECT SCOPE................................................................................................................................................. 4
3.0
PROJECT ORGANIZATIONAL & GOVERNANCE STRUCTURE .............................................................................. 4
4.0
RESOURCES ....................................................................................................................................................... 4
4.1
Human Resources ......................................................................................................................................... 5
4.2
Equipment/Materials Resources .................................................................................................................. 5
5.0
PROJECT SCHEDULE MANAGEMENT ................................................................................................................ 5
5.1
Project Schedule ........................................................................................................................................... 5
5.2
Schedule Maintenance ................................................................................................................................. 5
6.0
COST MANAGEMENT ........................................................................................................................................ 5
6.1
Budget ........................................................................................................................................................... 5
6.2
Project Spending Plan ................................................................................................................................... 6
7.0
PROCUREMENT MANAGEMENT ....................................................................................................................... 6
8.0
COMMUNICATIONS MANAGEMENT ................................................................................................................ 6
9.0
CHANGE MANAGEMENT................................................................................................................................... 6
10.0
ORGANIZATIONAL CHANGE MANAGEMENT .................................................................................................... 7
11.0
QUALITY MANAGEMENT .................................................................................................................................. 7
12.0
DELIVERABLE ACCEPTANCE .............................................................................................................................. 7
13.0
RISK MANAGEMENT ......................................................................................................................................... 7
13.1
Risk & Complexity Assessment ..................................................................................................................... 7
13.2
Project Risk Management ............................................................................................................................. 7
14.0
ISSUE MANAGEMENT ....................................................................................................................................... 8
15.0
SYSTEM SECURITY ............................................................................................................................................. 8
<AGENCY NAME>
Page 3 of 8
<PROJECT NAME> Project Plan Summary
1.0
EXECUTIVE SUMMARY
2.0
PROJECT SCOPE
[The description of the work to be performed to deliver a product/products, service(s), and result(s) with specified
features and functions. Include the following information:
3.0

Project Summary - Provide a summary description of the project.

In Scope - Provide a summary of the scope of the project and discuss how the project scope and objectives trace
back through the Project Charter to initial project documents such as the Schedule IV-B, LRPP, etc.).

Out of Scope - Provide a summary of what is excluded from the project.

Project Objectives - Provide the project objectives.

Critical Success Factors – Provide a summary of Critical success factors that are vital for the project to be successful.

Assumptions and Constraints - Provide a summary of the project assumptions and constraints.

Interdependencies - Identify production systems, other projects or initiatives that may impact or be impacted by
the project.

Milestones and Deliverables - Provide an initial list of milestones and deliverables for the project. Include specific
completion dates if known.]
PROJECT ORGANIZATIONAL & GOVERNANCE STRUCTURE
[The project governance management structure is a representation of the project from an organizational perspective.
For issues that are beyond the control of the project manager or team, the Project Steering Committee and Executive
Leadership serve as part of an escalation path.
Provide a high-level description or organizational chart with governance structures identified. Provide a summary of
the project governance and escalation process.] Milestone List and Deliverable List templates are available in the AST
Template Library.]
4.0
RESOURCES
<AGENCY NAME>
Page 4 of 8
<PROJECT NAME> Project Plan Summary
4.1
Human Resources
[The human resource plan establishes the project team and describes the roles and responsibilities of the
project team members. As the project evolves, more resources will be added to the project team and more
details of those resources will be available and necessary for resource management. Use tools such as a team
roster and / or a RACI (Responsible, Accountable, Consulted, and Informed) Chart to manage human
resources.
Provide an overview of the human resources needed, the skills needed, the responsibilities, the time required.
Human Resource Plan and RACI Chart templates are available in the AST Template Library.]
4.2
Equipment/Materials Resources
[Identify types of equipment, software or other materials, and the purpose and quantities required.]
5.0
PROJECT SCHEDULE MANAGEMENT
5.1
Project Schedule
[In this section, include a summary of the schedule containing project start and finish dates as well as dates
for significant project phases or milestones in this document. Reference the location where the Project
Schedule may be obtained. Sample schedule templates and a Schedule Best Practices Checklist may be
obtained from the AST Template Library.]
5.2
Schedule Maintenance
[Provide a summary of the responsibility and process for updating the schedule with data (to estimate effort,
duration and cost for future work and to record actual values for completed work) and the process for
baselining and re-baselining the schedule. Schedule management activities are subject to the governance
and escalation process and the change control processes.]
6.0
COST MANAGEMENT
6.1
Budget
[Project budgeting determines the estimated costs associated with defined project activities. Budgeting is
done in parallel with the project schedule development. The budget is highly dependent on both the
estimated length of tasks and the resources assigned to the project.
Provide a Project Budget that includes, but is not limited to:


Total cost for the project by major expense category (Contract Services, Expense, Other Capital Outlay,
etc.]
Projected of Costs by fiscal year (FY) over the life of the project. (Current fiscal year costs should be
accurate and match the Project’s Spending Plan for the fiscal year; future fiscal year costs may be
projections.)
<AGENCY NAME>
Page 5 of 8
<PROJECT NAME> Project Plan Summary


6.2
A discussion of current and future appropriations required for the completion of the project and any
special procedures or processes necessary.
Identification of the funding source(s) for the project (e.g., General Revenue, Trust Fund, grant).]
Project Spending Plan
[Provide a summary of the responsibility and process for developing and maintaining documentation of
monthly projected and actual budget for the Fiscal Year. This information will be required as part of the
Project Status Report. A Spending Plan template is available in the AST Template Library.]
7.0
PROCUREMENT MANAGEMENT
[The Procurement Management Plan ensures that contracts or other procurement documentation accurately reflects
the approved project scope. The Procurement Plan identifies any project needs that can be met by purchasing
products or services. Provide a summary of the following information:
 What to procure (and how much)
 When to procure
 How to procure
 Who will complete the procurement]
8.0
COMMUNICATIONS MANAGEMENT
[The Communication Plan ensures that the all project constituents (the project team, stakeholders and customers) are
kept informed of project status on a timely basis. This plan will serve as a guide for communications throughout the
life of the project and will be updated as communication needs change.
Identify the key stakeholders (organizations and individuals) affected by and interacting with the project or the systems,
services or activities that are affected by the project. Provide a summary of communications needed for the project.
Provide an overview of the approach for storing all project documentation.
Stakeholder Roster, Communication Matrix, Communications Log, Decision Log, and Action Item Log templates are
available in the AST Template Library.]
9.0
CHANGE MANAGEMENT
[During the project lifecycle, changes are expected. Any change impacting scope, time, or cost initiates the change
control process.
Provide a summary of the project change control process to include roles / responsibilities, the process for identification
and submission of a change, the process of review and tracking the change and the process for approval of the change.
Describe the change control tracking process, including the maintenance of a project Change Control Register/Log. The
register/log is used to record project change requests and track change status as they progress through the review and
approval process. A Risk Log template is available in the AST Template Library.]
<AGENCY NAME>
Page 6 of 8
<PROJECT NAME> Project Plan Summary
10.0 ORGANIZATIONAL CHANGE MANAGEMENT
[The organizational change management plan is a framework for managing the effect of new business processes,
changes in organizational structure or cultural changes within an enterprise. Simply put, OCM addresses the people
side of change management. Provide a summary of the project organizational change management needs and
activities planned. Include such activities as organizational impact analysis, organizational assessment, stakeholder
and sponsor analysis, communications, and training.]
11.0 QUALITY MANAGEMENT
[Quality management planning determines quality policies and procedures relevant to the project for both project
deliverables and project processes, defines who is responsible for what, and documents compliance. The purpose of
the Quality Management Plan is to describe how quality will be managed throughout the lifecycle of the project.
Provide an overview of the projects quality management activities and documentation.]
12.0 DELIVERABLE ACCEPTANCE
[The purpose of the Deliverable Acceptance Plan is to facilitate the timely review of project deliverables and ensure
deliverables are tracked and recorded. Provide an overview of the roles and responsibilities for deliverable review,
acceptance criteria for project deliverables, and how deliverables will be approved or denied and by whom.]
13.0 RISK MANAGEMENT
13.1 Risk & Complexity Assessment
[Provide the Initiation R&C Category in this section. Update the category score as you move through the
project.]
Risk & Complexity Assessments
Pre-Charter Risk & Complexity Category
Initiation Gate Risk & Complexity Category
Planning Gate Risk & Complexity Category
Event Driven Risk & Complexity Category
Category
[If applicable, provide the reason(s) for a change in the R&C Category between assessments.]
13.2 Project Risk Management
[Provide a summary of the process for managing risks to include risk identification, risk analysis,
prioritization or level of importance, and mitigation strategies or risk response. Identify and document the
process to be used for tracking, periodic review, and update of Risks. A Risk Log template is available in the
AST Template Library.]
<AGENCY NAME>
Page 7 of 8
<PROJECT NAME> Project Plan Summary
14.0 ISSUE MANAGEMENT
[An issue is an immediate problem that needs resolution. Acknowledging and addressing issues quickly ensures that
they do not impact the scope of the project. Provide a summary of the approach for the identification, analysis, and
management of project issues. Issue management consists of (1) Issue identification, (2) Issue analysis, and (3) ongoing
Issue management. Issue management is performed continually over the life of the project.]
15.0 SYSTEM SECURITY
[See Rule 71A-1, F.A.C., for a description of the requirements for the System Security Plan.]
<AGENCY NAME>
Page 8 of 8