Comparison of Configuration Management Activities Between Prince 2 & CMMI 1.1

Assets of the project are the products that are developed & managed. Configuration is the combined set of these assets. Configuration of final release of a project is the sum total of its products. Configuration management (CM) is not optional: it may be thought of an asset or product control & also plays a major role in quality control. CM is normally seen as the support activity to project management. Both capability maturity model integration (CMMI) version 1.1, developed by the Software Engineering Institute, and the project in controlled environment (PRINCE) version 2 developed by Central Computing & Telecommunications Agency [now Office of Government Commerce], emphasizes on proper execution of configuration control activities. These two are driven by similar concerns and intuitively correlated. Organizations concerned with PRINCE 2 certification often question its overlap with other standard(s). I had looked into OGC PRINCE 2 Configuration Management Component and map it to the CM process in continuous representation - support process area, SEI CMMI 1.1. Analysis provides answers to some common questions about the comparison of these two; in the vital domain of Configuration Management (Identify, Track, Protect the products). In order to achieve good transformation there is a need of applying appropriate software metrics based upon leading case studies across the globe & information elicited from the answers of questionnaires. These metrics needs to be implemented on each and every sub-process/typical artifacts and sub-practice/work products