How was Training?

more

I thought it achieved the purpose of explaining EA and how to put it in place, and it was helpful that the instructor integrated the education with a reasonable understanding of what we already have in place. - IT Architect, Hasbro, USA, Jan 2013

Recommend PEAF?

more

Yes - understandable, not so heavy as togaf, not as abstract as zachman - Enterprise Architect, The Corporate Architects, Belgium, Jan 2015

  Introduction   Context   Methods   Artefacts   Culture   Environment   Adoption  

Desktop

Mobile

 

<< Previous <<

>> Next >>

This section details the measures that would allow an Enterprise to measure the level of Maturity they currently have in relation to the whole Enterprise Transformation cascade and to also measure whether they have attained an increase in maturity.

These measures are not hard and fast rules (although they can be used as such), but are used to provide a basis for Enterprises to get a feel for their current level of Enterprise Transformation Maturity and to help guide them to decide what level of maturity they wish to attain and in what timescales.

Since Enterprise Transformation maturity is about how effective and efficient the whole Enterprise Transformation cascade is and not the individual parts, maturity is measured in terms of how the parts fit and work together and not the maturity of the individual parts since maturity of the individual parts is addressed using lower level frameworks such as PEAF, ITIL, TOGAF, PRINCE2, MSP, etc.

The Value is in the Lines not the Boxes

 

Methods

Unconsciously Incompetent

Consciously Incompetent

Consciously Competent

Definition

For each

Phase

boundary...

Modelled

No

Out of date

Yes and up to date

Improvement

Never

Annually

Quarterly

Tool Support

None

Some

Mostly

Projects budget for it

None

Some

Mostly

Ops

For each

Phase

boundary...

Approach

Mostly Black art

Some Structured

Mostly Structured

Artefacts

Unconsciously Incompetent

Consciously Incompetent

Consciously Competent

Definition

For each

Phase

boundary...

Modelled

No

Out of date

Yes and up to date

Improvement

Never

Annually

Quarterly

Tool Support

None

Some

Mostly

Projects budget for it

None

Some

Mostly

Ops

For each

Phase

boundary...

Approach

Mostly Black art

Some Structured

Mostly Structured

Culture

Unconsciously Incompetent

Consciously Incompetent

Consciously Competent

Definition

 

For each

Phase

boundary...

 

Modelled

No

Out of date

Yes and up to date

Language

Undefined

Somewhat defined

Mostly defined

Ops

For each

Phase

boundary...

 

Type

Authoritarian

Common Sense

Meritocracy

Language

Not used

Used somewhat

Used Mostly

Environment

Unconsciously Incompetent

Consciously Incompetent

Consciously Competent

Definition

 

For each

Phase

boundary...

 

Tool

Existence

None

Pragmatic Tool

Full-blown Tool

Framework

Existence

None

Ad-hoc

Industry Standard

Operation

For each

Phase

boundary...

Tool

Use

Used by a few select individuals

Used by many people

Used by most people

Change Control

Haphazard or non-existent

Mostly controlled

Fully controlled

Management

Centralised

Mostly federated

Fully federated

Framework

How well are we using / implementing the framework

Non existent

Used pragmatically

Used extensively

 

2008-2016 Pragmatic EA Ltd