[ Project ]

Project Plan

315798466.doc

Draft X
August 30, 2001

[ Organization Name ]
[ Paste Your Organizations Logo Here ]

Powered By

www.construx.com

[Paste your logo here] [ Organization Name ]

[ Project ] - Project Plan

Revisions
Version

Primary
Author(s)

Description of Version

Draft Type
and
Number

Full Name

Information about the revision. This table does not

need to be filled in whenever a document is
touched, only when the version is being upgraded.

Date
Completed
00/00/00

CxPattern_RevisionHistory provides details on

CxOnes recommended way to handle document
revisions.

The paragraphs written in the Comment style are for the benefit of the person writing
the document and should be removed before the document is finalized.
A project plan is the controlling document for managing a software project.
CxStand_ProjectManagement defines what CxOne requires for project plans.
CxGuide_ProjectPlan provides detailed information on how to use this template along with
background information on project planning.
This project plan template is intended to scale with the size of a project. On very small
projects, the project plan may be the only documentation for a project (also consider using
CxTemp_ProjectPlanLite). On very large projects, a family of project plans may exist. Most
projects will lie somewhere in-between, with the project plan being a combination of direct
information and pointers to other project documents.

315798466.doc (08/30/01)

Page i
Portions Copyright 2001 Construx Software Builders, Inc.

[Paste your logo here] [ Organization Name ]

[ Project ] - Project Plan

Review & Approval

If appropriate, this section contains formal sign-off for both review and approval of the
project plans. Normally the projects authority and agent should formally sign off the plan to
launch a project.
Project Plan Approval History
Approving Party

Version
Approved

Signature

Date

Signature

Date

Authority 1
Authority n
Agent

Project Plan Review History

Reviewer

Version
Reviewed

Authority 1
Authority n
Agent
Stakeholder 1
Stakeholder n
Etc.

315798466.doc (08/30/01)

Page ii
Portions Copyright 2001 Construx Software Builders, Inc.

[Paste your logo here] [ Organization Name ]

[ Project ] - Project Plan

Contents
REVIEW & APPROVAL..................................................................................................II
1 INTRODUCTION...........................................................................................................1
1.1 OVERVIEW................................................................................................................1
1.2 DELIVERABLES.........................................................................................................1
1.3 ASSUMPTIONS AND CONSTRAINTS...........................................................................1
1.4 REFERENCE MATERIALS...........................................................................................1
1.5 DEFINITIONS AND ACRONYMS..................................................................................1
2 MANAGEMENT STRUCTURE......................................................................................2
2.1 PROJECT LIFECYCLE.................................................................................................2
2.2 PROJECT ORGANIZATION..........................................................................................2
2.2.1 External Interfaces....................................................................................................2
2.2.2 Internal Structure......................................................................................................2
2.2.3 Roles and Responsibilities........................................................................................2
2.2.4 Staffing......................................................................................................................2

2.3 COMMUNICATION.....................................................................................................3
2.4 RISK AND ASSET MANAGEMENT..............................................................................3
2.5 STARTUP...................................................................................................................3
2.6 CLOSEOUT................................................................................................................3
3 PLANNING AND CONTROL.........................................................................................4
3.1 ESTIMATE..................................................................................................................4
3.1.1 Estimation Process...................................................................................................4

3.2 RESOURCE IDENTIFICATION......................................................................................4

3.2.1 Staff...........................................................................................................................4
3.2.2 Time..........................................................................................................................4
3.2.3 Cost...........................................................................................................................4
3.2.4 Materials..................................................................................................................4

3.3 RESOURCE ALLOCATION...........................................................................................4

3.3.1 Work Breakdown Structure.......................................................................................5
3.3.2 Schedule....................................................................................................................5
3.3.3 Budget.......................................................................................................................5

3.4 TRACKING AND CONTROL........................................................................................5

4 TECHNICAL PROCESS................................................................................................6
4.1 ENGINEERING...........................................................................................................6
4.1.1 Environment..............................................................................................................6
4.1.2 Methods, Tools and Techniques................................................................................6

315798466.doc (08/30/01)

Page iii
Portions Copyright 2001 Construx Software Builders, Inc.

[Paste your logo here] [ Organization Name ]

[ Project ] - Project Plan

4.2 TECHNOLOGY...........................................................................................................6
4.2.1 Environment..............................................................................................................6
4.2.2 Methods, Tools, and Techniques................................................................................6

4.3 INFRASTRUCTURE.....................................................................................................6
4.4 PROJECT ARTIFACTS.................................................................................................6
5 SUPPORTING PLANS...................................................................................................7
5.1 CONFIGURATION MANAGEMENT..............................................................................7
5.2 QUALITY ASSURANCE..............................................................................................7
5.3 TESTING....................................................................................................................7
5.4 DEPLOYMENT...........................................................................................................7
5.5 INTEGRATION............................................................................................................7
5.6 PROCUREMENT.........................................................................................................7
5.7 OPERATIONS.............................................................................................................7
5.8 MAINTENANCE.........................................................................................................7
5.9 STAFF DEVELOPMENT..............................................................................................8
5.10 PRODUCT ACCEPTANCE..........................................................................................8

