Confronted with the problems of Waterfall approaches, organisations are all jumping on the Agile bandwagon. This is often a very good thing. Big Up-Front Design (BUFD) has many drawbacks in volatile environments and much of what happens in IT happens in rather volatile and uncertain environments. The volatility and uncertainty come from everywhere, including the organisation itself, as I’ve argued in the book. Hence, the book suggests a much more agile and practical approach to enterprise architecture. But the book is still written from a perspective where projects are ‘classic’, with a design upfront. What about Agile? Continue reading
With the release of ArchiMate 3, The Open Group has changed the text of the license as well as their explanation. What has changed, and what does it mean? (Note, as this is not about modelling with ArchiMate but about ‘what is an open standard and how does ArchiMate stack up?’, this has not been published on the Mastering ArchiMate blog). Continue reading
Over on Enterprise Architecture Professional Journal I’ve just posted a column about ‘vertical integration’, where it comes from, how it drives certain developments (e.g. it is one of the drivers for the cloud) and how it is in conflict with years of established policy by IT departments.
The article also contains the first appearance of something I’ve been mulling about for a while already (and that is related to what was discussed in the post on this site about IT being the driver of increased complexity that creates the demand for Enterprise Architecture in the first place). This is the law of complexity-capacity exhaustion:
Capabilities deployed to lessen the impact of complexity on the human capacity to manage the landscape result in the deployment of more complexity until the limit of the capacity of humans to manage the landscape has again been reached.
In other words: every time we make something easier, we will do more of it until it is just as hard as before. Life doesn’t get easier. We just create more variation, more volume, etc., until it is as difficult for us as it was before.
Enjoy the story here.
ArchiMate, the enterprise architecture modelling language, is a standard from The Open Group (TOG). Most people infer from this that ArchiMate is an open standard (I did once) and often assume The Open Group is some sort of a not-for-profit entity. What is the real situation? This (longer than usual, but these matters need precision) post explains. Continue reading
Dutch national newspaper De Volkskrant launched a site to commemorate their initial steps on the internet, 20 years ago, on May 6, 1996. All in good fun, e.g. de site looks like a Windows 95 desktop. On it, they put a few articles from that time. Amongst the six articles they chose to put on the site, one is an opinion piece from me from July 1995. Continue reading
I’ll be giving the opening EA keynote for the Enterprise Architecture Conference Europe 2016 on 14 June 2016 in London. I’d love to discuss EA with you. So: meet me there?
Suppose you build a house. When it’s finished it’s shiny, new, and clean.
Then you live in it for decades. Stacks of old newspapers litter the floors. Sometimes a bunch of these get thrown out. You only do superficial cleaning, and crud accumulates in all nooks and crannies.
You also want to embrace the new. You enthusiastically follow each fashion trend in furniture, appliances, and so forth. A new chair arrives, but the old one is still in use because grandma gets back pains when she uses the new one. You buy new nice plates and cups, but the old ones are not thrown away, just in case. The new robot vacuum cleaner cleans the living room, but the old one is still in a closet for the cleaning the robot cannot do. Even your replacements of worn out stuff leave leftovers all over the place. Still more crud accumulates in all nooks and crannies. Sounds like a badly run household, doesn’t it? However, it also looks very much how many businesses operate with respect to their IT landscapes.