Break that Iceberg and free your true value

The Linkedin Post that started the idea.

Knowledge Preservation

Technical Debt is Business Value imprisoned in the Iceberg of Legacy Technology.

Break that Iceberg and free your business value.

Refactoring is very wide and slow circle of pain, always leading back to the beginning.

BPT Domains are regions of gravitational pull for organization roles

• Business roles are puled to the Business Domain
• BA roles gravitate around the Products Domain
• Engineers and DevOps fly above the Technology Domain

How is Knowledge Liberated

The Workflow of Knowledge Liberation

flowchart 
    A[Business creates initiative<br>to remove legacy] --> B[Business & Product declare<br>Legacy processes & Technical Debt]
    B --> C[Product forms<br>knowledge storage]
    C --> D[Business decides<br>new products]
    D --> E[Business selects<br>first new Product]
    E --> F[Business & Product<br>declare new Project]
    F --> G1[7.1 BAs decouple knowledge<br>from legacy processes]
    F --> G2[7.2 Product & Technology decouple knowledge<br>from legacy components]
    G1 --> I{More legacy<br>decoupling?}
    G2 --> I
    I -- Yes --> F
    I -- No --> J[Business & BAs decide<br>Conceptual & Logical Architecture]
    J --> K[BAs & Engineers decide<br>Physical Architecture]
    K --> L[Technology decides<br>Application Architecture]
    L --> M[Engineers start<br>Project Cycling]