Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /usr/www/users/playsn/pibold/wp-content/plugins/qtranslate-x/qtranslate_frontend.php on line 497
CMMI v1.3 — Changes « plays-in-business.com/pibold

CMMI v1.3 — Changes


Warning: Illegal string offset 'title' in /usr/www/users/playsn/pibold/wp-content/plugins/table-of-content/plugin.php on line 48

Warning: Cannot assign an empty string to a string offset in /usr/www/users/playsn/pibold/wp-content/plugins/table-of-content/plugin.php on line 48

Warning: Illegal string offset 'title-tag' in /usr/www/users/playsn/pibold/wp-content/plugins/table-of-content/plugin.php on line 50

Warning: Illegal string offset 'title-tag' in /usr/www/users/playsn/pibold/wp-content/plugins/table-of-content/plugin.php on line 52

Warning: DOMDocument::loadXML(): Opening and ending tag mismatch: hr line 5 and body in Entity, line: 6 in /usr/www/users/playsn/pibold/wp-content/plugins/wordpress-amazon-associate/APaPi/AmazonProduct/Result.php on line 149

Warning: DOMDocument::loadXML(): Opening and ending tag mismatch: body line 5 and html in Entity, line: 7 in /usr/www/users/playsn/pibold/wp-content/plugins/wordpress-amazon-associate/APaPi/AmazonProduct/Result.php on line 149

Warning: DOMDocument::loadXML(): EndTag: '</' not found in Entity, line: 8 in /usr/www/users/playsn/pibold/wp-content/plugins/wordpress-amazon-associate/APaPi/AmazonProduct/Result.php on line 149

Warning: Invalid argument supplied for foreach() in /usr/www/users/playsn/pibold/wp-content/plugins/wordpress-amazon-associate/APaPi/AmazonProduct/Result.php on line 160

Warning: DOMDocument::loadXML(): Opening and ending tag mismatch: hr line 5 and body in Entity, line: 6 in /usr/www/users/playsn/pibold/wp-content/plugins/wordpress-amazon-associate/APaPi/AmazonProduct/Result.php on line 149

Warning: DOMDocument::loadXML(): Opening and ending tag mismatch: body line 5 and html in Entity, line: 7 in /usr/www/users/playsn/pibold/wp-content/plugins/wordpress-amazon-associate/APaPi/AmazonProduct/Result.php on line 149

Warning: DOMDocument::loadXML(): EndTag: '</' not found in Entity, line: 8 in /usr/www/users/playsn/pibold/wp-content/plugins/wordpress-amazon-associate/APaPi/AmazonProduct/Result.php on line 149

Warning: Invalid argument supplied for foreach() in /usr/www/users/playsn/pibold/wp-content/plugins/wordpress-amazon-associate/APaPi/AmazonProduct/Result.php on line 160

Changes in CMMI v1.3 that affect all Constellations
[Top]

The SEI introduced concepts of the “CMMI Model Foundation” (CMF) and the “constellation” in CMMI v1.2. However, the constellations were developed and released with different schedules resulting in inconsistencies among their components. CMMI v1.3 strives to eliminate those inconsistencies and harmonize the components resulting in the simultaneous release of all three constellations: CMMI for Development (CMMI-DE)V, CMMI for Acquisition (CMMI-ACQ) and CMMI for Services (CMMI-SVC).

CMF refers to the set of sixteen core process areas that are common to all CMMI models. In addition to the CMF process areas there are  so called  shared PAs. These PAs are not common to all models rather a few. Today  there is only one shared PA: the Supplier Agreement Management (SAM) shared by CMMI-DEV and CMMI-SVC.

Because of the very specific nature of some constellations, the terminology used in those constellations was refined in v1.3 affecting most of the informative material and in some cases names of Process Areas (PA), as well as the names of Specific Goals (SG) and Specific Practices (SP).
One such term was the word “project” that was used in all three v1.2 CMMI models. However, for the service providers this term posed difficulties to interpret and in CMMI-SVC v1.3 it was changed to “work”. That resulted in changing the PA names such as Work Planning, Work Management and Control, Integrated Work Management. In addition, some work product names were also changed such as “work plan” for “project plan”, “managing work” vs. “managing project.”
Even though the PA names changed those PAs are still considered core process areas.

Architectural changes
[Top]

  • Many editorial (textual) changes that enable better understanding and easier reading of the model material were introduced.
  • Glossary was updated and harmonized with the model text.
  • All Generic Goals (GG) and Generic Practices (GP) are moved to Part Two thus reducing the size of the document. In v1.2 they were located with the Specific Goals (SG) and Specific Practices (SP) in each Process Area.
  • Clarified the use of GP 2.8, Monitor the Process. The informative material now emphasizes “evaluation of actual progress” instead of “measuring the actual progress and performance against the plan for performing the process.”
  • Rewrote description of GP 3.2 to make it easier to interpret. It now reads: “Collect process-related experiences derived from planning and performing the to support the future use and improvement of the organization’s processes and process assets.”
  • Generic Goals 4 and 5 and associated Generic Practices are eliminated (the impact of that change on the capability level rating is discussed below).
  • “Typical work products” were renamed “Example work products” and were modified to make them broader and more recognizable.
  • Two Specific Practices replace Integrated Product and Process Development (IPPD) “additions” (Specific Goals and related SPs): one in the Organizational Process Definition (OPD) (SP 1.7, Establish Rules and Guidelines for Teams) and one in the Integrated Project Management (IPM) (SP 1.6, Establish Teams).
  • Removed model “amplification” component (e.g., “For Software Engineering” or “For System Engineering”).
  • High maturity PAs (OPP, QPM, OPM, and CAR) were rewritten (see below).
  • Requirements Management (REQM) PA was moved from the Engineering Process category to Project Management category but without other major changes.
  • Added section “Interpreting CMMI When Using Agile Approaches” in “Using CMMI Models”, Part I, CMMI-DEV. Added guidance to appropriate PAs helping users interpret practices in a context where agile methods are used:
    • In DEV: CM, REQM, PP, RD, TS, PI, VER, PPQA, and RSKM
    • In SVC: SSD
    • Added Agile related examples (as bullets)
  • In some PAs, informative material has new discussion about customer satisfaction (e.g., measurements and examples); customer satisfaction was not addressed in v1.2.
    • In DEV: MA, OPF, PMC, and RD
    • In SVC: MA

