Difference between revisions of "Enterprise IT Maturity Assessments"

From EITBOK
Jump to: navigation, search
 
(11 intermediate revisions by 3 users not shown)
Line 1: Line 1:
−
 
+
<table border="3">
−
<p>Capability maturity for EIT refers to IT's ability to reliably perform. Maturity is a measured by an organization’s readiness and capability expressed through its people, processes, data and technologies and the consistent measurement practices that are in place. The organization’s maturity directly relates to the ability to execute the IT strategy; therefore, there is a need to assess maturity as an input to a realistic plan and as a guide to maturing IT to desired levels. In other words, unless the IT organization "knows itself," it can’t make plans to do more or to improve. Adoption of “lessons learned” is a key improvement strategy. Mature EIT organizations collect “lessons learned” during each project as it is executing and build the results into organizational improvements on a regular basis. When reviewed and areas prioritized by management, a maturity assessment is an input to the EIT strategy formulation, since its results may highlight its performance constraints.</p>
+
<tr><td>
−
 
+
<table>
 +
<tr>
 +
<td width="60%"><font color="#246196">'''Welcome to the initial version of the EITBOK wiki. Like all wikis, it is a work in progress and may contain errors. We welcome feedback, edits, and real-world examples. [[Main_Page#How to Make Comments and Suggestions|Click here]] for instructions about how to send us feedback.''' </font></td>
 +
<td width="20%">[[File:Ieee logo 1.png|100px|center]]</td>
 +
<td width="20%">[[File:Acm_logo_3.png|175px|center]]</td></tr></table>
 +
</td></tr></table>
 +
<p>&nbsp;</p>
 +
<h2>What Is a Maturity Assessment</h2>
 +
<p>Capability maturity for EIT refers to EIT's ability to reliably perform. Maturity is measured by an organization's readiness and capability expressed through its people, processes, data, and technologies and the consistent measurement practices that are in place. The organization's maturity directly relates to the ability to execute the EIT strategy; therefore, there is a need to assess maturity as an input to a realistic plan and as a guide to maturing EIT to desired levels. In other words, unless the EIT organization "knows itself," it can't make plans to do more or to improve. Adoption of "lessons learned" is a key improvement strategy. Mature EIT organizations collect lessons learned during each project as it is executing and build the results into organizational improvements on a regular basis. When reviewed and areas prioritized by management, a maturity assessment is an input to the EIT strategy formulation, because its results may highlight its performance constraints.</p>
 
<p>Maturity assessment involves scoring the organization against defined criteria and a ranking scheme. This assessment is generally organized in ascending steps with strategies on how to move up the maturity scale. Scales are often defined in a 1–5 range that indicates increasing levels of maturity. Some schemes allow for scoring that includes decimal points (such as 2.5). A common scheme defines the five levels in the following way:</p>
 
<p>Maturity assessment involves scoring the organization against defined criteria and a ranking scheme. This assessment is generally organized in ascending steps with strategies on how to move up the maturity scale. Scales are often defined in a 1–5 range that indicates increasing levels of maturity. Some schemes allow for scoring that includes decimal points (such as 2.5). A common scheme defines the five levels in the following way:</p>
 
<ol>
 
<ol>
−
<li>'''Performed:''' Activities are performed in an ad hoc manner.</li>
+
<li>'''Performed'''—Activities are performed in an ad hoc manner.</li>
−
<li>'''Managed:''' Activities are performed with managed processes.</li>
+
<li>'''Managed'''—Activities are performed with managed processes.</li>
−
<li>'''Defined:''' Activities are defined so the organization can performed them in a uniformed manner.</li>
+
<li>'''Defined'''—Activities are defined so the organization can perform them in a uniform manner.</li>
−
<li>'''Measured:''' Oversight is given to the performed activities to ensure performance and uniformity.</li>
+
<li>'''Measured'''—Oversight is given to the performed activities to ensure performance and uniformity.</li>
−
<li>'''Optimized:''' Continuous improvement processes are in place on the defined and measured processes.</li>
+
<li>'''Optimized'''—Continuous improvement processes are in place on the defined and measured processes.</li>
 
