Index

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

Methods

Methods

Phases

Overview
Strategising
Process

Capability Modelling

With DOTS
With MAGIC
Roadmapping
Process
Intermediate Journey
Create update Intermediate Models
Create update Portfolio Model
Enterprise Transformation Strategy
Solutioning
Process
Governance and Lobbying
Process
Overview
Dovetailing with the Project Process
Strategic vs Tactical
Transformation Debt
Ratio

Disciplines

Modelling
Populate The Model
Provide EA Education

Artefacts

Artefacts

Ontology

Structural and Transformational
Models
Relationships

Meta models

Overview
Transformational
Principles
Debt Agreement
Structural

Guidance

Guidance

Principles

Overview
Types
WHAT We Produce
HOW We Do Transformation

Items

Items

Frameworks

PEAF

Tools

Coverage
Vendors

Evaluation

Requirements
Process
Raw Scores
Weighted Scores
X Requirements

Culture

Culture

Organisation Structure

Traditional vs Pragmatic

Enterprise Architect

Two Types

Type 1

Requirements
Duties

Type 2

Requirements
Duties

The Management vs The Workers

Most Valued Player MVP
Comparison

IT vs The Business

Is IT Special

What vs How
Yes But Not Because its IT
When Two Tribes Go To War
Should IT Ever Say No to The Business
Comparison

Roles

Overview
SIB Strategic Investment Board
EASG Enterprise Architecture Steering Group

PF2

Appendix

Appendix
Background
The Author
Keypoints
Sources and Resources
Tail
       
Click a Thumbnail to read the component. Hold down Ctrl while clicking to expand the image

 

Enterprise Architecture

A Pragmatic Approach Using PEAF

Buy Paperback
or Kindle















PF2>Appendix>Background ◄◄◄           .           ►►► PF2>Appendix>Keypoints

Who Created The Pragmatic Family of Frameworks (PF2)?

A simple man.

My career began at the age of 16 in 1978 as an Electrical and Electronic Apprentice with Marconi Radar Systems (Blackbird Road, Leicester, UK) At that time I was really into electronics and had been playing with little circuits for a few years. It was really exciting. I spent my time between college and “The Factory” where I got the chance to work in many different departments. It was really exciting. Around 1980 I ended up in a Department (New Parks, Leicester UK) called TEPIGEN (TElevision PIcture GENerator) who had built the visual system for a ship simulator. Six million Pounds of custom built hardware (that had less processing power than the CPU in the phone that’s in your pocket) consisting mainly of four racks of “Picture Processors” (Motorola 68000s) driven by a PDP11. It was really exciting. The output was on three channels each delivering 40 degrees field of view which drove three large Barco projectors. Interestingly at one point there were black speckles that kept appearing on the displays, moving about in random patterns and appearing and disappearing in the same apparently random fashion. After months of software and hardware investigation the problem was identified. It was a test Radar across the apron from where our Portacabins where located that was spraying us periodically with microwaves! It was really exciting.

 ...to read more, please Login or Register

PF2>Appendix>Background ◄◄◄         Enroll to Self Study Now!         ►►► PF2>Appendix>Keypoints

Keypoint

Adopt this component by...

Use people for the type of person they are, not the type of person you want them to be. If we were all the same, nothing would ever get done.

Questions to ponder...

What are the MBTI, DISC and Belbin profiles of the people in your Enterprise?

Do they all suit their roles?

Have you ever found someone to be a “difficult person” or a “loose cannon”?

If so, did their MBTI/DISC/Belbin profile taken into account?

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