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









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?













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