All Posts

Another error corrected in my #ArchiMate 3.0.1 Reference Sheets

I've corrected another error (again reported by Alun Champion. Thanks!) in the ArchiMate 3.0.1 sheets. The Realisation from Technology Interface to Business Interface was in the sheet twice. Not a breach of the grammar, but better to have it fixed…

Prioritising Architecture and Debt with “Dado’s Diagram”

The previous blog post introduced a way to use WSJF (Weighted Shortest Job First) in Architecture prioritisation settings. That approach does have something missing which my colleague Henk Dado's approach to prioritising the fixing of debt has: a way to…

Agile, Dirt, and Technical Debt

Our discipline has long been working with the concept of 'technical debt'. Generally, technical debt is a (often hidden, but not always) defect of some substantial scale. There is substantial effort involved in repairing the debt, otherwise wel will classify…

Prioritising Architecture under Agile

In the previous story, Agile teaches us the true meaning of Architecture, I introduced a 'new' definition of Architecture: the design decisions that are hard to completely remove from implementations (or in short: that what is hard to change). And I…

Agile teaches us the true meaning of Architecture

What is architecture? Not of cities or buildings, but the organisational version: enterprise architecture, solution architecture, application architecture, software architecture, business architecture, infrastructure architecture? My neck hairs generally rise a little when we architects turn to this particularly vexing and…

Architecture principles considered harmful

Architecture principles are a very popular tool in the enterprise architect's tool box. The underlying concept of 'comply or explain', however, makes them particularly toxic. [This article originally appeared on InfoWorld in 2015. It has been reproduced here to have…