SWE 387

Software Project Management Plan (SPMP)

The document in this file is an annotated outline for specifying Software Project
Management Plan, adapted from the IEEE Standard for Software Project
Management Plans (Std 1058-1998) and from other online resources.

Tailor this to your needs, removing explanatory comments as you go along.

Where you decide to omit a section, you might keep the header, but insert a
comment saying why you omit the data.

Page 1 of 9
Note: Text displayed in blue italics is included to provide guidance to the author and should be deleted or
hidden before publishing the document.

Project Plan
for
<Project name>

<Team., Name>

<version>

<Date>

Help: The purpose of the Project Plan is to document all managerial aspects of a project that are required to
execute it successfully within its constraints.

Don’t remove of not applicable section, rather specify clearly that the section is not applicable.

Page 2 of 9
 Document History and Distribution

1. Revision History

Revision Revision Description of Change Author

# Date
1.0 xx/xx/2018 Initial Document

1.

Page 3 of 9
 Contents
1. Overview.....................................................................................................................
2. Goals and Scope...........................................................................................................
2.1 Project Goals................................................................................................................
2.2 Project Scope................................................................................................................
2.2.1 Included.......................................................................................................................
2.2.2 Excluded......................................................................................................................
2.3 References.....................................................................................................................
3. Organization................................................................................................................
3.1 Organizational Boundaries and Interfaces.....................................................................
3.2 Project Organization.....................................................................................................
3.2.1 Project Team................................................................................................................
4. Schedule and Budget....................................................................................................
4.1 Schedule and Milestones................................................................................................
4.2 Cost Estimation.............................................................................................................
4.2.1 Budget.........................................................................................................................
4.3 Development Process.....................................................................................................
5. Management Plans.......................................................................................................
5.1 Integration Management...............................................................................................
5.1.1 Configuration Management Plan....................................................................................
5.1.2 Change management plan..............................................................................................
5.1.3 Delivery Plan................................................................................................................
5.2 Scope Management Plan...............................................................................................
5.3 Schedule Management Plan...........................................................................................
5.4 Cost Management Plan.................................................................................................
5.5 Quality Management Plan.............................................................................................
5.6 Staffing Management Plan............................................................................................
5.7 Communication Management Plan...............................................................................
5.8 Risk Management.........................................................................................................
5.8.1 Risk Register................................................................................................................
5.9 Procurement Management Plan....................................................................................
5.9.1 Procurement Management.............................................................................................
5.9.2 Sub-contract Management.............................................................................................
6. Abbreviations and Definitions......................................................................................

Page 4 of 9
1. Overview
Help: This section describes a management summary. Provide essential information like:
 What the motivation for this project is
 Who the customer is
 What the project will deliver. Is it a new product or an extension of an existing one?

2. Goals and Scope

2.1 Project Goals
Help: The project goals define the expected project results
Identify the various categories of project goals such as functional, technological, etc.

2.2 Project Scope

Help: Clarify what the project will (and will not) deliver.

2.2.1 Included
Help: State what is specifically included in the project.
The deliverables of this project are listed in detail in the delivery plan section 5.1.3.

2.2.2 Excluded
Help: State what is specifically excluded from the project but what the customer may expect to be
included. This could, for example, be clarifying that training of end-users is excluded.

2.3 References
Help: [This subsection should provide a complete list of all documents referenced elsewhere in the Project
or Software Development Plan. Each document should be identified by title, report number (if
applicable), date, and publishing organization.]
<Doc. No.> Project Proposal for <project name>

3. Organization
3.1 Organizational Boundaries and Interfaces
Help: Identify the external stakeholders of the project. Describe the administrative and managerial
boundaries between the project and each of the following entities: the parent organization, the
customer organization, subcontracted organizations, and any other organizational entities that
interact with the project.
e.g. The team leads will be responsible for the communication between each team
member for a particular phase and meetings will also be conducted by the lead for
proper interaction. The documentation will be done by individual who has been
assigned with their respective task