</ol>
 
</ol>
−
 
+
<p>A typical description of organizational maturity was developed by Stanford's SLAC National Accelerator Laboratory, as shown in the table below.</p>
−
A typical description of organizational maturity was developed by Stanford’s SLAC National Accelerator Laboratory, as shown in the table below:
+
<table cellpadding="5" border="1">
−
 
+
<tr>
−
<table border="1">
+
<th style="background-color: #58ACFA;"><font color="white">Skill</font></th>
−
<tr><th width="10%">&nbsp;</th>
+
<th width="18%" style="background-color: #58ACFA;"><font color="white">Level 1<br />Performed</font></th>
−
<th width="18%">Level 1<br />
+
<th width="18%" style="background-color: #58ACFA;"><font color="white">Level 2<br />Managed</font></th>
−
Performed</th>
+
<th width="18%" style="background-color: #58ACFA;"><font color="white">Level 3<br />Established</font></th>
−
<th width="18%">Level 2<br />
+
<th width="18%" style="background-color: #58ACFA;"><font color="white">Level 4<br />Predictable</font></th>
−
Managed</th>
+
<th width="18%" style="background-color: #58ACFA;"><font color="white">Level 5<br />Optimizing</font></th></tr>
−
<th width="18%">Level 3<br />
+
<tr valign="top"><td><strong>People</strong></td>
−
Established</th>
+
<td valign="top"><ul><li>Success depends on individual heroics</li>
−
<th width="18%">Level 4<br />
+
<li>"Fire fighting" is a way of life</li>
−
Predictable</th>
+
<li>Relationships between disciplines are uncoordinated, perhaps even adversarial</li></ul></td>
−
<th width="18%">Level 5<br />
+
<td valign="top"><ul><li>Success depends on individuals and management system supports</li>
−
Optimizing</th></tr>
+
<li>Commitments are understood and managed</li>
−
 
+
<li>People are trained</li></ul></td>
−
<tr><td valign="top"><strong>People</strong></td>
+
<td valign="top"><ul><li>Project groups work together, perhaps as an integrated product team</li>
−
<td valign="top"><ul><li>Success depends on individual heroics.</li>
+
<li>Training is planned and provided according to roles</li></ul></td>
−
<li>“Fire fighting" is a way of life.</li>
+
<td valign="top"><ul><li>A strong sense of teamwork exists within each project</li></ul></td>
−
<li>Relationships between disciplines are uncoordinated, perhaps even adversarial.</li></ul></td>
+
<td valign="top"><ul><li>A strong sense of teamwork exists across the organization</li>
−
<td valign="top"><ul><li>Success depends on individuals and management system supports.</li>
+
<li>Everyone is involved in process improvement</li></ul></td></tr>
−
<li>Commitments are understood and managed.</li>
+
<tr valign="top"><td><strong>Process</strong></td>
−
<li>People are trained.</li></ul></td>
+
<td valign="top"><ul><li>Few stable processes exist or are used</li></ul></td>
−
<td valign="top"><ul><li>Project groups work together, perhaps as an integrated product team.</li>
+
<td valign="top"><ul><li>Documented and stable estimating, planning, and commitment processes are at the project level</li></ul></td>
−
<li>Training is planned and provided according to roles.</li></ul></td>
+
<td valign="top"><ul><li>Integrated management and engineering processes are used across the organization</li></ul></td>
−
<td valign="top"><ul><li>A strong sense of teamwork exists within each project.</li></ul></td>
+
<td valign="top"><ul><li>Processes are quantitatively understood and stabilized</li></ul></td>
−
<td valign="top"><ul><li>A strong sense of teamwork exists across the organization.
+
<td valign="top"><ul><li>Processes are continuously and systematically improved</li></ul></td></tr>
−
Everyone is involved in process improvement.</li></ul></td>
+
<tr valign="top"><td><strong>Technology</strong></td>
−
</tr>
+
<td valign="top"><ul><li>The introduction of new technology is risky</li></ul></td>
−
 
