Aggregated enterprise architecture wisdom
By A.J. Merlino, Associate VP of student professional development & Experiential Learning at Harrisburg University of Science and Technology In this article, I explore Ishikawa diagrams and how they can help identify the root cause […]
Earlier this year I promised a slew of research on FinOps. Today, I published the first in this series on What Technology Executives Need To Know: FinOps. This report is especially timely as FinOps is getting a front row seat with executives globally …
Part I appeared here on Monday. By Tim Green National Defense University The Washington D.C.-based university’s College of Information and Cyberspace offers a four-course architect certificate and an eight-course enterprise architect certificate. Click…
Lambert Finds Success Guiding Companies Down a Path of Digital Transformation To say Daniel Lambert keeps a busy schedule would be a massive understatement. Among the many companies the business architect represents are Business Architecture […]
By Scott Ambler, Consulting Methodologist, Ambysoft Inc. In Agile Architecture for Software Development Teams: Doing Agile I described a collection of techniques for agile architects, one of which is active stakeholder participation. As agilists we […]
By Gunnar Menzel Agility is a central requirement for many organizations. For organizations looking for a digital future, the question is no longer whether an agile innovation should be used, but which innovation, when, and […]
What Topics Will You Be Covering At Forrester? I am part of the Technical Architecture and Delivery Service. I will be authoring research for the “Lead A High Performing Enterprise Architecture Practice” priority. Briefly said I will help clients to be…
We recently asked Daniel Hutley, The Open Group Architecture Forum Director, about the potential of a global recession and the impact it could have on companies and their approach to technology. Question: If there is […]
(Editor’s Note: What follows is Part 11. Part I appeared yesterday.) By Greg Matthews Subject matter expert (SME) over-utilisation Most Enterprises have application owners that oversee and approve any changes to their allotted application(s). What […]
(Editor’s Note: What follows is Part 1. Part II appears tomorrow.) By Greg Matthews Many enterprises operate what is essentially a stone age-based IT lifecycle process. “Stone age” means that it is stuck at the […]
Functionality in retail and corporate banking is not highly differentiating anymore. In the future, only those that can support partner solutions in their ecosystem seamlessly can fully cope with banking industry’s expanding requirements.
By Kees van den Brink, Senior Manager Platform Architect, ServiceNow.
This blog title is derived from the famous quote by George E.P. Box from his paper “Science and Statistics”:
Box made this statement in relation to the use of statistical models by scientists, but I’ve found that it applies equally well to the use of open standards by enterprise architects and other digital practitioners.
Key take away from this blog:
o Standards can be useful when you:
o Learn and adopt from what makes sense
o Reject what does not fit
o Want to know more: Read “The Turning Point: A Novel about Agile Architects Building a Digital Foundation”
Frankly, standards can be very helpful and are necessary, like the TCP/IP standard, or even old standards such as the Baudot Code (https://en.wikipedia.org/wiki/Baudot_code), which helped early instances of what would later be called telecommunications companies grow fast, or the ISO Standards, which help with interoperability.
However, there are a lot of lesser-known standards that are not getting such broad adoption. Examples that come to mind are the IT4IT™ Standard, TOGAF® Standard, BIZBOK®, etc.