Becoming Enterprise Agile

Share it on Twitter  
Share it on Facebook  
Share it on Linked in  
Slide Show

10 Elements to Look for to Identify Agile Enterprise Integration Software

There's obviously a lot of interest in agile application development these days, especially as the economy recovers and companies start to revitalize their operations.

But the rush to embrace agile development is starting to tear at the fabric of the structured application development processes that companies rely on. To address this issue, Oracle is starting to position the Oracle Application Integration Architecture (AIA) as a framework for managing software development artifacts regardless of the methodology used to develop that particular piece of code.

Tim Hall, Oracle senior director of product management, says that when it comes to methodologies, Oracle has no particular ax to grind. The company is squarely focused, he says, on accelerating the application development process, as evidenced by the new version 3.1 of AIA that includes a raft of integration templates for various vertical industries and support for Oracle Fusion Middleware 11g.


Regardless of the methodology, Hall says it's a simple process to publish an artifact to the Oracle Repository, from which the organization can govern the overall process without getting in the way of the developers. Hall says that Oracle describes this as becoming "enterprise agile" in the sense that rapid application development and good governance practices are not mutually incompatible.

In the final analysis, developers want the satisfaction of creating code that actually does something. Every management task that gets in the way of that goal is, in their minds, corporate overhead that is somebody else's problem. The trick is to keep it that way because once it becomes the developer's problem, it's almost guaranteed that you won't like how they went about solving it.