Software process definition, documentation, and improvement should be an integral part of every software engineering organization. This ReadyNote addresses the specific documentation requirements in support of the CMMI-SW Project Planning process area, providing
- detailed organizational policy examples,
- deployable Project Planning templates, and
- examples of common Project Planning work products required to support CMMI Level 2 assessment activities.
It describes the documentation required for the CMMI Project Planning activities associated with Level 2 software development projects. The goal is to provide practical support for individuals responsible for the development and documentation of software processes and procedures. These individuals are responsible for
- software project management,
- software process improvement or gap analysis (for example, software process owners, team members tasked with process definition and improvement, and engineers), and
- CMM/CMMI-SW implementation (for example, software engineering process group members, and software quality assessors).
The CMMI is descriptive: It does not tell users how to satisfy the criteria for their key process areas, nor does it show how to accomplish their goals. Instead, it describes the criteria that the implementation should support. IEEE standards are prescriptive: They describe how to fulfill the requirements associated with effective software project management.
This ReadyNote should be used as a best-practices supplement to the SEI CMMI and the IEEE Software Engineering Standards set. It provides the link between the “what” and the “how to” of software process improvement leading to certification. For organizations that do not wish to pursue CMMI Level 2 accreditation, this document will show how the application of IEEE Standards, and their use as reference material, can facilitate the development of sound software engineering practices.
CHAPTER 1: INTRODUCTION
What is the CMMI?
What the CMMI is Not
What are Standards?
CHAPTER 2: SUMMARY OF CMMI-SW
THE CMM-SW
CMMI-SW Continuous vs. Staged
Structural Elements of the CMMI-SW
PROCESS AREAS
Specific and Generic Goals
Specific and Generic Practices
CMMI-SW Common Features
CMMI-SW Components
GENERIC PRACTICES
CMMI-SW Level 2 Generic Practices
CHAPTER 3: CMMI-SW LEVEL 2 PROJECT PLANNING SUPPORT
PROJECT PLANNING
CMMI-SW Goals
IEEE / CMMI-SW (Staged) Project Planning Matrix
PROJECT PLANNING ANALYSIS
SOFTWARE PROJECT MANAGEMENT PLAN
Data Management
Stakeholder Involvement
CHAPTER 4: LEVEL 2 CMMI FOR SMALL PROJECTS
INTRODUCTION TO CMMI AND SMALL PROJECTS
PROJECT MANAGEMENT PLAN ý SMALL PROJECTS
APPENDIX A / PROJECT MANAGEMENT PLAN TEMPLATE
Project Overview
Project Deliverables
Document Overview
ACRONYMS AND DEFINITIONS
Acronyms
Definitions
REFERENCES
PROJECT ORGANIZATION
Organizational Policies
Process Model
Organizational Structure
Organizational Boundaries and Interfaces
Project Responsibilities
MANAGERIAL PROCESS
Management Objectives and Priorities
Assumptions, Dependencies, and Constraints
Risk Management
Monitoring and Controlling Mechanisms
Staffing Plan
TECHNICAL PROCESS
Tools, Techniques, and Methods
Software Documentation
Project Support Functions
WORK PACKAGES
Work Packages
Dependencies
Resource Requirements
Budget and Resource Allocation
Schedule
ADDITIONAL COMPONENTS
APPENDIX B / SOFTWARE PROCESS WORK PRODUCTS
PROJECT PLANNING
Organizational Policy Examples
Probability/Impact Risk Rating Matrix
Project Schedule
Risk Action Request
Risk Mitigation Plan
Risk Matrix Sample
Software Reviews [2]
Work Breakdown Structure
Workflow Diagram
Stakeholder Involvement Matrix
APPENDIX C / COMPARISON OF CMMI-SW LEVELS 2 & 3 TO IEEE STANDARDS
APPENDIX D / IEEE STANDARDS ABSTRACTS
REFERENCES
IEEE PUBLICATIONS
SEI PUBLICATIONS
OTHER REFERENCES