315798466.doc (08/30/01)

Page iv
Portions Copyright 2001 Construx Software Builders, Inc.

[Paste your logo here] [ Organization Name ]

[ Project ] - Project Plan

1 Introduction
This project plan is the top level controlling document for the [ Project ] project, whose
charter is [Project Charter Document Reference].
The introduction section provides context for the project. Where appropriate the project
charter should be referenced. This section may provide additional detail to charter content,
but should avoid simply duplicating information in the charter.

1.1 Overview
This section normally consists of a summary of project purpose, scope, and objective. It may
also include background for the project, a summary of the project planning, or other
contextual material as appropriate.

1.2 Deliverables
What are the ultimate deliverables that will be delivered to the customers or consumers of the
project? If appropriate, a delivery milestone schedule should be provided.

1.3 Assumptions and Constraints

A formal or informal collection of assumptions, constraints, external dependencies, etc.

1.4 Reference Materials

(Optional) Bibliographic listing of non-project and non-CxOne materials referenced in the
plan. CxOne and project materials are normally referenced in-line.

1.5 Definitions and Acronyms

(Optional) List any project definitions and acronyms introduced to the project by this plan.
Do not repeat items covered in the CxOne definitions and acronyms document or in a global
project definitions and acronyms document.

315798466.doc (08/30/01)

Page 1
Powered by CxOne from Construx Software Version 2.0

[Paste your logo here] [ Organization Name ]

[ Project ] - Project Plan

2 Management Structure
This section covers all aspects of managing the project that are not related to estimating,
planning, and controlling the work.

2.1 Project Lifecycle

Describe in detail the lifecycle for the project. Normally this section discusses phases,
deliverables, and dates abstractly to provide a clear view of the project time line from a
process standpoint and to avoid duplicating content from other sections.

2.2 Project Organization

Describe the organization structure (management, groups, roles, etc.) of the project and
relationships to the external organization or other projects.

2.2.1 External Interfaces

2.2.2 Internal Structure
2.2.3 Roles and Responsibilities
A table like the one below can be used, roles shown are illustrative of a software project
based on CxOne lead positions:
Role

Responsibility

Project Manager
Planning and Tracking Lead
Requirements Lead
Quality Assurance Lead
Design Lead
Implementation Lead
Development Engineer
QA Engineer

2.2.4 Staffing
Contains the schedule of assignment of roles and responsibilities to particular individuals.
Role

Staff Member

Start Date

End Date

Project Manager

315798466.doc (08/30/01)

Page 2
Powered by CxOne from Construx Software Version 2.0

[Paste your logo here] [ Organization Name ]

Role

[ Project ] - Project Plan

Staff Member

Start Date

End Date

Planning and Tracking Lead

Requirements Lead
Quality Assurance Lead
Design Lead
Implementation Lead
Development Engineer 1
Development Engineer n
QA Engineer 1

2.3 Communication
Describe the types of communication that need to occur during the project and their timing.

2.4 Risk and Asset Management

Describe how risks and assets will be actively managed on a project. On small projects risk
identification and mitigation could go here, but normally are separate artifacts.
Relevant CxOne Materials: CxCheck_RiskLists, CxPattern_RisksList.

2.5 Startup
(Optional) What special steps are necessary to get the project up and running?

2.6 Closeout
(Optional) How will the project ramp down and end or transition into a new project?

315798466.doc (08/30/01)

Page 3
Powered by CxOne from Construx Software Version 2.0

[Paste your logo here] [ Organization Name ]

[ Project ] - Project Plan

3 Planning and Control

This section covers all aspects of managing the project related to estimating, planning, and
controlling the work. Most project plans will contain pointers to specialized artifacts and
group of artifacts for the items in this section.

3.1 Estimate
Describe any and all estimates to date relating to the project. This section will often refer to a
separate project estimate document or set of artifacts.
Relevant CxOne Materials: CxCheck_ProjectEstimate.

3.1.1 Estimation Process

How and when will estimates be refined during the project? This may be handled in other
sections including project lifecycle or tracking and control.

3.2 Resource Identification

List the resources available to the project including information on available staff, time, cost,
materials, etc. When appropriate, describe the resource obtainment and phase out timelines.

3.2.1 Staff
Unlike the staffing section that assigns individuals to the project, this section deals with
abstracted planning of the peak staff, staffing profile, and staff build-up of the project.

3.2.2 Time
What is the available calendar time for the project. This section normally consists of detailed
constraints.

3.2.3 Cost
The available budget for the project.

