[Sticky] Link to the YouTube video of the 'fundamentals' part of my 2024 talks on insights into the digital revolution. About how the IT revolution provides reliable performance, but the price paid is less agility (IT is brittle and thus ever more It becomes ever more difficult to change). About how we humans react/have reacted to this and why 'Complexity Crunch' and not a 'Singularity Point' is coming. Also contains links to related posts on the site for those that rather read than watch..
Category: Agile and Architecture
Don’t forget all the things that a core team performs to a tee, but that you never see
The third 'fragmentation wave' of the IT-revolution is upon us, it seems. Fragmentation/encapsulation is a repeated pattern in the IT-revolution for managing complexity. First as object oriented programming (for code) and later as agile (for IT landscape change). Now, it is the organisation’s turn to fragment. How strong is your mission, your ‘why’? You might soon find out, thanks to IT.
Definition of Ready, Done? What about a ‘Definition of Broken’?
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 and are generally used at all levels these days, not just on stories, but also on features and epics, the larger items in the agile-tree. There is, however, a new concept that maybe very helpful at the higher levels that we might use: a Definition of Broken.
Will McKinsey be the first ‘big consultancy’ that gets (enterprise) architecture right?
McKinsey seems to be the first 'big consultancy' that really frees itself from outdated, ineffective, orthodox enterprise architecture notions.
Should you derive your IT Strategy from your Business Strategy? Probably not too much.
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.
From Dark Scrum to Broken SAFe — some real problems of Agile-at-scale. And a way out.
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.
Yes, 2-speed IT is real, but not like you think
The idea of 2-speed IT has been doing the rounds for a while. It is now dying. But in a different way, it is actually a really important aspect of IT.
John A. Zachman: Agile at 82 (85)
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.
“Architecture in an Age of Agile” is online
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 of maximising your success in digital…
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…
Read More Prioritising Architecture and Debt with “Dado’s Diagram”
R&A IT Strategy & Architecture 