Index

PF2

Head

Introduction

Introduction

Companies

Overview
Pragmatic EC
Licensing

Training

Certification Courses
Focused Workshops
Options

Pragmatic Publishing Platform

Overview
Design

Frameworks

Frameworks

Overview

Prominent EA Frameworks Strengths and Weaknesses
Reading Approach
Connecting the DOTS
Coverage
X Frameworks
Applicability
Context
Influences
Versions

Available Now

PEFF Enterprise Fundamentals
Why Use It
POET Enterprise Transformation
Overview
Why Use It
Operating Model
PEAF Enterprise Architecture
Overview
Why Use It
Logical Model
PTMC Transformation Maturity
Overview
Why Use It
Logical Model

Coming Soon

POED Direction
Overview
POEO Operation
Overview
POES Support
Overview
PEEF Enterprise Engineering
Overview

Comparisons

TOGAF and Zachman
Misunderstanding
Criteria
Raw Scores
Overall
Example Weightings 1
Example Weightings 2

TOGAF

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

Zachman

Basic Message
Missing Perspective and Model
Overall
Architect Engineer
Why How
How When What Where Who
Perspectives and Models

Adoption

Overview
Mapping

PEFF

Head

Language

Language

Basics

I Didnt Mean What You Heard
What is a System
What is an Enterprise
What is Transformation
What is a Framework
Theory or Practice
Colours
What is Business Architecture Enterprise Architecture Solution Architecture

Pragmatic

Effectiveness
Efficiency
Quality Time
Fundamentals
Thinking
Empowerment
Sustainability

Ontologies

Ontologies

Structural

MAGIC
Relationships
Interrelations

Transformational

MAGMA
Relationships

MAGIC and MAGMA Derivation

Structure
Strategy
Execution
Fundamental Types
Levels

Enterprise

DOTS
Relationships
Problems
Department Mapping
Department Percentages

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

Adoption

Adoption
Step 4
Actions
Step 5
Actions
Step 6
Actions

Methods

Methods

Phases

Overview
Architectures
Resource Utilisation
Strategising
Roadmapping
Solutioning
A Pragmatic Approach
Project Execution
Pattern
Models

Disciplines

Overview
Capability Model
Phase
Artefacts
Orchestration
Requirements Management
Discovery
Analysis and Design
Modelling
Decision Making
Culture
Making Them
Changing Them
The Red Button
Jumping to Conclusions
Governance and Lobbying Disciplines

Governance and Lobbying

Artefact Mapping
Transformation Synchronisation
►Technical Debt
Technical Debt vs Transformation Debt

Transformation Debt

Overview
Investment Profiles
Investment Results

Artefacts

Artefacts

Overview

Overview
Architectures

Ontology

Basics
Mapping to Phases
Volume Volatility and Focus
Impact and Costs
Population
Two Whys
Recursive Model Abstractions
Transitions

Detail

Structural and Transformational Zachman
Models

Meta models

Mapping

POLDAT
BMM
EBMM
Hybrid

Guidance

Guidance
Context is King
Types

Items

Items

The Architecture Paradigm

What is Architecture

Purpose

Its Not What You Think
Structural Complexity
Transformational Volatility
Transformational Complexity
Contextual Volatility and Complexity

Justification

Applicability
Cost and Ability
Investment
Procrastination
Abstraction and Elaboration
Relationships
The Value is in the Lines not the Boxes
Patterns
Models Meta Models and Semantics

Architecture and Engineering

Why and How
Yin and Yang
Architect Horizontally Engineer Vertically
Overlap
Inter Phase

Frameworks

Number and Growth
How POET Helps

Tools

Number and Growth
How POET Helps
Coverage
Integration

Culture

Culture

Organisation Structure

Management
Workers

Culture Trumps Everything

For Better or Worse
The Power of Culture
Immense Problems
Immense Opportunities

Slaves to Psychology

What Do You Think
Is All Value Easy to See
I Was Only Doing What I was Told
Are You Better Than a 5 Year Old
Who Decides
Absolute Power Corrupts Absolutely
Style over Substance
The Halo Horn Effect
Cognitive Dissonance
The Dunning Kruger Effect
The Peter Principle
The Matthew Effect
Prices Law
The Best Managers Are Sociopaths
Personality Traits
The Prisons of Two Ideas
Logical Fallacies

Architects and Engineers

Fundamentals
Comparison
Architects and Engineers Who Are You

The Architect

Secrets
An Impossible Job
What Does An Architect Do
Architect or Charlatan
The Pragmatic Architect Creed
Language

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
Meta models

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

 

     

The Complete Pragmatic

Family of Frameworks
Buy Paperback
or Kindle









POET>Methods>Disciplines>Governance-and-Lobbying>Transformation-Synchronisation ◄◄◄           .           ►►► POET>Methods>Disciplines>Governance-and-Lobbying>Technical-Debt-vs-Transformation-Debt

The term “Technical Debt” (in relation to the Creation and Transformation of IT systems) was coined by Ward Cunningham March 26, 1992. He coined the debt metaphor to explain the refactoring that he was doing on the WyCash product. http://c2.com/cgi/wiki?WardExplainsDebtMetaphor

 ...to read more, please Login or Register

POET>Methods>Disciplines>Governance-and-Lobbying>Transformation-Synchronisation ◄◄◄         Enroll to Self Study Now!         ►►► POET>Methods>Disciplines>Governance-and-Lobbying>Technical-Debt-vs-Transformation-Debt

Keypoint

Adopt this component by...

Technical Debt is the future problems created when we write “bad” code. (Ward Cunningham)

Questions to ponder...

Have you heard the term “Technical Debt” before?

How did is show itself?

What happened when “Technical Debt” was created?












Terms and Conditions

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

Privacy