3.2.4 Materials
Materials that will be used for the project, if any.

3.3 Resource Allocation

Describe the allocation of the resources to meet the project goals. This section will at a
minimum refer to a WBS and top-level project schedule. It may also refer to multiple
schedule views, budgeting plans, etc.

315798466.doc (08/30/01)

Page 4
Powered by CxOne from Construx Software Version 2.0

[Paste your logo here] [ Organization Name ]

[ Project ] - Project Plan

3.3.1 Work Breakdown Structure

This section refers to the WBS for the project, which is normally an external document. The
WBS breaks down all work on the project into work packages.
Relevant CxOne Materials: CxCheck_WorkBreakdownStructure.

3.3.2 Schedule
This section refers to schedules for the project. There are usually several different schedules
of varying levels of detail that describe the allocation of work packages. Most schedules are
stored in separate documents or specialized schedule tools, but this section may contain a
top-level summary schedule.
Relevant CxOne Materials: CxCheck_DetailedSchedule, CxCheck_BusinessSchedule.

3.3.3 Budget
(Optional) Cover allocation of budget resources to the project. This may not be needed
because often budget allocation is implied by the allocation of staff effort, as that is usually
the largest cost driver on software projects.

3.4 Tracking and Control

Describe how project cost, schedule, quality, and functionality will be tracked and controlled
throughout the project.
This section will normally delegate quality tracking to the QA plan and functionality tracking
to the CM plan, but impacts of those areas on the top-level schedule should be covered (such
as audits or planning checkpoint reviews).
Relevant CxOne Materials: CxCheck_ExecutiveStatusReport,
CxTemp_ExecutiveStatusReport, CxCheck_DetailedStatusReport,
CxTemp_DetailedStatusReport.

315798466.doc (08/30/01)

Page 5
Powered by CxOne from Construx Software Version 2.0

[Paste your logo here] [ Organization Name ]

[ Project ] - Project Plan

4 Technical Process
Describes or summarizes the top-level technical processes used on the project.

4.1 Engineering
Covers environment, tools, methods, and techniques related to software engineering.

4.1.1 Environment
4.1.2 Methods, Tools and Techniques

4.2 Technology
Covers environment, tools, methods, and techniques related to technology.

4.2.1 Environment
4.2.2 Methods, Tools, and Techniques

4.3 Infrastructure
What needs to be done to create development environments?

4.4 Project Artifacts

(Optional) If appropriate, this section describes all planned artifacts or groups of artifacts
for a project.

315798466.doc (08/30/01)

Page 6
Powered by CxOne from Construx Software Version 2.0

[Paste your logo here] [ Organization Name ]

[ Project ] - Project Plan

5 Supporting Plans
This section either incorporates or references via pointer detailed supporting plans.

5.1 Configuration Management

Identification and organizational of project artifacts, change control, builds, and release
processes. Often the different components of configuration management may be broken into
separate specialized plans.
Relevant
CxOne
Materials:
CxTemp_ConfigurationManagementPlan.

CxCheck_ConfigurationManagementPlan,

5.2 Quality Assurance

Planning, tracking, and control for ensuring project meets quality goals. Also discusses
technical process specific to quality assurance, such as reviews.
Relevant CxOne Materials: CxCheck_QualityPlan, CxTemp_QualityPlan.

5.3 Testing
Planning for execution and tracking of test activities, including test coverage planning..
Relevant CxOne Materials: CxCheck_TestPlan, CxTemp_TestPlan.

5.4 Deployment
Normally this section will point to a dedicated document if there are any significant
deployment issues.
Relevant CxOne Materials: CxCheck_DeploymentPlan.

5.5 Integration
(Optional) Covers integration between sub-projects, tasks, releases, or other significant
project integration. Normally this section will point to a dedicated document if it is needed.

5.6 Procurement
(Optional) Covers significant procurement of materials or sub-contracted services on a
project. Normally this section will point to a dedicated document if it is needed.

5.7 Operations
(Optional) Covers issues related to system operation after deployment. Normally this
section will point to a dedicated document if it is needed.

315798466.doc (08/30/01)

Page 7
Powered by CxOne from Construx Software Version 2.0

[Paste your logo here] [ Organization Name ]

[ Project ] - Project Plan

5.8 Maintenance
(Optional) Covers issues related to maintenance phase of a project. If the project itself is a
maintenance effort this would not be needed. Normally this section will point to a dedicated
document if it is needed.

5.9 Staff Development

(Optional) Covers significant training, teambuilding, or other staff development activities,
e.g., a hiring plan. Normally this section will point to a dedicated document if it is needed.

5.10 Product Acceptance

(Optional) If significant customer acceptance activities are necessary that cannot be
handled as part of the test plan.

315798466.doc (08/30/01)

Page 8
Powered by CxOne from Construx Software Version 2.0