Template For A Software Project Management Plan

Template for a Software Project Management Plan (SPMP)
Project Id: ______

Project Name: ________
Project Manager: ______
Project Plan Version # _______
Location: ________________
Status: _______
Approved by: _______
CHANGE HISTORY
DATE CHANGED BY APPROVED BY DESCRIPTION
1. Introduction
1.1. Project Identification
Provides a unique identifier for this project
1.2. Project Summary

Presents a brief summary of the project. This and the Project Objectives given below
provide the basic links to the Statement of Work from the Requirements Management
KPA
1.3. Project objectives

Briefly states the high level objectives of the project
2. References
Lists the documents referred to in this SPMP. One would be Statement of Work from the
Requirements Management; others could include standards, templates, etc.
3. Assumptions and dependencies

Documents the basic assumptions, which have been made in arriving at the SPMP. Some of these
could come from the Statement of Work (e.g., Responsibilities of customer and organization).
Others may be new for the planning phase (e.g., availability of planning tools)
4. Terminology, Definitions and Abbreviations

Lists out the terminology, definitions and abbreviations/acronyms used in this plan. Ideally, these
should be consistent with what is used in the Statement of Work.
5. Project Deliverables
5.1. External deliverables
Documents the specific deliveries to be made to the customer. These could be software,
documentation, etc. Captures details like media, number of copies, etc. This information
is likely to have been available in the Statement of Work.
5.2. Internal deliverables
Identifies the internal deliverables. These need not be given to customers but are needed
to verify and quantify internal progress (e.g., internal testing plans would be necessary to
plan and track the project but need not be delivered to the customer)
6. Components and Constraints

6.1. Identification of Components and Work Breakdown Structure Units
Identifies the individual components that the project is composed of. Translates into WBS
units that have clear accountability, well identified deliverables and presents clean
interfaces.
6.2. Non-negotiable constraints

If there are any non-negotiable constraints in terms of cost, schedule etc, these are
documented here. These are likely to be taken directly from the Statement of Work.
7. Project Success Measures

7.1. Quantitative targets for measuring project success
The high-level project goals (that are identified in the Statement of Work) are translated
into quantitative targets. The goals cover timelines (e.g., delivery dates), quality (e.g.,
defect density), performance (e.g., response times), etc.
8. Configuration Management Plans.

We will discuss this in detail in the Software Configuration Management Plan (SCMP) template in
Chapter 9. The SCMP can be considered as a part of the SPMP, even if it is maintained as a
separate document
9. Development methodologies
9.1. Life cycle model
Specifies which life cycle model is going to be used for the project (e.g., Waterfall, Spiral,
etc)
9.2. Standards (external and internal)

Specifies the external standards (e.g., API standards like JDBC) and internal standards
(e.g., coding and documentation standards) to be used in the project.
9.3. Specific processes to be used for the project

Lists the specific processes to be followed for the project. This includes processes for
planning, development, testing, release, etc.
10. Quality Plan

Details of this are discussed in Chapter 7 on Software Quality Assurance. Like SCMP, SQA plan
could be a separate document but can be considered as part of the SPMP.
11. Estimations
11.1. Size estimation
Documents the size estimation method used, assumptions and base data used to get the
size estimates and the eventual estimates themselves
11.2. Effort estimation

Documents the effort estimation method used, assumptions and base data (e.g.,
productivity data, project type, etc.) used to get the effort estimates and the eventual
estimates themselves
11.3. Schedule estimation

Documents the schedule estimation method used, assumptions and base data (e.g.,
parallelism possible, resource availability) used to get the estimates and the eventual
estimates themselves
12. Schedules
12.1. Critical path activities
From the schedules, identifies the critical path activities to ensure they get better
visibility and attention
12.2. Resource – Activity map

This is a by-product of the schedule and resources. By mapping who is doing what
activity (and when), a clearer picture of accountability emerges.
13. Human Resource Requirements

