Agile Ea Princples List
  • Aim to store single instance of the truth - the Enterprise knowledge - Just as all business these days stores all the business products, transactions and static data, so too should the base information about the enterprise and how it operates be stored such as office locations, Services, Compliance, Standards, Processes, Business Entites and Relationships, Applications, technologies, etc.
  • To be dynamic and responsive to business change - EA teams have to respond to the Business and IT to add value from day one. It for this reason that they plan their work well, manage by Risk and operate in an Agile and Iterative manner.
  • Learn to Crawl before you Walk before you Run - Because the practice of Enteprise Architecture is so immature in terms of standards and operational processes (not in age or concept), many teams fail because they try and run before they can even crawl. This principle drives this Agile EA Process, which tries to organise the dependencies, while still delivering value to the Enterprise.
  • Deliver value progressively - An Enterprise Architecture is a medium to long term endevour, akin to building up a puzzle. Initially the core pieces like the corner and edge pieces are found to create the context, but over time all the subtle pieces are gathered and put together to form an accurate picture of the ever changing Enterprise.
  • Adaptive over Predictive planning - Do allow for change, but do be disciplined and plan to fix what you know for a short period to get ahead and deliver value.
  • Simplify Complexity - Starting from an Extremely Coarse grained view across the enterprise, gather all the relevant Entities at the various Architectural levels into a single related model. Continuously baseline and improve these simple coarse grained models, so that all Projects trace to this central context. Iteratively refine these areas on each project and segments over time.
  • Drive Planning by Risk Management - By managing Risks (and Opportunities) the Enterprise Architecture team can steer a course through troubled seas by being pro-active and relevant.
  • ReUse over Buy over Build - Wherever possible make use of existing components which fit into the Architecture of the Enterprise. First Reuse existing building blocks, then purchase proven components, finally build what is required.
  • EA is an ongoing, sustainable and continuous business operation (not a finite piece of work) - While EA can be established as a specific project initiative, the essence of good Enterprise Architecture is to embedd certain principles at all levels of Architecture within the Enterprise and govern the Enterprise Architecture based upon these Principles. It is therefore just another Operation within the Enterprise and has to be sustainable and continuous. (It could be implemented as a series of un-interrupted and continuous back to back projects if necessary)
Unless otherwise stated, the content of this page is licensed under GNU Free Documentation License.