Index

PF2

Head

PEFF

Head

Adoption

Adoption
Overview
Detail

Guidance

Iterations

Single
Over Time

Measures

Maturity Model

PTMC

Levels
Tools
Example Report
Step 0
The First Step is NOT the Hardest
Actions

Measures PTMC

Level 0

Motivation

Paradigm Shift
WE Deming
70 of All Change Initiatives Fail
Enterprise Viability
Sage Words
Basic Premise
The Transformation of Transformation
What Your Transformation Capability Looks Like
Building the Machine that Makes the Machine
Culture

Demotivation

Psychology
Dont Throw The Baby Out With The Bathwater
Domain Blindness
The Red Pill
Timing Paradox
Management Workers Paradox
Process Paradox
Unconscious Degradation
False Accomplishment
Oversimplification
Reality Avoidance
Its Just Not Sexy
The Drowning Children
Step 1
Actions

Measures PTMC

Level 1
Step 2
Actions

Measures PTMC

Level 2
Step 3
Actions

Measures PTMC

Level 3

PEAF

Head

Adoption

Adoption
Step 4
Actions
Risks
Step 5
Actions
Setup EA Governance
Prepare Process Change
Define the EA Meta model
Prepare EA Education
Prepare Culture Change
Select an EA Modelling Tool
Step 6
Actions
Rollout Process Change

Actions

Setup the EA Meta model
Provide EA Education
Rollout Culture Change
Rollout EA Modelling Tool
Guidance

What Is EA

Bridging the Gap
You Decide
Solution Architecture

160 Char Challenge

Question
Raw Word Cloud
Analysis
Analysed Word Cloud
Description
Simplified Description

Frameworks

Why use a PM Framework
Why use an EA Framework

Where to Start

Can I start with one Department
EA Catalysts
Vision
Goals
Strategies
Tactics
Objectives

Tools

Types

Issues

Ability to Use Information
Effort to Maintain Information
Fundamentals
Can I use my CMDB
Content
Entities
Attributes
       
Click a Thumbnail to read the component. Hold down Ctrl while clicking to expand the image

 

- TK-PEAF Adoption










PEAF>Adoption>Guidance>Frameworks>Why-use-a-PM-Framework ◄◄◄           .           ►►► PEAF>Adoption>Guidance>Where-to-Start>Can-I-start-with-one-Department

Here we identify the things that EA claims to achieve. It aims to increase our maturity (Effectiveness and Efficiency) with respect to Strategising, Roadmapping and Project Governance. Adopting EA is not about doing these things - it is about how we do these things.

So, can we achieve all these things without utilising an EA framework like PEAF? The answer is, yes of course we can. If we have experienced Enterprise Architects and they are allowed to execute their role in the way they know to be efficient and effective they would have no reason to adopt PEAF.

 ...to read more, please Login or Register

PEAF>Adoption>Guidance>Frameworks>Why-use-a-PM-Framework ◄◄◄         Enroll to Self Study Now!         ►►► PEAF>Adoption>Guidance>Where-to-Start>Can-I-start-with-one-Department

Keypoint

Adopt this component by...

Using an EA framework will not guaranteed success. Not using an EA framework will not guaranteed failure.

Questions to ponder...

Has your Enterprise adopted an EA framework?

How was the mandate to do so secured?

If not, who in your Enterprise, is Accountable for the EA capability?

© 2008-2021 Pragmatic 365 Ltd         A Non-Profit dedicated to improving Transformation, and the lives of people that work in Transformation.