Define An EA Process Organisation And Relationships

To do.


This Business Use Case / Capability describes a process to define EA process organisation and relationships.

For the EA Practice team to understand its own operational process, it is important that the team organisation is clearly defined. It is important to assign Roles to people on Activities and ensure all Activities for the Phase are 1) put into the Backlog, so that they can 2) covered at some point in one of the iterations in the Phase.

  • By considering and defining Phases, Milestones, Budgets, Resources, Activities, Roles and Work Products a high level plan can be framed, instantiated and run in the large.
  • The suggestion is to use this AgileEA set of Business Processes, Roles and Work Products as a starting point and refine it over time or tailor it to suit the needs of the practice.
  • Also define a Capability Maturity Model (these can be obtained on the internet and some are included for suggestion) and assess your current maturity level.
  • This assessment, when done by the whole team, helps bind a common understanding of the current team around the EA practice maturity.
  • Indirectly it sets a baseline and helps drive out common agreed areas for improvement.
  • Realizations of areas higher up the maturity ladder can be spotted for quick wins. E.g. “Oh, we already have and use a tool that supports Config Management, if we use it then we will get to level 3 on that particular score. So lets go for that?”
  • Identify where you want to get to by when in terms of maturity and use this to help guide the iteration planning and process establishment.
  • Also use these above structures to help define the Directory structure for saving files in EA, so that team members using a consistant directory structure early. This is the beginnings of defining a Configuration Management Plan, but only the absolute basics initially.



Unless otherwise stated, the content of this page is licensed under GNU Free Documentation License.