RSS Feed
Download our iPhone app
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.


Making Enterprise Architecture Work in Agile Environments

The perceived chasm between enterprise architecture and Agile Software Development can be bridged by leveraging the processes common to both.




Building the Right Environment to Support AI, Machine Learning and Deep Learning

A recurrent topic in meeting rooms and discussion groups is "Can enterprise architecture work in an Agile Software Development environment?" The question is so often asked that even those architects and developers who have already found the answer through personal experience stop to think about it. They wonder if perhaps they have missed something and need to re-evaluate their conclusions.

They likely haven't missed anything, but the fact that they even question their experiences is a testimony to the perceived chasm between the enterprise architecture (EA) and Agile disciplines. In fact, EA and Agile have great potential to work together to the benefit of architects, Agile developers and entire development organizations. This article helps define that potential.

Enterprise Architecture and Agile Development Viewpoints

Viewpoint is a key influence on perception. Many factors shape a viewpoint (which is a topic worthy of study in itself), but for the purpose of this discussion consider two broad viewpoints at the core of an individual's (or organization's) beliefs regarding EA and Agile:

  • The two disciplines are fundamentally similar.
  • The two disciplines are fundamentally different.

Let's take a close look at these in order.

EA and Agile Are Fundamentally the Same

EA and Agile share the following process:

  1. Review the current state of the solution landscape
  2. Elicit the desired state from business
  3. Determine the technical and non-technical gaps between the current and target states
  4. Take steps to narrow the gap by implementing one or more solutions towards the target
  5. Review the results of the implementation to choose the next step and revise (if necessary) the approach towards the target state

For those who believe that enterprise architecture and Agile Development are fundamentally different, the list above most likely presents a new viewpoint. Practitioners of either discipline agree that discovering a new viewpoint should trigger a re-evaluation of existing views. The new viewpoint also suggests that the accepted principles should be confirmed or expanded as necessary.

Comment and Contribute






(Maximum characters: 1200). You have 1200 characters left.



Thanks for your registration, follow us on our social networks to keep up-to-date