Delivery Process: The EA Practice Lifecycle
When an EA practice is first started; the assumption is it starts with no collateral and is built up to a working department. This is the lifecycle that is followed from the early days and months of the EA Practice to instantiate it as a going and viable concern, through to the Architecture-as-usual iterations that keep it running effectivly.
DescriptionWork Breakdown StructureTeam AllocationWork Product Usage
Purpose
To build up an EA Practice centric View of collaboration of People, Roles, Work Products, Processes and Tools, with a common purpose, plan, vision and mission.
Relationships
Context
Properties
Event-Driven
Multiple Occurrences
Ongoing
Optional
PlannedYes
Repeatable
Staffing

Staffing is likely grow in the Practice (or Project) as it moved into the different successive phases. See individaul Phases for detail.

Key Considerations
  • It is important not to crawl (Inception) before you can walk (Elaboration) , and walk before you can run (Architecture-as-usual).  The Phases help you with this concept.
  • Do not dive directly into Project Segment Architecture work initially unless they add value to what you are trying to achieve in the Practice. Triage initially.
  • Each Phase sets guidelines on what level of Project work to take on versus Practice establishment work.

Current Version: 2007.0.030 (8th November 2007)  - built using EPF-composer v1.2.0.

Development and content by: 

Collaboration on much of the content so far from:

Early input

To get on this list - simply Collaborate on the AgileEA wiki - put forward comments and improvements on the content.