Changes introduced into CMMI for Development, v1.3
[Top]

  • There are no model “addition” components in the model. They have been removed.
  • Added new subpractices in several PAs to help improve understanding of the associated Specific Practices.
  • In the PAs RD, TS, PI, VER, informative material was revised and modern engineering concepts were introduced (e.g., quality attributes [“ilities”], product lines, system of systems, architecture-centric practices, allocation of product capabilities to release increments, technology maturation).
  • In the Supplier Agreement Management (SAM) PA, two SPs found in v1.2 (SP 2.2, Monitor Selected Supplier Processes and SP 2.3, Monitor Selected Supplier Work Products) were demoted to subpractices of SP 2.1, Execute the Supplier Agreement.

Changes to High Maturity PAs
[Top]

One of the goals for v1.3 was to eliminate deficiencies in the existing model. This was especially critical for the High Maturity PAs. The biggest problem for those PAs was that the high maturity requirements were implied defined in the model but  lead appraisers rely on explicite material published outside the model by organizations as  proof of evidence.

  • Terminology (in the model and Glossary) was revised and clarified.
  • Added extensive informative material.
  • Organizational Process Performance (OPP)
    • Moved/reordered SP 1.3, Establish Quality and Process-Performance Objectives, in v1.2 to become SP 1.1 in v1.3.
    • Rewrote SP 1.4 to read “Analyze Process Performance and Establish Process-Performance Baselines.”
  • Quantitative Project Management (QPM)
    • Restructured SGs so that SG 1 focuses on preparation and SG 2 on managing.
    • Added new SP 2.3, Perform Root Cause Analysis.
    • Deleted SP 2.2, Apply Statistical Methods to Understand Variation, to minimize over-reliance on control charts.
    • Deleted SP 2.4, Record Statistical Management Data.
  • Causal Analysis and Resolution (CAR)
    • Changed terminology to also include positive “outcomes” instead of limiting it to “defects and other problems”.
    • Added more information for how Process-Performance Models can be used and how to proactively address defect prevention.
  • Organizational Performance Management (OPM)
    • Expanded and renamed the former Organization Innovation and Deployment (OID) PA to include performance management. This enables better focus on performance of organizational processes as they relate to business objectives.
      • Created new goal SG 1, Manage Business Performance, that emphasizes using statistical and other quantitative techniques when managing business performance.
        This goal has three new SPs: SP 1.1, Maintain Business Objectives, SP 1.2, Analyze Process-Performance Data, and SP 1.3, Identify Potential Areas for Improvement.
      • Rewrote what used to be SG 1 in v1.2. In v1.3 it is SG 2, Select Improvements.
        • Deleted former SP 1.1 and SP 1.2.
        • Created three new SPs: SP 2.1, Elicit Suggested Improvements; SP 2.2, Analyze Suggested Improvements; and SP 2.3, Validate Improvements (and piloting is just one possible validation technique).
    • Generic Goals 4 and 5 were deleted and the concept of Capability Level 4 and 5 eliminated. The following explains how to attain high maturity when using continuous representation:
      • When using the continuous representation, to attain high maturity, one must use the equivalent staging concept.
      • High maturity that is equivalent to staged Maturity Level 4 using equivalent staging is attained when one achieves Capability Level 3 for all process areas in the model except for Organizational Performance Management (OPM) and Causal Analysis and Resolution (CAR).
      • High maturity that is equivalent to staged Maturity Level 5 using equivalent staging is attained when one achieves Capability Level 3 for all process areas.

Changes introduced into CMMI for Services v1.3
[Top]

  • No substantial changes beyond harmonization and those described in CMMI-DEV were made to the following core PAs, DAR, MA, OPD, OPF, OT, PPQA.
  • No substantial changes beyond harmonization and those described in CMMI-DEV were made to the shared PA, SAM.
  • No substantial changes were made to the SCON, SD, STSM SVC PAs.
  • Some additional changes were introduced into the following core PAs.
    • CM — additional examples of work products to be placed under CM
    • IPM — renamed this PA to be Integrated Work Management (IWM) and made changes in the informative material
    • PMC — renamed this PA to be Work Monitoring and Control (WMC), however, no substantive changes were made
    • PP — renamed this PA to be Work Planning (WP) and made changes in the informative material
    • REQM — made changes in the informative material
    • RSKM — made changes in the informative material
  • Some additional changes were introduced into the following SVC PAs
    • CAM — provided guidance relating CAM to quality attributes
    • IRP — restructured SG 2 (addresses timely management of individual incidents) and SG 3 (addresses defining approaches to reducing impacts of future incidents); revised informative material
  • In the following PAs informative material was revised and modern engineering concepts were introduced (e.g., terms: quality attribute [“ilities”], product lines, system of systems, architecture-centric practices, allocation of product capabilities to release increments, technology maturation)
    • SSD
    • SST — changes are limited to the term “quality attributes” only
  • In High Maturity PAs added service-related examples

Further Readings
[Top]


Warning: count(): Parameter must be an array or an object that implements Countable in /usr/www/users/playsn/pibold/wp-includes/class-wp-comment-query.php on line 405

Leave a Reply

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>