Index

PF2

Head

Introduction

Introduction

Companies

Overview
Pragmatic EC
Licensing

Training

Certification Courses
Focused Workshops
Options

Pragmatic Publishing Platform

Overview
Design

Frameworks

Comparisons

TOGAF and Zachman
Misunderstanding

TOGAF

Now What
Content vs Benefits
Overall
ADM
Other Frameworks
Other Detail
Guidance vs Detail
Trends

PEFF

Head

Ontologies

Ontologies

Structural

MAGIC
Relationships

Transformational

MAGMA
Relationships

Enterprise

DOTS
Relationships

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

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

POET

Head

Methods

Methods

Phases

Models

Disciplines

Governance and Lobbying

Transformation Synchronisation
Technical Debt
Technical Debt vs Transformation Debt

Transformation Debt

Overview
Investment Profiles
Investment Results

Artefacts

Artefacts

Ontology

Detail

Structural and Transformational Zachman
Models

Items

Architecture and Engineering

Yin and Yang
Architect Horizontally Engineer Vertically
Overlap
Inter Phase

Culture

Culture

Organisation Structure

Management
Workers

Slaves to Psychology

The Prisons of Two Ideas
Logical Fallacies

Architects and Engineers

Comparison

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

Methods

Methods
Governance and Lobbying
Process
Overview
Dovetailing with the Project Process
Strategic vs Tactical
Transformation Debt
Ratio

Artefacts

Artefacts

Ontology

Models

Relationships

Meta models

Transformational

Principles
Debt Agreement

Guidance

Guidance

Principles

Overview
Types
WHAT We Produce
HOW We Do Transformation

Items

Items

Tools

Evaluation

X Requirements

Culture

Culture

Organisation Structure

Traditional vs Pragmatic

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

 

Kick-start Your TOGAF Adoption

Pragmatically

Buy Paperback
or Kindle















POET>Items>Architecture-and-Engineering>Overlap ◄◄◄           .           ►►► POET>Culture>Section

From the perspective of the entire Transformation Capability, Architecture is performed more at the top of the stack and less at the bottom. Conversely Engineering is performed more at the bottom of the stack and less at the top.

The further down the stack we go the more concrete things become, and the further up the stack we go, the more abstract things become. This does not mean we are saying that there is no Engineering happening at the top and there is no Architecture happening at the bottom.

 ...to read more, please Login or Register

POET>Items>Architecture-and-Engineering>Overlap ◄◄◄         Enroll to Self Study Now!         ►►► POET>Culture>Section

Keypoint

Adopt this component by...

Architecture is performed largely in the early phases of Transformation, while Engineering is performed largely in the later phases.

C-Suite: Instigate training so that people recognise that Architecture is performed largely in the early phases of Transformation, while Engineering is performed largely in the later phases.

C-Suite: Instigate training so that people recognise that Architecture and Engineering are skills that can be applied anywhere.

Questions to ponder...

Does your Enterprise recognise that people working towards the top of the Transformation stack are more Architects than Engineers?

Does your Enterprise recognise that people working towards the bottom of the Transformation stack are more Engineers than Architects?

If not, does this create any problems?

Does this create any opportunities for education?

Considering each phase of Transformation, do people who work there think of themselves primarily as Architects or Engineers or a mixture?

Which phase of Transformation do you primarily work in?

Do you consider yourself to be primarily an Architect or Engineer or a mixture?

Are the Architecture and Engineering disciplines recognised in your Enterprise?

Are they working in harmony or not?

If not, what will you do to increase the harmony?



















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