11 years, 11 months, 11 days

Today, it has been 11 years, 11 months, and 11 days since the first post on this blog. The blog was called masteringarchimate.com and the first years the modelling language ArchiMate was the subject. To celebrate, I am today presenting my ArchiMate 3.2 compatible (here and there a bit opinionated) 'ArchiMate Cheat Sheets' in PDF. A preliminary, English only version. More to come later...

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.

The lack of use cases for blockchain should teach organisations a valuable lesson about handling hypes

If someone tries to get you to invest in some shiny new technology — like blockchain 5-8 years ago — beware. How do you judge these proposals? A realistic use case is key.

Cicero and chatGPT — signs of AI progress?

Cicero, an AI, performed in the top 10% against human performers in the game Diplomacy, which is about negotiating with others. chatGPT is making the rounds with its impressive output. Are these AI breakthroughs or at least signs of real progress? Or signs of trouble to come?

On the Psychology of Architecture and the Architecture of Psychology

Advisors need (a) to know what they are talking about and (b) be able to convince others. For architects, the first part is called 'architecture' and the second part could be called 'the psychology of architecture'. We tend to do that already, but most attention is paid to the role of the advisor. But it takes two to tango. The 'receiving end' (the one being advised) plays a key role and it is here that psychological and neurological research of the last few decades on 'the architecture of psychology' can be put to good use.

Layering — is it really a useful approach in Business/IT/Enterprise Architecture?

Is layering — e.g. the classic BDAT (Business, data, Application, Technology) stack — really useful in Enterprise Architecture? An analysis with some side nodes about ArchiMate. Warning: may contain traces of analytic EA geekery.