Index

PF2

Head

Introduction

Introduction

Companies

Overview
Pragmatic EC
Licensing

Training

Certification Courses
Focused Workshops
Options

Pragmatic Publishing Platform

Overview
Design

PEFF

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

Ontologies

Ontologies

Structural

MAGIC
Relationships

Transformational

MAGMA
Relationships

Enterprise

DOTS
Relationships

POET

Methods

Methods

Phases

Overview
Architectures
Resource Utilisation
Pattern
Models

Disciplines

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

Detail

Structural and Transformational Zachman

Culture

Organisation Structure

Workers

PEAF

Methods

Methods

Phases

Roadmapping

Process
Solutioning
Process
Governance and Lobbying
Process
Strategic vs Tactical
Transformation Debt
Ratio

Artefacts

Artefacts

Meta models

Transformational

Principles
Debt Agreement

Guidance

Guidance

Principles

Overview
Types
WHAT We Produce
HOW We Do Transformation

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

 

Enterprise Transformation Governance

A Pragmatic Approach Using Transformation Debt

Buy Paperback
or Kindle













PEAF>Methods>Section ◄◄◄           .           ►►► PEAF>Methods>Phases>Solutioning

Although the process laid out here is step by step, it should be understood that many iterations of this work may need to be done, and that these steps only provide an overall outline of the work required and the probably order of its execution.

When

The process is usually conducted once per year although can be executed on an ad-hoc basis whenever a major event causes the Enterprise to rethink its Intermediate or Target Model. E.g. A Merger or acquisition. In addition, it should be understood that when Solutioning and Engineering projects execute, they may (via Lobbying) expose problems or opportunities that cannot be solved or exploited unless the roadmap is revisited.

 ...to read more, please Login or Register

PEAF>Methods>Section ◄◄◄         Enroll to Self Study Now!         ►►► PEAF>Methods>Phases>Solutioning

Keypoint

Adopt this component by...

Accumulated Transformation Debt™ is reviewed during Roadmapping.

Enterprise Architect: Feed outstanding Transformation Debt™ into Roadmapping.

Questions to ponder...

Does this process match your Enterprises process for doing Roadmapping?

If not, is their anything missing?

Does it feed currently existing Transformation Debt into the mix?

How would you mature your Enterprises Roadmapping process?









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