Aggregated enterprise architecture wisdom
Just an announcement that the video of the ‘fundamentals’ part of my recent talks on essential insights on technology and psychology in relation to the digital revolution is now online on my YouTube channel.
The third ‘fragmentation wave’ of the IT-revolution is upon us, it seems. Fragmentation is a repeated pattern in the IT-revolution, that has given us object oriented programming and agile/DevOps as solutions to managing complexity. Now, it is the organ…
As the IT world has been largely taken over by Agile methods, the concepts of Definition of Ready and Definition of Done have become mainstream.
While these concepts were introduced at the story/sprint level in Scrum, they have taken on a wide role an…
McKinsey seems to be the first ‘big consultancy’ that really frees itself from outdated, ineffective, orthodox enterprise architecture notions.
It is generally accepted that IT Strategy must follow Business Strategy. It seems a no-brainer. But is it? There are reasons to look at it differently, reasons that become more pressing as organisations become more digital.
There is a massive movement of organisations moving to agile-at-scale (e.g. SAFe). Ironically, it can turn into an organisation becoming one big ‘project’, the opposite of what agile wants to achieve.
John Zachman is often called ‘the father of Enterprise Architecture’. Some will characterise his work as irrelevant and John a dinosaur. But he is surprisingly agile, in more ways than one.
I’ve (finally!) posted the narrated presentation of a slightly adapted version of my keynote at the Enterprise Architecture Conference Europe 2018: “Architecture in an Age of Agile”. Both Architecture and Agile are important aspects o…
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…
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…
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 chang…