Each project by default is initially at CMM level 1. The basic requirement for CMM level 2 is Effective Requirement Management, Project Planning, monitoring and control, Quality assurance. All these steps are explained later from a typical software project point of view.
The main steps for proper requirement management are as follows:
The first Step towards Requirement Management is to have a signed off Project Authorization document which can be also work as a statement of work (SOW). This should be stored and archived.
Project Scope should be clearly defined and documented.
Requirements should be baselined. And should state the in scope and out of scope requirements properly.
Requirement Change Management – Any change in requirements should be tracked to ensure that the change is propagated till the last stage of software life cycle
The main steps for proper project planning are as follows:
The project needs to start with an official Kick-Off meeting. The Minutes of this meeting need to be captured and stored.
Project Management Plan should be updated, approved by higher management and basedlined after the review process.
Study the Configurable and Non-Configurable Items for the project and draft a Configuration Management Planand get this approved from the Quality team.
Estimationshould be done for Effort, Cost and Defects and shared with the client.
The Quality Management plan should be designed. This will include designing the strategies for Quality and Productivity Metrics and defect Prevention Guidelines.
Project Monitoring and Control
The main steps for proper Project Monitoring and Control are as follows:
All data should be properly captured and tracked to monitor the project properly.
Status of project should be reviewed after constant interval and the status should be recorded for monitoring purpose.
Milestone Reports should be submitted in regular intervals to higher management.
Process and Software Quality Assurance
The main steps for proper Process and Software Quality Assurance and Control are as follows:
Quality audits should be performed regularly.
Each project should have the Configuration Management Audits planned once in 2 months.
All Deliverables should undergo a review and the review defects should be captured properly.