Maximizing Business Results with CMMI Maturity Models: Lessons Learned and Recommendations

CMMI, or Capability Maturity Model Integration, is a set of maturity models developed by ISACA to help organizations assess and improve their capabilities and performance in various areas. Originally designed for the U.S. Department of Defense to evaluate software contractors, CMMI has evolved to cover a range of industries and business functions. By using CMMI, organizations can gain insight into their current level of maturity and identify areas for improvement, ultimately leading to better business results.

Trends

• CMMi has been widely applied in the United States and China over the past three years (71.8% of which occurred in China).
• Organizations with less than 100 employees account for 88%.
• It is widely used in government agencies, defense, and manufacturing companies.
• IT is the most commonly used field.
• It is widely used in areas such as quality, productivity, customer satisfaction, and cost savings.

In my experience, for a project to end successfully, not only the project manager but also the developers and stakeholders need to pay close attention to software quality management. Although it may be difficult to reach CMMi level 5, I believe that the excellent software quality management standard that most companies aim for starts from level 3.

I would like to share a real case where I received feedback during a CMMi assessment meeting regarding common mistakes made by project participants in project management.

Although these are theoretically well-known, they are often not well followed in practice. Therefore, it is essential to always be aware of these factors in project management.

Things we're not doing well

• Efforts are needed for quality activities at an enterprise level even for small projects (with a budget of less than 1 billion).
• There is a lack of application of standard processes, and the application of standard templates is insufficient.
• The use of PMS/EDMS/business management systems is not being utilized.
• There is a difference between the standard templates provided to the enterprise methodology by reusing business deliverables and some items.
• Standard templates, such as requirements definition documents, are not being applied.
• The definition of pre- and post-activities is not clear in the WBS (weak critical path).
• The project Lessons Learned quality inspection checklist is not being fully added.
• The process of analyzing the results of peer review activities and sharing them with QA is weak.

Improvement Suggestions

• Regular organization-wide analysis of project performance data is needed.
• Project performance assets need to be reduced and stored in EDMS.
• Business deliverables need to be reused to reduce management time leads.
• Analysis of peer review activities and active collaboration with QA is needed.

To conclude, it is essential to prioritize clear communication, proper change management, regular code reviews and testing, and thorough documentation throughout the software development process. These measures can help ensure timely project delivery, high-quality software, and ease of future maintenance and updates.

By Jake Park(jake.kbpark@gmail.com) / IT Project Manager

#SDLC #Software Development #CMMi #Capability Maturity Model Integration #Inspection #Project Management #Project Manager