Index

PF2

Frameworks

Overview

X Frameworks

Available Now

PEFF Enterprise Fundamentals
POET Enterprise Transformation
PEAF Enterprise Architecture
PTMC Transformation Maturity

Coming Soon

POED Direction
POEO Operation
POES Support
PEEF Enterprise Engineering

PEFF

Language

Basics

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

Ontologies

Structural

MAGIC

Transformational

MAGMA

Enterprise

DOTS

POET

Methods

Phases

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

Disciplines

Governance and Lobbying Disciplines

Governance and Lobbying

Technical Debt
Technical Debt vs Transformation Debt

Transformation Debt

Overview

Artefacts

Overview

Overview
Architectures

Ontology

Detail

Models

Guidance

Context is King

Types

Items

The Architecture Paradigm

Purpose

Structural Complexity
Transformational Volatility
Transformational Complexity

Justification

Applicability
Abstraction and Elaboration
Models Meta Models and Semantics

Architecture and Engineering

Yin and Yang
Architect Horizontally Engineer Vertically
Overlap

Culture

Architects and Engineers

Fundamentals
Comparison

PEAF

Adoption

Guidance

What Is EA

Bridging the Gap
You Decide
Solution Architecture

160 Char Challenge

Description
Simplified Description

Methods

Phases

Overview
Strategising
Roadmapping
Enterprise Transformation Strategy
Solutioning
Governance and Lobbying
Strategic vs Tactical
Transformation Debt
Ratio

Artefacts

Ontology

Models

Relationships

Culture

Enterprise Architect

Two Types

Type 1

Requirements
Duties

Type 2

Requirements
Duties

Roles

SIB Strategic Investment Board
EASG Enterprise Architecture Steering Group
       
Click a Thumbnail to read the component. Hold down Ctrl while clicking to expand the image

 

Definitions - Some Fundamental Definitions


PEAF>Methods>Governance-and-Lobbying>Transformation-Debt ◄◄◄           .           ►►► PEAF>Artefacts>Ontology>Models>Relationships

Although Transformation Debt Ratio™ is defined for each project, it can also be combined to produce an TDR for a group of projects in a program or an overall TDR for the entire Project Portfolio. Of course, when combining TDR you need to weight each individual TDR to get a balanced view.

While TDR for the entire Transformation Portfolio provides a useful metric at a point in time, it is more useful to track it over time. A sensible view might be that over time, an Enterprise might like to see the amount of work that is Compliant increase and the amount of work done in a Non-Compliant way decrease - since doing work in a Compliant way is generally the most effective, most efficient and least risky manner of doing it.

 ...to read more, please Login or Register

PEAF>Methods>Governance-and-Lobbying>Transformation-Debt ◄◄◄         Enroll to Self Study Now!         ►►► PEAF>Artefacts>Ontology>Models>Relationships

Keypoint

Adopt this component by...

Over time, increase the ratio of Strategic to Tactical work.

Management: Over time, increase the amount of Transformation work done in a Compliant fashion, while decreasing the amount of Transformation work done in a Non-Compliant fashion.

Questions to ponder...

What is the TDR for your currently executing Transformation Portfolio?

How do you want that to change going forward?

What do you need to do to make that happen?

What will you do to break the cycle?

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