Get documents about "Integrated Project Management Templates
Description
Integrated Project Management Templates document sample
Document Sample
DEPARTMENT OF HUMAN SERVICES
<See Instructions: Enter DHS Cluster and/or Unit-Office Name>
<Project Name> Project Integrated Project Plan Low
Complexity Document
Title <briefly identify proposed project – if necessary, add a short subtitle of no
more than 1 or 2 lines>
From: <unit, team, group, etc>
To: <ITGC?, Exec Staff?, DHS Cabinet?>
File Name: <file name>
Date First Created: <mm/dd/yyyy>
Date Last Updated: <mm/dd/yyyy this date is very
important because there may be
multiple versions as new data is
analyzed>
Author: <name or group>
D:\Docstoc\Working\pdf\78a553cb-03c8-4566-a134-4896c77723cd.doc
Created on: 4/14/2011
<Project Title or Acronym> Integrated Project Plan
Purpose of the Document
Planning
Determine work Determine work
activities, resources, controls to ensure
schedule, costs project performance
(Core work Plans) (Facilitating Plans)
Project Plan
Incorporate planning
outputs into one coherent
document
(Integrated Project Plan)
Executing
The Integrated Project Plan is used to guide both project execution and project
control. It is required to ensure that the various elements of the project are
properly coordinated. It is a document or collection of documents, which
communicate the project’s plan. The integrated plan should be expected to
change over time, as more information becomes available to the project.
The amount of planning performed should be commensurate with the scope of
the project and the usefulness of the information developed.
D:\Docstoc\Working\pdf\78a553cb-03c8-4566-a134-4896c77723cd.doc
Last printed 4/14/2011 5:25:00 PM
<Project Title or Acronym> Integrated Project Plan
Document Change Activity
The following is a record of the changes that have occurred on this document
from the time of its original approval
# Change Description Author Date
Template Instructions
The template instructions rely on the user to use the PM Guide
and current examples available on the PMO web site,
http://www.dhs.state.or.us/admin/ois/pmo/, or within the organization.
This template should be used on low complexity projects only. The
facilitating controls are much less formal. Low complexity project
plans are generally 4-5 pages in length and require the template user
to greatly simplify by editing non-applicable sections and/or to provide
brief “reality” statements to address the section. For example the
WBS may be a short to-do list of actions required and the user would
cut the WBS Dictionary.
Higher Complexity Project’s Integrated Project Plan may be quite
extensive and include many referenced facilitating plans. In this case
the Integrate Project Plan could be contained in a very large binder or
series of binders.
Insert information between left and right brackets - <>
Delete Brackets
Information in italics is additional template instructions or examples
Delete all italicized instructions
In file on the menu go to properties and in the summary folder enter
the document title and author (person or group)
D:\Docstoc\Working\pdf\78a553cb-03c8-4566-a134-4896c77723cd.doc
Last printed 4/14/2011 5:25:00 PM
<Project Title or Acronym> Integrated Project Plan
1 Problem/Opportunity .................................................................. 1
2 Scope Statement........................................................................ 1
2.1 Objectives ........................................................................... 1
2.2 Major Deliverable Milestones .............................................. 1
2.3 Assumptions ....................................................................... 2
2.4 Completion Criteria ............................................................. 2
3 Work Plan .................................................................................. 3
3.1 Lifecycle Model Selection .................................................... 3
3.2 Work Breakdown Structure (WBS) and Schedule ............... 3
3.3 Budget Projection ................................................................ 3
4 Facilitating Controls .................................................................... 3
4.1 Change Management Plan.................................................. 3
4.2 Quality Management Plan ................................................... 3
4.3 Risk Management Plan ....................................................... 4
4.4 Status Reporting ................................................................. 4
4.5 Project Document Standards, Approval, and Controls......... 4
4.6 Cost Management Plan ....................................................... 4
D:\Docstoc\Working\pdf\78a553cb-03c8-4566-a134-4896c77723cd.doc Page i
Last printed 4/14/2011 5:25:00 PM
<Project Title or Acronym> Integrated Project Plan
1 PROBLEM/OPPORTUNITY
Describe briefly the problem/opportunity to be solved - from the product
description.
2 SCOPE STATEMENT
The project scope includes all the work required, and only the work
required to successfully complete the project. The defined work will be an
integration of the work required to plan and manage the project with the
work to define, implement and support the customer’s request. The
following section’s objectives, milestones, assumptions and completion
criteria indicates what is in scope for this project:
2.1 Objectives
The following are the approved objectives from the product description.
1. Objective-1
3 to 7 objectives are usually sufficient – consider these very high-level
requirements.
2.2 Major Deliverable Milestones
This is the basis for a high-level plan. Planned complete dates may initially
be best guesses until more work has been defined as part of the project.
The following is an example for a maintenance project, using the system
maintenance methodology.
MS# Milestone Description Planned
Complete
MS1 Requirements documented, agreed and approved <Date>
Review request, meet with user to clarify, modify requirements
and obtain user approval.
MS2 High Level Analysis and Design Completed <Date>
Research and document high-level design changes and
additions. Review high-level analysis and design document
with sponsors; develop resources needed to perform remainder
of project.
D:\Docstoc\Working\pdf\78a553cb-03c8-4566-a134-4896c77723cd.doc Page 1
Last printed 4/14/2011 5:25:00 PM
<Project Title or Acronym> Integrated Project Plan
MS3 Detailed Analysis and Design Completed <Date>
Document system changes needed to meet user requirements,
document detailed specifications, review detailed design, revise
project plan and create an implementation plan.
MS4 Construction Completed <Date>
Create test scripts, complete coding, perform unit testing and
code review, and update system test plan.
MS5 Testing Completed <Date>
Perform system testing, integrated systems testing, and user
acceptance testing. Finalize implementation plan.
MS6 System or Application Implemented <Date>
Perform training, communicate changes, and execute
implementation plan. Perform post implementation activities,
file documentation and wrap–up loose ends.
2.3 Assumptions
Define any known planning assumptions.
2.4 Completion Criteria
Define what will indicate that the project has been completed and at what
point the ongoing work can and should be turned over to standard
operations and routine maintenance. For example:
All of the objectives and milestones have been satisfactorily met and
accepted by the business and steering committee or responsible
management.
The business has resolved or assigned responsibility for any open issues.
The ongoing maintenance and funding for maintenance has been
negotiated and agreed by the business and OIS.
Those responsible for maintaining the application or the changes to the
application have reviewed the documentation, code changes, and other
pertinent information.
All documentation has been filed in the standard PMO library structure and
is accessible to those who will maintain the application.
D:\Docstoc\Working\pdf\78a553cb-03c8-4566-a134-4896c77723cd.doc Page 2
Last printed 4/14/2011 5:25:00 PM
<Project Title or Acronym> Integrated Project Plan
3 WORK PLAN
3.1 Lifecycle Model Selection
Define the lifecycle model(s) that will be used for this project/phase and the
reasoning used in its selection.
3.2 Work Breakdown Structure (WBS) and Schedule
The work breakdown structure incorporates the milestone plan with the
management or coordination of the project. The System Maintenance
methodology – project control document is the basis for the major
milestones.
The WBS Dictionary is located in the appendix of this document due to the
page orientation and size.
3.3 Budget Projection
Indicate an approximate monthly spending plan of resource time for both
the business and technical staff in full time equivalents (FTE). Indicate an
approximate monthly spending plan in other project costs.
4 FACILITATING CONTROLS
4.1 Change Management Plan
All changes will be negotiated with the technical team lead, business and
appropriate DHS manager. Changes are likely to require a change in
completion date of the project or of a major milestone. The technical lead
will recommend whether to incorporate the changes or hold changes for a
future release.
4.2 Quality Management Plan
The Business and Technical Assessment indicated that this project was of
low complexity. The following quality management activities have been
recommended and approved for this project:
The project will follow the Standard System Maintenance Methodology.
The technical team will perform peer review of documentation and code.
D:\Docstoc\Working\pdf\78a553cb-03c8-4566-a134-4896c77723cd.doc Page 3
Last printed 4/14/2011 5:25:00 PM
<Project Title or Acronym> Integrated Project Plan
A formal test plan will be developed and executed with customer
acceptance approval.
4.3 Risk Management Plan
The project has determined the risks that are likely to occur and have a
high impact to the success and timing of the project. The following is a list
of the risks and the plan for how the project plans to mitigate each risk:
Note in many cases is the risk is likely to occur and have a high impacted it
should be listed here with the mitigation being a direct change to increase
time, funding, or whatever to accommodate the risk. For example, if the
risk is lack of skilled resources – then the mitigation might be an increase in
scheduled completion, or the adding of a person to mentor.
4.4 Status Reporting
The project manager will deliver status reporting to the steering committee
and sponsor formally on a monthly basis during regularly scheduled
meetings. Informal status will be given weekly at the regularly scheduled
team meetings.
4.5 Project Document Standards, Approval, and Controls
All internal work products being drafted or revised will be located in a
shared electronic project directory using the PMO Standard directory
structure. The directory is located on XXXXXXXXXXX.
4.6 Cost Management Plan
Briefly describe how the project will track time and any other expenditure.
Your team may have a specified method, i.e. using core, or some other
time tracking mechanism.
D:\Docstoc\Working\pdf\78a553cb-03c8-4566-a134-4896c77723cd.doc Page 4
Last printed 4/14/2011 5:25:00 PM
<Project Title or Acronym> Integrated Project Plan
Del Name & # Dur. Critically Skill
# WBS Dictionary Est. Depend
N/A
1. Phase Initiate – Obtaining agreement on the business requirement and charting the project.
N/A PM
Project Proposal Approved by
1.1.1.1. Milestone
N/A
2. Phase Plan – Creation and approval of the core work plan and facilitating plans that will guide
project execution and control.
N/A
2.1. Activity Develop the Project Plan – Integrating the results of the other planning activities
into a coherent document to guide the project execution and control.
N/A 0 PM
Plan
2.1.1.1. Milestone and Schedule Approved by
N/A
3. Phase Execute – Definition of the required work activities to define, construct, pilot, and
implement the product scope or selected system functions.
N/A
3.1. Activity Requirements Definition
3.1.1. Task Review Request
3.1.2. Task Meet with users to clarify request
3.1.3. Task Modify request requirements
3.1.4. Task Obtain user approval of requirements
N/A 0
Requirements documented, agreed and approved
3.1.4.1. Milestone
N/A
3.2. Activity High Level Analysis & Design
D:\Docstoc\Working\pdf\78a553cb-03c8-4566-a134-4896c77723cd.doc Page 5
Last printed 4/14/2011 5:25:00 PM
<Project Title or Acronym> Integrated Project Plan
Del Name & # Dur. Critically Skill
# WBS Dictionary Est. Depend
3.2.1. Task Research and Documentation
3.2.2. Task Review High Level Analysis and Design document with Sponsors
3.2.3. Task Resource needs
N/A 0
High
3.2.3.1. Milestone Level Analysis and Design Completed
N/A
3.3. Activity Detailed Analysis and Design
3.3.1. Task Document system changes needed to meet user requirements
3.3.2. Task Document detailed specifications
3.3.3. Task Review detail design
3.3.4. Task Revise Project Plan
3.3.5. Task Draft Implementation Plan
N/A 0
Detailed Design Completed
3.3.5.1. Milestone
N/A
3.4. Activity Construction
3.4.1. Task Create Test scripts
3.4.2. Task Perform coding changes to specification, conduct code review and perform unit testing
3.4.3. Task Update System Test Plan
D:\Docstoc\Working\pdf\78a553cb-03c8-4566-a134-4896c77723cd.doc Page 6
Last printed 4/14/2011 5:25:00 PM
<Project Title or Acronym> Integrated Project Plan
Del Name & # Dur. Critically Skill
# WBS Dictionary Est. Depend
N/A 0
Construction Completed
3.4.3.1. Milestone
N/A
3.5. Activity Testing
3.5.1. Task Perform System Testing
3.5.2. Task Perform Integrated systems testing
3.5.3. Task Perform User acceptance testing and obtain acceptance approval
3.5.4. Task Finalize Implementation Plan
N/A 0
Testing Completed
3.5.4.1. Milestone
N/A
3.6. Activity Implementation
3.6.1. Task Perform training
3.6.2. Task Communicate changes
3.6.3. Task Execute implementation plan.
3.6.4. Task Perform post implementation activities, file documentation and wrap –up loose ends.
N/A 0
System or Application Implemented
3.6.4.1. Milestone
N/A
4. Phase Controls – Administer and manage work controls to ensure project performance.
D:\Docstoc\Working\pdf\78a553cb-03c8-4566-a134-4896c77723cd.doc Page 7
Last printed 4/14/2011 5:25:00 PM
<Project Title or Acronym> Integrated Project Plan
Del Name & # Dur. Critically Skill
# WBS Dictionary Est. Depend
N/A
5. Phase Close – Evaluate the project’s achievement of scope, objectives, and measurements.
Identify the maintenance plan, turnover to maintenance, and release project resources.
N/A
5.1. Activity Project Evaluation – Recognize the achievements and lessons learned of the
project, and determine readiness to close the project.
Project PM
5.1.1. Task Prepare a project evaluation – Review the project’s completion criteria, scope, Evaluation
objectives, measurements, and lessons learned. Identify all items or components, and
their production version/location, which will become maintenance responsibility. Ensure
change request log is accurate and up-to-date. Ensure all issues and prior decisions are
documented for turnover. Identify maintenance staff and any associated budgets. Meet
with maintenance lead and review this information.
N/A 0
Project successfully closed
5.1.1.1. Milestone
D:\Docstoc\Working\pdf\78a553cb-03c8-4566-a134-4896c77723cd.doc Page 8
Last printed 4/14/2011 5:25:00 PM
Related docs
Other docs by vhh18453
LIABILITY LETTER OF CREDIT HAZARDOUS WASTE MANAGEMENT The Letter of Credit authorized by R 299 9710 10 must be worded as follows exc
Views: 30 | Downloads: 0
