Software Project Plan 6/2/2005
Project Plan
Document Number: [nn]
Date: Day, Month Day, Year
[Project Name]
[Authors]
Professor [Name]
Software Engineering Department
Monmouth University
West Long Branch, NJ 07764-1898
Table of Contents
1. Introduction 3
2. Project Overview 3
2.1 Scope 3
2.1.1 Identification 3
2.1.2 System Overview 3
2.1.3 Document Overview 3
2.2 Current System or Situation 3
2.3 Background, Objectives, and Scope 3
2.4 Operational Policies and Constraints 3
2.5 Description of Current System or Situation 3
2.6 Users or Involved Personnel 4
2.7 Support Concept 4
3. Development Background/Approach 4
3.1 High Level Estimates 4
3.2 Key Contacts and Stakeholders 4
4. Features, Primary Deliverables, and External Commitments 4
4.1 Feature List 4
4.2 Customer Deliverables 4
5. Project Schedule 5
5.1 Major Project Milestones 5
5.2 Detailed Project Schedule 5
5.3 Project Status Tracking & Working Meeting Minutes 5
6. Project Work and Product Estimates 5
6.1 Estimate Summary 5
7. Project Resource Requirements 6
7.1 Staffing/ Skill Requirements 6
7.2 Plan to Fill Skill Gaps 6
8. Dependencies and Constraints 7
8.1 Constraints 7
9. Risk Management 7
9.1 Risk Management Strategy 7
9.2 Initial Risk List 7
9.2.1 Risk Details: 7
10. Project Configuration and Data Management 7
10.1 Configuration Management 7
11. Project Quality and Measurement Plans 7
12. Project Process 7
12.1 Software Life Cycle Model 7
13. Referenced Documents 8
14. Glossary 8
15. Change Record 8
1. Introduction
This Project Plan describes the scope, context, stakeholders, activities, resources, schedule, constraints, risks, quality goals, and processes. It is intended to provide a guide to how development work will be managed.
This section should provide a high level description of the project and product being developed (e.g. change counter).
2. Project Overview [1]
2.1 Scope
2.1.1 Identification
[This paragraph shall contain a full identification of the system and the software to which this document applies, including, as applicable, identification number(s), title(s), abbreviation(s), version number(s), and release number(s).]
2.1.2 System Overview
[This paragraph shall briefly state the purpose of the system and the software to which this document applies. It shall describe the general nature of the system and software; summarize the history of system development, operation, and maintenance; identify the project sponsor, acquirer, user, developer, and support agencies; identify current and planned operating sites; and list other relevant documents.]
2.1.3 Document Overview
[This paragraph shall summarize the purpose and contents of this document and shall describe any security or privacy considerations associated with its use.]
2.2 Current System or Situation
[This section shall be divided into the following paragraphs to describe the system or situation as it currently exists.]
2.3 Background, Objectives, and Scope
[This paragraph shall describe the background, mission or objectives, and scope of the current system or situation.]
2.4 Operational Policies and Constraints
[This paragraph shall describe any operational policies and constraints that apply to the current system or situation.]
2.5 Description of Current System or Situation
[This paragraph shall provide a description of the current system or situation, identifying differences associated with different states or modes of operation (for example, regular, maintenance, training, degraded, emergency, alternative-site, wartime, peacetime). The distinction between states and modes is arbitrary. A system may be described in terms of states only, modes only, states within modes, modes within states, or any other scheme that is useful. If the system operates without states or modes, this paragraph shall so state, without the need to create artificial distinctions. The description shall include, as applicable:
· The operational environment and its characteristics
· Major system components and the interconnections among these components
· Interfaces to external systems or procedures
· Capabilities/functions of the current system
· Charts and accompanying descriptions depicting inputs, outputs, data flow, and manual and automated processes sufficient to understand the current system or situation from the user’s point of view
· Performance characteristics, such as speed, throughput, volume, frequency
· Quality attributes, such as reliability, maintainability, availability, flexibility, portability, usability, efficiency
· Provisions for safety, security, privacy, and continuity of operations in emergencies]
2.6 Users or Involved Personnel
[This paragraph shall describe the types of users of the system, or personnel involved in the current situation, including, as applicable, organizational structures, training/skills, responsibilities, activities, and interactions with one another.]
2.7 Support Concept
[This paragraph shall provide an overview of the support concept for the current system, including, as applicable to this document, support agency(ies); facilities; equipment; support software; repair/replacement criteria; maintenance levels and cycles; and storage, distribution, and supply methods.]
3. Development Background/Approach
[Provide a high level description of the development activity including information such as the target platform, development environment, team characteristics, etc.]
3.1 High Level Estimates
[Provide high level estimates to accomplish each phase of the project including total effort, lines of code, pages of requirements & other development documentation, test cases and duration]
3.2 Key Contacts and Stakeholders
[Provide a list of the stakeholders and their roles. Include a description of the role, the responsible individual and their contact information (email & telephone)]
4. Features, Primary Deliverables, and External Commitments
4.1 Feature List
[Provide a list of the features committed for this release along with a brief description of each capability]
4.2 Customer Deliverables
[Provide a list of the final delivery dates along with a description of the contents of each delivery (e.g. user guide, install script)]
5. Project Schedule
5.1 Major Project Milestones
Date (YYYY-MM-DD) / Milestone/ Event / Entry Deliverable & Criteria / Exit / Notes /Project Plan Baselined / Inspection completed / In progress
5.2 Detailed Project Schedule
[Provide a pointer to the current project schedules]
5.3 Project Status Tracking & Working Meeting Minutes
[Description of information to be tracked during the regularly scheduled working meetings. Information could include attendees, discussion items, risks, issues, deliverable status & other metrics that are tracked on a regular basis]
6. Project Work and Product Estimates
Inputs to estimation include:
1) Deliverables listed in Section 4
2) Major Milestones listed in Section 5
3) Tasks and/or sub-tasks identified in the detailed project Schedule.
6.1 Estimate Summary
[Provide a pointer to the detailed estimates]
The tables below summarize the product size and effort estimates:
Project / Estimate AttributesSize
WBS areas / Unit of Size / Size / Effort
Total Requirements Effort
(includes feature-related and "other" (non-feature) Requirements work)
Feature Related Requirements Size and Effort Totals / PAGES
Total Development Effort
(includes feature-related and "other" (non-feature) Development work)
Feature Related Development Coding Size and Effort Totals / LOC
Feature Related Development Documentation Size and Effort / PAGES
Total Testing Effort
(includes feature-related and "other" (non-feature) Testing work)
Feature Related Testing Size and Effort Totals / TEST CASES
Feature Level Effort Total
(from Feature Estimate Worksheet)
Development Effort Total
(Includes Feature Level and project level overhead for Requirements, Development, and Testing)
Project Level Effort Total
(from Project Level Effort Estimates worksheet, excluding requirements, development, and testing)
Project Total Effort (Project Totals + Feature Totals)
7. Project Resource Requirements
7.1 Staffing/ Skill Requirements
Role: Team Leader
Critical Skills
[List key skills, experience & training required]
Skill Gaps: [list skill gaps]
Role: Development Manager
Critical Skills
Skill Gaps:
Role: Planning Manager
Critical Skills
Skill Gaps:
Role: Quality & Process Manager
Critical Skills
Skill Gaps:
Role: Support Manager
Critical Skills
Skill Gaps:
7.2 Plan to Fill Skill Gaps
[identify the specific activities to be undertaken to address skill gaps described above]
8. Dependencies and Constraints
8.1 Constraints
9. Risk Management
9.1 Risk Management Strategy
[Describe the team’s high level strategy for addressing the project risks]
9.2 Initial Risk List
This is the initial risk list; the risks are listed in priority order from top to bottom. Descriptions are provided below the table. Risks with a pre-mitigation magnitude of 2.0 or below are not listed.
Risknumber / Risk Priority (H, M, L) / Likelihood
of
Occurrence / Risk name: brief description / Mitigation Strategy
“ACCEPTED” or “MITIGATED” with pointer to plan. /
1
2
3
9.2.1 Risk Details:
[Risk details including description, likely consequences & mitigation strategy]
10. Project Configuration and Data Management
10.1 Configuration Management
[Describe the high level configuration management plan – e.g. tools, repository, process pointer]
11. Project Quality and Measurement Plans
[Describe the high level measurement plan, types of data being collected, who is collecting, objective of data collection]
12. Project Process
12.1 Software Life Cycle Model
[Describe the life cycle approach used including methodology & development tools]
13. Referenced Documents
[This section shall list the number, title, revision, and date of all documents referenced in this specification. This section shall also identify the source for all documents.]
14. Glossary
[List any acronyms or other terms where further description might be helpful to the reader]
15. Change Record
[This section provides a history of changes made to this Plan.
Include date changed, change request #, new issue #, description of changes, reason for changes & person who modified the document]
Page 2 of 8 Project_Plan_Template_v02.doc
[1] Note: this section is based on Professor Tepfenhart’s OCD template.