13.1. Staffing plans
Lists the need for the various people at various time periods within the project life span.
This helps planning for resources available (just) in time.
13.2. Skill sets and experience requirements

Lists the skill sets and preferred experience levels for the project members. This would
help in focused hiring.
13.3. Training plans

Identifies the training needs for each individual. This would include what training needs
to be offered, who should take the training and when. Acts as inputs to the Training KPA
in Level 3
13.4. Organization structure and responsibilities

Presents an organization chart of the project, with clear identification of roles and
responsibilities
14. Computer Resources Requirements

14.1. Project-specific computer hardware and software requirements
Lists the hardware and software specifically required for this project. Includes
workstations, project specific servers, software licenses, etc.
14.2. Infrastructure requirements

Documents the demands made on infrastructure by this project. Examples are additional
burden placed on the communication infrastructure, common servers like email servers,
configuration management servers etc.
14.3. Identification of and planning for critical computer resources

Demarks the critical computer resources, so that extra attention can be given to these
critical resources.
15. Stakeholder Involvement Plan

Lists the requirements from other groups within the organization.
XXX Raja, I am unable to edit this to put section numbers to add Data Control Plan. Also, this
template looks too fat, with stuff not directly in CMMI
16. Risk Management

16.1. Risk identification and quantification
Documents the risks that are anticipated and the rationale for expecting these risk; also
quantifies / prioritizes the risks on the dimensions of probability of occurrence and the
impact.
16.2. Risk symptoms mitigation strategies
Identifies the symptoms which are tell-tale signs of impending risks and possible “Plan
B” mitigation strategies
17. Tracking and Project Management

These link the planning phase to the tracking phase.
17.1. Factors to be tracked

Identifies the specific factors to be tracked. Some of these could be size estimate,
cumulative costs, risks encountered, etc.
17.2. Tracking and reporting frequency and responsibility

Identifies the specific responsibilities to track the chosen parameters, who would capture
the tracking data, how it would be reported, etc.
17.3. Project Plan change management, review and approval procedures

Documents the conditions and procedures for changing the plan. Examples could be
reviewing (and changing, if necessary) the plan on a periodic basis (e.g., bi-weekly) or
when certain key factors (e.g., schedule) slip by more than a threshold percentage)
18. Management Reporting and review procedures

18.1. Management Review procedures
Lists out planned activities for tracking and review – project review meetings by the
Project Manager, senior management review, status reporting details, etc.
18.2. Service Level Agreements and Escalation mechanisms

Commitments expected from each group in terms of service levels. Also specifies
escalation channels if the service levels are not met.

Template For A Software Project Management Plan

Uploaded by

Copyright:

Available Formats

Template For A Software Project Management Plan

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Template For A Software Project Management Plan

Uploaded by

Copyright:

Available Formats

Template for a Software Project Management Plan (SPMP)

Project Id: ______

1.2. Project Summary

1.3. Project objectives

3. Assumptions and dependencies

4. Terminology, Definitions and Abbreviations

6. Components and Constraints

6.2. Non-negotiable constraints

7. Project Success Measures

8. Configuration Management Plans.

9.2. Standards (external and internal)

9.3. Specific processes to be used for the project

10. Quality Plan

11.2. Effort estimation

11.3. Schedule estimation

12.2. Resource – Activity map

13. Human Resource Requirements

13.2. Skill sets and experience requirements

13.3. Training plans

13.4. Organization structure and responsibilities

14. Computer Resources Requirements

14.2. Infrastructure requirements

14.3. Identification of and planning for critical computer resources

15. Stakeholder Involvement Plan

16. Risk Management

17. Tracking and Project Management

17.1. Factors to be tracked

17.2. Tracking and reporting frequency and responsibility

17.3. Project Plan change management, review and approval procedures

18. Management Reporting and review procedures

18.2. Service Level Agreements and Escalation mechanisms

You might also like