tag:blogger.com,1999:blog-5843108629504158226.post6114637007886343109..comments2023-09-04T05:47:50.471-07:00Comments on PPQC Blog: Frequency for REQM SP 1.5Henry Schneiderhttp://www.blogger.com/profile/12588884323537313318noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5843108629504158226.post-24769710727780840372008-07-29T14:49:00.000-07:002008-07-29T14:49:00.000-07:00Hi Allen,Since REQM is a special instance of CM, y...Hi Allen,<BR/>Since REQM is a special instance of CM, you might think that there is some overlap between these two practices, but there really isn't any. The SEI has made a lot of effort over the years to clean up the model and remove redundancies. There was a major improvement to the CMMI with v1.2.<BR/>REQM SP 1.5 is about looking at all of the different plans, work products, and requirements and taking steps to identify inconsistencies between them that will develop over time as requirements etc. evolve. All of these items are in the baseline, but the Configuration Audits of CM SP 3.2 are not for determining if there are any inconsistencies between configuration items. The intent of a Configuration Audit is to provide an objective way of knowing that what is supposed to be controlled is in fact controlled and can be retrieved as needed. Retrieval of accurate information is one on CM's many benefits. A Configuration Audit most likely will not identify inconsistencies between configuration items, just the right items are resident in the repository.Henry Schneiderhttps://www.blogger.com/profile/12588884323537313318noreply@blogger.comtag:blogger.com,1999:blog-5843108629504158226.post-20907371590379880182008-07-28T14:00:00.000-07:002008-07-28T14:00:00.000-07:00Isn't REQM SP 1.5 a duplicate of CM SP 3.2, "perfo...Isn't REQM SP 1.5 a duplicate of CM SP 3.2, "perform configuration audits?" Everytime you update your configuration baseline, you should perform a configuration audit to ensure that what is there is supposed to be there. REQM SP 1.5 seems to be saying the same thing.Anonymousnoreply@blogger.com