Project Work Products Outline

Actions and Issues

A log that includes the following elements:
• Item #
• Description
• Assigned individual
• Target completion date
• Action taken (open, closed, pending)
• Key learnings

Enables the PM and others to keep track of and

eventually close actions and issues that affect tasks and
milestones within the project plan
Change Request Log
A Change Log is a list containing some of the information about
all or some of the Change Requests.

The purpose of the Change Log is to provide summary

information about all the unforeseen changes that the project is
managing. For example, a Change Log could be used as an
agenda for a change board meeting or to provide input for a
status report.
Critical Success Factors
The Critical Success Factors work product identifies those
elements of the project or solution that must go right for the
project to be successful.

The purpose of the Critical Success Factors is to serve as a

guide for solution development, testing, and deployment.
Critical success factors may apply to any area of the project.
For Example:
o Project Schedule

o Program

o Component

o System Integration

o Operation/Production

o Organization Impact

Customized Work Breakdown Structure

The purpose of the Work Breakdown Structure is to
define all the activities that the project team must
complete and so to provide a basis upon which the work
can be scheduled.

Without a Work Breakdown Structure, the project team

does not have a clear definition of the work that it is
required to carry out.
Financial Template Description

Should include:
-Overview
-Department financials
-structure
-breakdown
-roles and responsibilities
-Corporate finance and charge codes
-Funding
-approval
-recoveries
-purchase orders
-capital funds/requirements
-agreements
-Statementsof Work
-Forecasts vs. actuals
-original forecast
-tracking actuals
Purpose

To be able to plan for and defend budget items at each status

juncture.

Integrated Project Plan (D) (High Description

Level)
The Integrated Project Plan is the way in which the project is managed.
It is documented as a collection of plans and procedures that direct all
project management activity and records, which provide evidence of their
implementation.
For each of these plans, procedures and records, the Integrated Project
Plan typically:
• Either provides a brief overview of the work product and
specifies the location of the full document

• Or (particularly on small projects) replaces the work product

entirely

The Integrated Project Plan is a relatively short document. The

level of detail is such that all the key aspects of the project (i.e.
those of which the sponsor and/or functional management
should be aware) are fully documented but less important
information is relegated to the supporting plans, procedures
and records.
Purpose

The purpose of the Integrated Project Plan is to:

• Help ensure that all members of the project team understand:

- how the project will be managed

- their role within the management process

o Document the agreement between the project

manager and constituency senior management
 regarding how the project will be managed

o Document any agreed deviations from constituency

policy and practice that have been agreed with senior
management and, if appropriate, the quality assurance
function

o Provide a starting point for project audits or

compliance reviews
The primary uses of the project plan are to document planning
assumptions and decisions, to facilitate communication among
stakeholders, and to document approved scope, cost, and schedule
baselines. A project plan may be summary or detailed. A systems
development plan might include:
o Initial Plan Activities

o High Level Technical Integrated Project/Program Plan

o High Level Data Migration activity

o Data Migration CoC activity

o Critical Path Analysis of Integrated Program

Components

o High Level System Integration Activities

o Life Cycle and Production Support

o Global support

Key Project Assumptions Description

The Key Project Assumptions work product is a listing of those items

which the project team determines to be "givens" for the project. If Key
Project Assumptions become invalid, the project plan will require
revision.
Purpose

Assures that the there are no surprises during the implementation and
deployment of the project

Key Project Dependencies Description

The Milestone List is a definition of the key milestones contained in

theProject management schedule together with a log of all the changes
that have been planned for those milestones during the course of the
project. For BTOP projects, dependencies on other organizations or
projects should be included in the Milestone List as a single point of
reference for dependencies.
Purpose

The purpose of the Milestone List is:

• To provide a high-level summary of the Project management
schedule that the project manager can use to focus on the
important events within his/her remit in and as a means of
communications with the other stakeholders.

• To provide a history of any changes that have occurred to the

milestones or their dates.
Lessons Learned Description

Key facts describe real project circumstances that are important to day-
to-day decision making. The Key Fact Log records the history of the
project as told by these key facts.
Purpose

The Key Fact Log is intended to:

• Shed light on situations involving project objectives, and
therefore help the project manager to deal with them.

• Provide background for issue identification and resolution.

• Facilitate assessment of "lessons learned" by providing

historical data.

• Help project managers at any level demonstrate how they carry

out their responsibilities when confronting day-to-day project
situations.

Operational Schedule for Each Description

Phase
Each project organizational unit (team) that does technical work (as
opposed to only project management work) develops a series of
Operational Schedules. The schedule shows how the work of the project
team is broken down into work packages, each of which has a planned
completion date and is assigned to an individual named resource or a
small team of named resources.
Operational Schedules are created during each phase and then
recreated several times during the remainder of the project. The
planning horizon, i.e., the duration of the schedule, is typically the
shorter of the end of the current project phase or one to three months.
There may be more than one sub-project team within an operational unit.
In that case, each team leader owns his section of the Operational
Schedule.
Purpose

The purpose of the Operational Schedule is:

• To provide each member of the project team with a list of work
packages together with target dates for their completion.

• To enable the team leaders to track progress from day to day.

Each project organizational unit that does technical work must

have an Operational Schedule.

Project Charter Description

The Project Charter formalizes the request from a sponsor for

responding to a business need.

The Project Charter is usually a short document that refers to some other
more detailed documents such as a ‘new offering request’ or a ‘request
for proposal’.
Notice that the Project Charter is a special work product that is created
by the sponsor.

Purpose
 The purpose of the Project Charter is to write down:
The reasons for undertaking the project.
The project objectives and constraints.
Directions concerning the solution.
Who are the main stakeholders.
Project Definition Document Description

The Project Definition contains the results of the Defining Activities.

Those results are used as a starting point to build the project plan.
Purpose

The purpose of the Project Definition is to:

• Formalize the understanding of the Project Charter by the
delivery organization.

• Provide the plan elements in order to control the Defining

Activities.

• Give an initial description of the project "shape" used as a

framework for the Planning Activities.

• Provide the plan elements in order to control the Planning

Activities.

• Gather the fundamental characteristics of the project in a

unique document.

Project and Resource Plan Description

This is the project plan that is built in a PM Software program such as

Microsoft project, Project Workbench, Primavera, etc. This is built in
conjunction with a base resource Plan in the same software
Purpose

Enables team to understand the extent of the plan

Utilizes resources efficiently who are assigned to multiple
projects.
Risk Management Plan Description

The Risk Management Plan is the collection of the project's mitigation,

contingency and reserve plans for dealing with identified risks. Each
individual plan addresses a single risk or a group of related risks.
Because a single risk or group or related risks can have more than one
planned response (e.g., a risk can be addressed by both a mitigation
and a contingency plan), there is one risk response plan (entry) in the
Risk Management Plan for each planned response for each identified
risk or group of related risks.
Purpose

The purpose of the Risk Management Plan is to document all the plans
associated with a risk or set of related risks.
• Risk mitigation plans identify the activities that have been
planned to reduce the probability of the occurrence of a
particular risk and/or to minimize the adverse impact of the
occurrence of a particular risk.

• Risk contingency plans define the strategies, activities, and

 budget that have been planned for responding to a particular
risk, if and when the risk occurs.

• Reserve plans define the management and/or contingency

reserves set-side to address risks affecting the project's costs
or schedules.

Team Charter Description

This is the agreement that describes the roles and responsibilities of

each team member and is signed (electronically) and returned to the
Project Manager
Purpose

Enables all team members to understand:

ƒ Project Expectations
ƒ Project success factors
ƒ Administrative process
ƒ Roles and responsibilities