3.2 Project Organization

Help: Describe how the project is organized. Graphical illustrations such as hierarchical organization
charts or matrix diagrams may be used to depict the lines of authority, responsibility, and
communication within the project.

3.2.1 Project Team

Help: List all project team members here and ensure that the time they spend on the project is accounted
for in the project budget.

Team member Role Comment

Page 5 of 9
 Team member Role Comment

4. Schedule and Budget

4.1 Schedule and Milestones
Help: Define the full schedule that includes the Work Breakdown Structure, the work packages and
project activities with their sequencing. Also, show the milestones. It is normally a separate
document, therefore list it in References and refer to it.

4.2 Cost Estimation

Help: Use any estimation method to estimate the cost of the project, show the details of the estimation.

4.2.1 Budget
Help: Calculate the required project budget based on cost estimates for project activities, sub-contracts,
training, etc. Present the distribution of the budget over the whole project life.

Category Budget for Period in SAR

Months
1 2 3 4 5 6
Human Resources
Purchases
Equipment
Tools
Travel costs
Training
…
Total
Total cumulated

4.3 Development Process

Help: Describe the development process applied in this project. Explain why this development process has
been selected.

5. Management Plans
5.1 Integration Management
5.1.1 Configuration Management Plan
NA
5.1.2 Change management plan
Help: This section should describe your change control process. This section should identify who has
approval authority for changes to the project, who submits the changes, how they are tracked and
monitored.

5.1.3 Delivery Plan

Help: List here all deliverables from the project and who the receivers of the deliverables are. Indicate
also the planned delivery date.

# Deliverable Planned Date Receiver

D1
D2

Page 6 of 9
Page 7 of 9
 5.2 Scope Management Plan
Help: This section provides a summary of the Scope Management Plan in which it addresses the
following:
 Who has authority and responsibility for scope management
 How the scope is defined (i.e. Scope Statement, WBS, WBS Dictionary, Statement of Work,
etc.)
 The scope change process (who initiates, who authorizes, etc.)
 Who is responsible for accepting the final deliverable and approves acceptance of project
scope

5.3 Schedule Management Plan

Help: This section provides a general framework for the approach which will be taken to create the
project schedule. This section should include discussion of the scheduling tool/format, schedule
milestones, and schedule development roles and responsibilities.

5.4 Cost Management Plan

Help: The Cost Management Plan defines how the costs on a project will be managed throughout the
project’s lifecycle. The Cost Management Plan:
 Identifies who is responsible for managing costs
 Identifies who has the authority to approve changes to the project or its budget
 How cost performance is quantitatively measured and reported upon

5.5 Quality Management Plan

Help: This section discusses how quality management will be used to ensure that the deliverables for the
project meet a formally established standard of acceptance. This section should include quality
roles and responsibilities, quality control, quality assurance, and quality monitoring.

5.6 Staffing Management Plan

Help: Discuss how you plan to staff the project. This section should also specify the key resources needed
for the project. Include a Resource Calendar as part of your project plan. The resource calendar
identifies key resources needed for the project and the times/durations they'll be needed.

5.7 Communication Management Plan

Help: Include, for example, how often the reporting will take place, the type of reports or information, the
type of media in which it is presented, and the type of meetings that will take place.

5.8 Risk Management

Help: Describe the procedure to be used for managing risks in the project. The procedure should specify
who is responsible for risk management.

5.8.1 Risk Register

Help: The complete risk table for the identified risk is presented

5.9 Procurement Management Plan

5.9.1 Procurement Management
Help: The Procurement Management Plan should clearly identify the necessary steps and
responsibilities for procurement from the beginning to the end of a project.

5.9.2 Sub-contract Management

Help: List which part of work is outsourced to which sub-contractor.

6. Abbreviations and Definitions

Help: List all abbreviations and definitions used within this document.
Page 8 of 9
CCB Change Control Board
CM Configuration Management
CR Change Request

Page 9 of 9