Implementing Software Development PM Best Practices
school_life15
table_4.4a.pdf
PRINTED BY: [email protected]. Printing is for personal, private use only. No part of this book may be reproduced or transmitted without publisher's prior permission. Violators will be prosecuted.
• a statement of the purpose and objectives of the project • identification of stakeholders and their objectives • software development model to be used • software development environment to be used • platform technology to be used • scope of work activities to be completed • schedule of work activities including periodic, objective milestones • skill levels and numbers of software personnel needed • when various numbers and kinds of software personnel will be needed • resources in addition to software personnel • a plan for periodically reporting project status • a risk management plan
As has been repeatedly emphasized, these elements of a project plan must be based on the development model to be used and scaled to the size and complexity of the project. Techniques for developing and documenting these elements of a project plan are presented in subsequent chapters.
The following sections of this chapter provide a template for and a description of the elements of a comprehensive plan-driven plan, an example of tailoring the template, and techniques for reducing the effort required to develop a software project management plan.
4.6 A TEMPLATE FOR SOFTWARE PROJECT MANAGEMENT PLANS In the absence of a standard format for project plans in your organization, the template presented in Tables 4.4a, b, and c can be used. This template is similar to the format for project plans specified in IEEE/EIA Standard 1058. The template is comprehensive and is intended for the largest and most complex projects. It can be, and should be, tailored to fit the needs of each project; an example of tailoring is presented later in this chapter. The lengthy template is presented in three tables for ease of presentation. The topics in the tables are discussed in numerous places throughout the text; the “Discussed In” column of each table indicates the chapters and sections where the primary discussion of each topic is presented.
TABLE 4.4A Template for a Software Project Management Plan (part 1)
Contents Discussed In
Front matter Section 4.4.1
Title Page
Revision History
PRINTED BY: [email protected]. Printing is for personal, private use only. No part of this book may be reproduced or transmitted without publisher's prior permission. Violators will be prosecuted.
Contents Discussed In
Preface
Table of Contents
List of Figures
List of Tables
Project summary Section 4.4.2
1. Project Summary
1.1 Purpose, Scope, and Objectives
1.2 Assumptions Section 4.4.2
1.3 Constraints
1.4 Project Deliverables Chapter 1
1.5 Schedule and Budget Summary
Evolution, references, definitions Section 4.4.3
2 Evolution of the Plan
3 References
4 Definitions
Project organization Section 4.4.4
PRINTED BY: [email protected]. Printing is for personal, private use only. No part of this book may be reproduced or transmitted without publisher's prior permission. Violators will be prosecuted.
Contents Discussed In
5. Project Organization
5.1 Project Interfaces
5.2 Project Structure Chapter 1
5.3 Roles and Responsibilities Chapter 8
TABLE 4.4B Template for a Software Project Management Plan (part 2)
Contents Discussed In
Contents Discussed In
Managerial processes Section 4.4.5
6. Managerial Processes
6.1 Start-up Plan
6.1.1 Project Estimation Chapter 6
6.1.2 Staffing Plan Chapter 5
6.1.3 Resource Acquisition Plan
6.1.4 Project Staff Training Plan
6.2 Work Plan
6.2.1 WBS and Work Packages Chapter 5
PRINTED BY: [email protected]. Printing is for personal, private use only. No part of this book may be reproduced or transmitted without publisher's prior permission. Violators will be prosecuted.
Contents Discussed In
6.2.2 Schedule Dependencies Chapter 5
6.2.3 Resource Allocation Chapter 5
6.2.4 Budget Allocation Chapter 5
6.3 Project Control Plan
6.3.1 Requirements Chapters 3 and 7
6.3.2 Schedule Chapter 8
6.3.3 Budget Chapter 8
6.3.4 Quality Chapter 7
6.3.5 Metrics Plan Chapter 8
6.3.6 Reporting Plan Chapters 7 and 8
6.4 Risk Management Plan Chapter 9
6.5 Closeout Plan
TABLE 4.4C Template for a Software Project Management Plan (part 3)
Contents Discussed In
Contents Discussed In
Technical processes Section 4.4.6
PRINTED BY: [email protected]. Printing is for personal, private use only. No part of this book may be reproduced or transmitted without publisher's prior permission. Violators will be prosecuted.
Contents Discussed In
7. Technical Processes
7.1 Development Process Model Chapter 2
7.2 Methods, Tools, and Techniques
7.3 Infrastructure Plan
7.4 Product Acceptance Plan
Supporting processes Section 4.4.7
8. Supporting Processes
8.1 Configuration Management Chapter 3
8.2 Verification and Validation Chapter 2
8.3 Documentation Chapter 1
8.4 Quality Assurance Chapter 1
8.5 Reviews and Audits Chapter 2
8.6 Problem Resolution Chapter 1
8.7 Subcontractor Management Chapter 1
8.8 Process Improvement
Additional plans, appendixes, index Section 4.4.8
PRINTED BY: [email protected]. Printing is for personal, private use only. No part of this book may be reproduced or transmitted without publisher's prior permission. Violators will be prosecuted.
Contents Discussed In
9. Additional Plans
Appendices
Index
An annotated version of the template is contained in Appendix 4B of this chapter. In the appendix a series of questions is posed to assist you in preparing your project plan. An on-line version of the template that provides an easy-to-use outline for preparing project plans can be obtained at the URL listed in the Preface to this text.
An overview of the various elements of the template is presented in the following sections.
4.6.1 Front Matter There are nine major sections in the template for software project management plans based on IEEE Standard 1058 plus the “front matter,” which includes a title
