CMM Configuration Management and Project Management

Configuration Management is a discipline that is unique to the business of developing software so is not specifically addressed anywhere in the PMBOK PMP certification . The purpose of this article is to offer suggestions on how this discipline can be incorporated into your project management plans for a software development project with the least amount of disruption.

Although none of the elements of configuration management are directly addressed in the PMBOK you’ll find that developing a software application of any size is impossible without some elements of configuration management. The source library used to version and release the software is a good example. CMM also specifies that the purpose of configuration management is to maintain the integrity of the software throughout the project’s software life cycle.

Beyond helping in the CMM/CMMI certification process, adhering to the criteria set for level 2 certification in the area of configuration management will not only benefit your software project but will also benefit future projects and help the support organization maintain the software products produced. The areas discussed in this series previously (requirements management, project planning.

project tracking and oversight, subcontract management, and quality assurance) all align with some knowledge area from the PMBOK so compliance with those criteria should not add significantly to the project scope. The activities required to comply with CMM/CMMI criteria in this area might add significant overhead to your project. You should compare the needs of the project for configuration management work against the work required to meet CMM/CMMI level 2 criteria, identify the work and tools required to address the delta and ensure that your project is adequately funded and resourced to undertake the additional work.

Leave a Reply

Your email address will not be published.