Aggregated enterprise architecture wisdom
It’s time to review our EA practices and make amendments to the core frameworks and processes to face the challenges emerging from technology mega trends (Cloud/Mobile) and evolving business models (emerging markets). Continue reading →
Two weeks ago, Ruth Malan (@ruthmalan) of Bredemeyer Consulting and contributing author to the Cutter Consortium commented in her online journal (being maintained since 2006 and recommended!) that between the metaphor used by Tom Graves (@tetradian) in Agility Needs a … Continue reading →
Several people, including Nigel Green, Doug Newdick and Kris Meukens, picked up on my comments about architecture versus design in my earlier post ‘Great conversations on enterprise-architecture‘. Nigel kindly wrote a follow-up post on his Posterous blog, and Kris pointed to an earlier blog-post of his own, whilst Doug also added useful comments to both of those […]
Title inflation/mis-direction is vermicious. Like a Knid.
As technology architecture professionals, we can only be successful and valuable to those who pay us if we frame our work in terms of capabilities at the outset. If we start with details, we’ll ultimately fail.
The basic question I’m exploring visually here is “Is there another perspective to be found using the BMCanvas by Alexander Osterwalder at any orientation?” For the Architect (whatever prefix is used Business/Enterprise/IT) relating to the concept of different orientations may help in focusing the effort on the areas most important to the sponsor. The value […]
As the IT environment has changed significantly over the past several years, members of the Security Forum saw a need to revisit the document, Enterprise Security Architecture, and to update the guidance contained in it to address changes including mob…
Merely putting SOA into your proposal or as a stated capability is no longer going to be a “deal clincher” or a key “business differentiator”. The counterview I hear practitioners in SOA will say is that SOA is not just the standardized service…
A new technical report and a Quick Reference Guide exploring the synergies and identifying integration points between Frameworx and TOGAF® has been published by The Open Group and TM Forum. Continue reading →
An architecture for a solution requires understanding the problem at hand well enough that solving it can be described in terms that everyone understands. The architect speaks in terms of capabilities, not products.
What would it take for your business to view IT as a valuable, essential partner instead of an annoying cost-center that they’re forced to deal with? Wouldn’t that be better for you and better for them?
Just been reading (via Tweet by Bill Ives) a post by Anne Marie McEwan on ‘Loosening the Taylorist Stranglehold on the Workplace‘. Within a much larger context in a very good article, this one brief section caught my attention:
The Japanese concept of ‘ba’ came up in one of the face-to-face conversations. … Nonaka et al say that […]