Aggregated enterprise architecture wisdom
Agility is the ability to change direction quickly.
The paradox of agility is that it is that the slower you are moving the faster you can change direction.
Just going really fast, in the belief that speed is agility, can lead to a nasty, sudden stop.
Photo by Dan Masa
https://www.flickr.com/photos/danmasa/27160870210/in/dateposted/
creativecommons.org 2.0
By The Open Group It’s not just industry and corporations that are undergoing massive change due to digital transformation—governments worldwide are being equally affected by the need to create more efficient processes and to provide online services to citizens. With … Continue reading →
In the past, my colleagues and I have written several blogs on the combination of enterprise architecture and agile ways of working (e.g. Enterprise Architecture and Agile Development: Opposites Attract?, Enterprise Architecture and Innovation: A cultu…
Today I wanted to ask if any professionals know of a any good paying contracts that may not yet be advertised, as I am looking for my next contract. I can start straight away. Related Post On Stupidity – Outcome Driven Application Ar… The importance of analysis Sainthood in architecture False consensus effect
One of the fundamental concepts in enterprise architecture is the creation of a Future State that holistically embodies directional guidance for decision-making. The concept is often mis-understood and seems to have recently been lost in the noisy sea…
One of the fundamental concepts in enterprise architecture is the creation of a Future State that holistically embodies directional guidance for decision-making. The concept is often mis-understood and seems to have recently been lost in the noisy sea of conversations about models,…
In 2014, I recognized something was a bit off with all the big data excitement and I started interviewing companies to get to the bottom of it. In 2015, Ted Schadler and I published the first of my ideas in the report “Digital Insights Are The New Currency Of Business.” In that report, we pointed out what was wrong – big data only focused on how to turn more data into more insight. It didn’t say anything about how to turn that insight into more action. In that report we defined a system of insight, which focused big data energy on implementing insights in software using closed loops that create action and continous learning. In this year’s Top Emerging Technologies To Watch report, we evaluated sytems of insight technologies that were creating the most change, and we found many. For example:
Insight Platforms: Data management and analytics are not separate technologies anymore. Open source and cloud have made it so easy for vendors to combine these technologies into a platform – but things don’t stop there. Add insight-to-execution technologies like predictive model runtimes and you get a platform that is ideal for building closed-loop systems of insight. Our latest vendor and user surveys indicate that insight platforms are hot, hot. Expect to see more data and analytics tools merge into platforms this year.
In the previous post ‘Decisions, decisions…‘, I promised to list the tools for sensemaking, strategy, modelling, metagovernance and the like, for use in enterprise-architectures and similar fields, that I’ve been working on over this past decade or so. So here…
It is sometimes amazing that well paid architects are the last people to pay license fees for software and then arguing that the licenses should be free anyhow as all software companies make far than enough profits anyhow. Often I also hear that because of 5 projects that failed partial because the used a certain … Continue reading The missing logic with architects →
On April 5, 2016, Simon Fraser University hosted a live stream of Edward Snowden: Big Data, Security and Human Rights. The talk had Mr Snowden live streamed from Russia and a panel of experts on the stage at the Queen Elizabeth Theatre. The host was …
The underlying theme of my last post, “Babies, Bathwater, and Software Architects”, was that it’s necessary to understand the role of a software architect in order to understand the need for that role. If our understanding of the role is flawed, not just missing aspects of what the role should be focusing on, but […]
ArchiMate 3, at first glance, looks like a very orthodox IT-oriented enterprise architecture modeling langage. It can show how the business is supported (‘service-oriented’) by applications which are supported (‘service-oriented’) by infrastructure. This has been the Core of ArchiMate’s view … Continue reading →