+
<td valign="top"><ul><li>Technology supports established, stable activities</li></ul></td>
−
<tr><td valign="top"><strong>Process</strong></td>
+
<td valign="top"><ul><li>New technologies are evaluated on a qualitative basis</li></ul></td>
−
<td valign="top"><ul><li>Few stable processes exist or are used.</li></ul></td>
+
<td valign="top"><ul><li>New technologies are evaluated on a quantitative basis</li></ul></td>
−
<td valign="top"><ul><li>Documented and stable estimating, planning, and commitment processes are at the project level.</li></ul></td>
+
<td valign="top"><ul><li>New technologies are proactively pursued and deployed</li></ul></td></tr>
−
<td valign="top"><ul><li>Integrated management and engineering processes are used across the organization.</li></ul></td>
+
<tr valign="top"><td><strong>Measurement</strong></td>
−
<td valign="top"><ul><li>Processes are quantitatively understood and stabilized.</li></ul></td>
+
<td valign="top"><ul><li>Data collection and analysis are ad hoc</li></ul></td>
−
<td valign="top"><ul><li>Processes are continuously and systematically improved.</li></ul></td>
+
<td valign="top"><ul><li>Planning and management data is used by individual projects</li></ul></td>
−
</tr>
+
<td valign="top"><ul><li>Data is collected and used in all defined processes</li>
−
 
+
<li>Data is systematically shared across projects</li></ul></td>
−
<tr><td valign="top"><strong>Technology</strong></td>
+
−
<td valign="top"><ul><li>The introduction of new technology is risky.</li></ul></td>
+
−
<td valign="top"><ul><li>Technology supports established, stable activities.</li></ul></td>
+
−
<td valign="top"><ul><li>New technologies are evaluated on a qualitative basis.</li></ul></td>
+
−
<td valign="top"><ul><li>New technologies are evaluated on a quantitative basis.</li></ul></td>
+
−
<td valign="top"><ul><li>New technologies are proactively pursued and deployed.</li></ul></td>
+
−
</tr>
+
−
 
+
−
<tr><td valign="top"><strong>Measurement</strong></td>
+
−
<td valign="top"><ul><li>Data collection and analysis are ad hoc.</li></ul></td>
+
−
<td valign="top"><ul><li>Planning and management data is used by individual projects.</li></ul></td>
+
−
<td valign="top"><ul><li>Data is collected and used in all defined processes.</li>
+
−
      <li>Data is systematically shared across projects.</li></ul></td>
+
 
<td valign="top"><ul><li>Data definition and collection are standardized across the organization</li>
 
<td valign="top"><ul><li>Data definition and collection are standardized across the organization</li>
−
      <li>Data is used to understand the process qualitatively and stabilize it.</li></ul></td>
+
<li>Data is used to understand the process qualitatively and stabilize it</li></ul></td>
−
<td valign="top"><ul><li>Data is used to evaluate and select process improvements.</li></ul></td>
+
<td valign="top"><ul><li>Data is used to evaluate and select process improvements</li></ul></td></tr>
−
</tr>
+
 
</table>
 
</table>
−
 
 
<p>Periodic reassessments are performed to gauge progress against the baseline assessment and prior periods. Adjustments to the efforts to maintain and improve maturity can then be made against possible strategic priority changes, governance initiatives, and roadmap resets. </p>
 
<p>Periodic reassessments are performed to gauge progress against the baseline assessment and prior periods. Adjustments to the efforts to maintain and improve maturity can then be made against possible strategic priority changes, governance initiatives, and roadmap resets. </p>
−
 
