1. Thoughts on IT Enterprise Architecture Maturity Models for the
Thoughts on IT Enterprise Architecture Maturity Models for the .edu Community
June 29, 2017

2. What is a Maturity Model?
Wikipedia provides a (somewhat less than helpful) definition:
Maturity is a measurement of the ability of an organisation for continuous improvement in a particular discipline (as defined in O-ISM3).[1] The higher the maturity, the higher will be the chances that incidents or errors will lead to improvements either in the quality or in the use of the resources of the discipline as implemented by the organisation.
Most maturity models assess qualitatively people/culture, processes/structures, and objects/technology.[2]
Two approaches for implementing maturity models exist. With a top-down approach, such as proposed by Becker et al.,[3] a fixed number of maturity stages or levels is specified first and further corroborated with characteristics (typically in form of specific assessment items) that support the initial assumptions about how maturity evolves. When using a bottom-up approach, such as suggested by Lahrmann et al.,[4] distinct characteristics or assessment items are determined first and clustered in a second step into maturity levels to induce a more general view of the different steps of maturity evolution.
Source:
ITIL provides a definition in the context of Process Improvement and CMMI
The Capability Maturity Model Integration (CMMI) is a process improvement approach developed by the Software Engineering Institute (SEI) of Carnegie Mellon University. CMMI provides organizations with the essential elements of effective processes. It can be used to guide process improvement across a project, a division or an entire organization. CMMI helps integrate traditionally separate organizational functions, sets process improvement goals and priorities, provides guidance for quality processes, and suggests a point of reference for appraising current processes. There are several CMMI models covering different domains of application.
Source: 05 ITIL Continual Service Improvement

3. What are the outcomes of using a Maturity Model
Using the ITIL language: “guide process improvement across a project, a division or an entire organization”
Then, we should expect a Maturity Model effort to deliver:
An assessment of current state across the selected domains
An understanding of what is possible in the selected domains
A process to setting target process improvements in the selected domains
A plan to move each domain from current to desired state, including:
Investments
Resources
Timing

4. Who is the audience?
There are two general audiences for an IT Maturity Model effort:
Those who need to know where they are on the maturity scale
Those who need to know how maturity levels have changed over time
Examples of interested roles include:
Technical staff
Technical managers
Technical executives
University management
University executives
Proposal:
As a practical matter, process improvement in the ITANA context is a strategic effort aimed at Technical and University executives
If we agree to this, then language used in creating a Maturity Model and the assessments must be in language leveled for the intended audience: clear, compelling, strategic. Not technical.

5. What are the elements of a Maturity Model
A Maturity Model establishes:
A scale for process maturity
A set of processes domains of interest
Metrics for each process domain x maturity level, in language that describes process effectiveness

6. The X Axis: Providing Maturity with a Semi-Quantified Scale
Several scales exist with varying numbers of levels and definitions.
Sources:

7. Proposed Maturity Scale
Proposal: Use a 5-level scale of 1 to 5
Key Rationale: Conforms to CMMI standard
Source:

8. The Y Axis: What to measure?
The CMMI does not have a process domain model for the .edu community. We could use an existing process domain model, or invent one.
Sources:

9. Proposed Domain Model Proposal: ITIL Service Model
Key Rationale: Comprehensive, conforms to ITIL standard
Sources: 9
Source:

10. Descriptions of Maturity for Each Domain
Maturity descriptions for each domain is language that expresses the organization’s minimum capability to ideal capability. This is spread over levels in the chosen scale. Typically the low end is chaotic and the high end is excellent.

11. Example of a Maturity Model Assessment Capability Vision
4/8/14
The Vision for EA Maturity Model Assessment Capability
Provide University organizations with a common approach for understanding their current levels of operational and process maturity, while enabling them to plan improvements in areas that need it the most.
Objectives
Guiding Principles
Key Performance Indicators
An assessment of current state across the selected domains
An understanding of what is possible in the selected domains
A process to set target process improvements in the selected domains
A plan to move each domain from current to desired state, including:
- Investments
- Resources
- Timing
Business relevance: Services should be defined in terms of the services customers demand.
Financial transparency: Services should have cost transparency with stakeholders.
Customer experience: Services should deploy mechanisms that enable customers to make appropriate service selections and to control costs.
Ownership: Services should centralize accountability with service managers
Business relevant measurement: Services should measure and report service performance effectively
Culture: Services should create a culture among all staff that promotes continuous service improvements
Compliance - Compliance metrics determine if the process is being performed as documented in policies and procedures.
Quality - Quality metrics are used to demonstrate how well something is being done (or how free it is of errors).
Performance - Performance or efficiency metrics demonstrate how fast or slow something is happening.
Value - Value or effectiveness measures seek to answer the question “Are we making a difference?”.

12. Assessment: What Metrics to Use When Measuring the Maturity of a Process?
Assessment of process maturity is a combination of quantified (numeric) assessment along with qualified (intuitive) assessment. Both can be combined into a scale that gives a comprehensive view of processes.
Sources:

13. Proposed ‘Measures’ for Assessing Service Maturity for Each Domain
Maturity Measurement requires comparing the current-state of a process against the spectrum of maturity capabilities defined for a domain. Some considerations that can be used include:
Compliance - Compliance metrics determine if the process is being performed as documented in policies and procedures.
Quality - Quality metrics are used to demonstrate how well something is being done (or how free it is of errors).
Performance - Performance or efficiency metrics demonstrate how fast or slow something is happening.
Value - Value or effectiveness measures seek to answer the question “Are we making a difference?”.
Scoring a Maturity Level Quantifies These Qualitative Measures
Sources:

14. Hypothetical Model of an Overall Enterprise
This maturity model uses the major ITIL processes to give an overall assessment.
Sources:

15. Hypothetical (Detailed) Model of an Enterprise or Sub-organization
This maturity model uses detailed ITIL processes domains for a deeper assessment.
Sources:

16. Reference Materials These documents are available from the internet:
IT Process Wiki - the ITIL® Wiki: This Wiki is about the IT Infrastructure Library ITIL® (ITIL 2011, ITIL V3 & V2), ISO and IT Service Management (ITSM)
EDUCAUSE ITIL CG Webinar – December 4, How to do an ITSM Process Maturity Assessment
Lund University - School of Economics and Management - Department of Informatics - IT maturity self-assessment - does a quantitative survey get it right?
NATIONAL ASSOCIATION OF STATE CHIEF INFORMATION OFFICERS - Enterprise Architecture Maturity Model
EDUCAUSE CENTER FOR ANALYSIS AND RESEARCH - Getting Your Ducks in a Row: IT Governance, Risk, and Compliance Programs in Higher Education
EDUCAUSE - Higher Education IT Governance Checklist