Aggregated enterprise architecture wisdom
Gene Hughson This week’s episode of Tom Cagley’s Software Process and Measurement (SPaMCast) podcast, number 385, features Tom’s essay on Agile portfolio metrics, Kim Pries talking about the value of diversity, and a Form Follows Function installment on sense-making and decision-making in the practice of software architecture. Tom and I discuss my post “Architecture and OODA Loops […]
I’ve been following Tom Graves and his Tetradian blog for quite a while. His view of Enterprise Architecture (EA), namely that it is about the architecture of the enterprise and not just the enterprise’s IT systems, is one I find compelling. With some encouragement on Tom’s part, I’ve begun touching on the topic of EA, […]
From my very first post, I’ve been writing on the subject of “accidental architecture”, which is also sometimes confused with “emergence”. From the picture on the right (which I used previously on a post titled “Accidental Architecture”), it should be easy to infer what my opinion is in regard to the idea that coherent system […]
“Customer-centricity” is one of the biggest tags in the tag cloud to the right. My first post this year was “Is 2016 the Year for Customer-Focused IT?”. It’s a concept that I find vitally important to IT for the simple reason that to the extent that IT is not fit for purpose, it’s a waste […]
This week’s episode of Tom Cagley’s Software Process and Measurement (SPaMCast) podcast, number 381, features Tom’s essay on Agile adoption, Kim Pries talking about technology’s gender gap, and a Form Follows Function installment on the fallacy of greenfield development. Tom and I discuss my post “The Seductive Myth of Greenfield Development”. We talk about how […]
Consider this Tweet for a moment. I’ll be coming back to it at the end. In my last post, I brought up Twitter’s rumored changes to the timeline feature as a poor example of customer awareness in connection with an attempt to innovate. The initial rumor set off a storm of protest that brought out […]
Two articles from the same site (CIO.com), both dealing with planned innovations, but with dramatically different results: “Report: Twitter’s algorithmic timeline may arrive next week” reports that rumors (or “rumors”) of Twitter switching from a chronological timeline to one curated algorithmically has led to an uprising under the hashtag #RIPTwitter. Twitter’s CEO, Jack Dorsey, has […]
There’s an old saying about what happens when you assume. The fast lane to asininity seems to run through the land of hubris. Anshu Sharma’s Tech Crunch article, “Why Big Companies Keep Failing: The Stack Fallacy”, illustrates this: Stack fallacy has caused many companies to attempt to capture new markets and fail spectacularly. When you […]
Over the past few months, I have touched on a variety of what might seem to be disparate topics: the need for architects (or at least architectural design), estimates, organizations as systems/enterprise architecture, customer-centricity, and IT management and governance. I suspect the trend will continue for a while, so it’s time for a post to […]
In my post “Architecture and OODA Loops – Fast is not Enough”, I stated that sense-making and decision-making were critical skills for the practice of software architecture. I further stated that I found the theories of John Boyd, particularly his OODA loop, useful in understanding and describing effective sense-making and decision-making. My conclusion was that […]
This week’s episode of Tom Cagley’s Software Process and Measurement (SPaMCast) podcast, number 377, features Tom’s essay on empathy, Kim Pries talking about the application of David Allen’s concepts for Getting Things Done, and the first Form Follows Function installment for 2016 on organizations and innovation. Tom and I discuss my post “Changing Organizations Without […]
Sense-making and decision-making are critical skills for the practice of software architecture. Creating effective solutions (i.e. the collection of design decisions that make up the product) is dependent on understanding the architecture of the problem. In other words, the quality of our decisions depends on the quality of our understanding of the context those decisions […]