+
<p>Maturity assessments on internationally recognized frameworks generally involve external auditors with certification and recertification requirements. Engagement in the maturity assessment and improvement process requires a minimum level of organization self-awareness to the issues and commitment to the improvements necessary. A cultural readiness, resistance, and capability assessment may be built into a maturity assessment. The set of standards centered round ISO/IEC 33001 attempt to provide an overall general structure for process assessment related to software development. </p>
−
<p>Maturity assessments on internationally recognized frameworks generally involve external auditors with certification and recertification requirements. Engagement in the maturity assessment and improvement process requires a minimum level of organization self-awareness to the issues and commitment to the improvements necessary. A cultural readiness, resistance, and capability assessment may be built into a maturity assessment. </p>
+
−
 
+
 
<h3>Capability Maturity Model Integration (CMMI)</h3>
 
<h3>Capability Maturity Model Integration (CMMI)</h3>
−
<p>[http://eitbokwiki.org/Glossary#cmmi Capability Maturity Model Integration (CMMI)]&nbsp;[[#Eighteen|[18]]] is a standard reference model for process improvement with cross-sector applicability with special focuses:</p>
+
<p>[http://eitbokwiki.org/Glossary#cmmi Capability Maturity Model Integration (CMMI)]&nbsp;[[#F_One|[1]]] is a standard reference model for process improvement with cross-sector applicability with special focuses:</p>
 
<ol>
 
<ol>
−
<li>Product and service development &mdash; [http://eitbokwiki.org/Glossary#cmmi_dev CMMI for Development (CMMI-DEV)]</li>
+
<li>Product and service development—[http://eitbokwiki.org/Glossary#cmmi_dev CMMI for Development (CMMI-DEV)]</li>
−
<li>Service establishment, management, &mdash; [http://eitbokwiki.org/Glossary#cmmi_svc CMMI for Services (CMMI-SVC)]</li>
+
<li>Service establishment, management—[http://eitbokwiki.org/Glossary#cmmi_svc CMMI for Services (CMMI-SVC)]</li>
−
<li>Product and service [http://eitbokwiki.org/Glossary#acquisition acquisition] &mdash; [http://eitbokwiki.org/Glossary#cmmi_acq CMMI for Acquisition (CMMI-ACQ)]</li>
+
<li>Product and service [http://eitbokwiki.org/Glossary#acquisition acquisition]—[http://eitbokwiki.org/Glossary#cmmi_acq CMMI for Acquisition (CMMI-ACQ)]</li>
−
<li>Data management &mdash; [http://eitbokwiki.org/Glossary#cmmi_dmm CMMI for Data (CMMI-DMM)]</li>
+
<li>Data management—[http://eitbokwiki.org/Glossary#cmmi_dmm CMMI for Data (CMMI-DMM)]</li>
 
</ol>
 
</ol>
−
 
+
<h3>People Capability Maturity Model </h3>
−
<h3> IT-Capability Maturity Model (IT-CMF)</h3>
+
<p>In addition, the CMMI Institute provides the ''People CMM'' (https://www.sei.cmu.edu/reports/09tr003.pdf), which describes five levels of maturity for workforce management. It progresses from inconsistent management, to people management, to competency management, to capability management, and ends with continually improving management practices. It is designed for continuously improving individual competencies, developing effective teams, motivating improved performance, and shaping the people capabilities the organization needs to accomplish its future plans. </p>
−
 
+
<h3>IT-Capability Maturity Model (IT-CMF)</h3>
−
<p>Getting better at EIT strategy and governance requires both organizational change in how IT is managed and the development of individuals. The IT-Capability Maturity Model (IT-CMF) takes an organizational management approach to improving IT capability rather than a one focused on processes and thus is very complimentary to CMMI. IT-CMF helps organizations to measure, develop, and monitor their IT capability maturity progression for maximum benefit in their particular context. It consists of 35 IT management capabilities and these are organized into four macro capabilities: managing IT like a business; managing the IT budget; managing the IT capability; managing IT for business value. Its 35 Critical Capabilities (CCs) are defined in as “A defined IT management domain that helps mobilize and deploy IT-based resources to effect a desired end, often in combination with other resources and capabilities” (Curley et al. 2015).  Each has five different levels of maturity starting from "initial" and going up to ‘optimizing’. The IT-CMF includes questionnaires to assess current maturity and a suite of practice recommendations to improve maturity.</p>
+
<p>Getting better at EIT strategy and governance requires both organizational change in how EIT is managed and the development of individuals. The IT-Capability Maturity Model (IT-CMF) takes an organizational management approach to improving EIT capability rather than one focused on processes and thus is very complimentary to CMMI. IT-CMF (https://ivi.ie/) helps organizations measure, develop, and monitor their EIT capability maturity progression for maximum benefit in their particular context. It consists of 35 EIT management capabilities and these are organized into four macro capabilities: managing EIT like a business; managing the EIT budget; managing the EIT capability; and managing EIT for business value. Its 35 critical capabilities (CCs) are described as "A defined EIT management domain that helps mobilize and deploy EIT-based resources to effect a desired end, often in combination with other resources and capabilities".&nbsp;[[#F_Two|[2]]] Each has five different levels of maturity starting from "initial" and going up to "optimizing." The IT-CMF includes questionnaires to assess current maturity and a suite of practice recommendations to improve maturity.</p>
 +
<h2>References</h2>
 +
<div id="F_One"></div><p>[1] Capability Maturity Model Integration (CMMI) Version 1.2 Overview, http://www.sei.cmu.edu/library/assets/cmmi-overview071.pdf, Software Engineering Institute, Carnegie Mellon University, 2007. </p>
 +
<div id="F_Two"></div><p>[2] IT Capability Maturity Framework (IT-CMF): The Body of Knowledge Guide. 2015. Eds. Martin Curley, Jim Kenneally, Marian Carcary. Van Haren Publishing.</p>

Latest revision as of 22:51, 22 December 2017

Welcome to the initial version of the EITBOK wiki. Like all wikis, it is a work in progress and may contain errors. We welcome feedback, edits, and real-world examples. Click here for instructions about how to send us feedback.
Ieee logo 1.png
Acm logo 3.png

 

1 What Is a Maturity Assessment

Capability maturity for EIT refers to EIT's ability to reliably perform. Maturity is measured by an organization's readiness and capability expressed through its people, processes, data, and technologies and the consistent measurement practices that are in place. The organization's maturity directly relates to the ability to execute the EIT strategy; therefore, there is a need to assess maturity as an input to a realistic plan and as a guide to maturing EIT to desired levels. In other words, unless the EIT organization "knows itself," it can't make plans to do more or to improve. Adoption of "lessons learned" is a key improvement strategy. Mature EIT organizations collect lessons learned during each project as it is executing and build the results into organizational improvements on a regular basis. When reviewed and areas prioritized by management, a maturity assessment is an input to the EIT strategy formulation, because its results may highlight its performance constraints.

Maturity assessment involves scoring the organization against defined criteria and a ranking scheme. This assessment is generally organized in ascending steps with strategies on how to move up the maturity scale. Scales are often defined in a 1–5 range that indicates increasing levels of maturity. Some schemes allow for scoring that includes decimal points (such as 2.5). A common scheme defines the five levels in the following way:

  1. Performed—Activities are performed in an ad hoc manner.
  2. Managed—Activities are performed with managed processes.
  3. Defined—Activities are defined so the organization can perform them in a uniform manner.
  4. Measured—Oversight is given to the performed activities to ensure performance and uniformity.
  5. Optimized—Continuous improvement processes are in place on the defined and measured processes.

A typical description of organizational maturity was developed by Stanford's SLAC National Accelerator Laboratory, as shown in the table below.

Skill Level 1
Performed		 Level 2
Managed		 Level 3
Established		 Level 4
Predictable		 Level 5
Optimizing
People
  • Success depends on individual heroics
  • "Fire fighting" is a way of life
  • Relationships between disciplines are uncoordinated, perhaps even adversarial
  • Success depends on individuals and management system supports
  • Commitments are understood and managed
  • People are trained
  • Project groups work together, perhaps as an integrated product team
  • Training is planned and provided according to roles
  • A strong sense of teamwork exists within each project
  • A strong sense of teamwork exists across the organization
  • Everyone is involved in process improvement
Process
  • Few stable processes exist or are used
  • Documented and stable estimating, planning, and commitment processes are at the project level
  • Integrated management and engineering processes are used across the organization
  • Processes are quantitatively understood and stabilized
  • Processes are continuously and systematically improved
Technology
  • The introduction of new technology is risky
  • Technology supports established, stable activities
  • New technologies are evaluated on a qualitative basis
  • New technologies are evaluated on a quantitative basis
  • New technologies are proactively pursued and deployed
Measurement
  • Data collection and analysis are ad hoc
  • Planning and management data is used by individual projects
  • Data is collected and used in all defined processes
  • Data is systematically shared across projects
  • Data definition and collection are standardized across the organization
  • Data is used to understand the process qualitatively and stabilize it
  • Data is used to evaluate and select process improvements

Periodic reassessments are performed to gauge progress against the baseline assessment and prior periods. Adjustments to the efforts to maintain and improve maturity can then be made against possible strategic priority changes, governance initiatives, and roadmap resets.

Maturity assessments on internationally recognized frameworks generally involve external auditors with certification and recertification requirements. Engagement in the maturity assessment and improvement process requires a minimum level of organization self-awareness to the issues and commitment to the improvements necessary. A cultural readiness, resistance, and capability assessment may be built into a maturity assessment. The set of standards centered round ISO/IEC 33001 attempt to provide an overall general structure for process assessment related to software development.

1.1 Capability Maturity Model Integration (CMMI)

Capability Maturity Model Integration (CMMI) [1] is a standard reference model for process improvement with cross-sector applicability with special focuses:

  1. Product and service development—CMMI for Development (CMMI-DEV)
  2. Service establishment, management—CMMI for Services (CMMI-SVC)
  3. Product and service acquisition—CMMI for Acquisition (CMMI-ACQ)
  4. Data management—CMMI for Data (CMMI-DMM)

1.2 People Capability Maturity Model

In addition, the CMMI Institute provides the People CMM (https://www.sei.cmu.edu/reports/09tr003.pdf), which describes five levels of maturity for workforce management. It progresses from inconsistent management, to people management, to competency management, to capability management, and ends with continually improving management practices. It is designed for continuously improving individual competencies, developing effective teams, motivating improved performance, and shaping the people capabilities the organization needs to accomplish its future plans.

1.3 IT-Capability Maturity Model (IT-CMF)

Getting better at EIT strategy and governance requires both organizational change in how EIT is managed and the development of individuals. The IT-Capability Maturity Model (IT-CMF) takes an organizational management approach to improving EIT capability rather than one focused on processes and thus is very complimentary to CMMI. IT-CMF (https://ivi.ie/) helps organizations measure, develop, and monitor their EIT capability maturity progression for maximum benefit in their particular context. It consists of 35 EIT management capabilities and these are organized into four macro capabilities: managing EIT like a business; managing the EIT budget; managing the EIT capability; and managing EIT for business value. Its 35 critical capabilities (CCs) are described as "A defined EIT management domain that helps mobilize and deploy EIT-based resources to effect a desired end, often in combination with other resources and capabilities". [2] Each has five different levels of maturity starting from "initial" and going up to "optimizing." The IT-CMF includes questionnaires to assess current maturity and a suite of practice recommendations to improve maturity.

2 References

[1] Capability Maturity Model Integration (CMMI) Version 1.2 Overview, http://www.sei.cmu.edu/library/assets/cmmi-overview071.pdf, Software Engineering Institute, Carnegie Mellon University, 2007.

[2] IT Capability Maturity Framework (IT-CMF): The Body of Knowledge Guide. 2015. Eds. Martin Curley, Jim Kenneally, Marian Carcary. Van Haren Publishing.

Retrieved from "http://eitbokwiki.org/index.php?title=Enterprise_IT_Maturity_Assessments&oldid=1902"