AEG believes that a proven methodology is the backbone to a successful implementation. Our approach blends the traditional Waterfall methodology with the flexibility of the AEGile process. The AEGile process is manifested by combining the traditional Design and Coding phases into one AEGile Design Phase. A control Prototyping control mechanism is deployed in this phase to limit the number of iterations allowed for the Design/Coding cycle.
Flexible deliverable - the content of the deliverable is dictated by the environment.
Flexible schedule - the deliverable may be required sooner or later than initially planned.
Small teams - each team has no more than 6 members. There may be multiple teams within a project
Frequent reviews - team progress is reviewed as frequently as environmental complexity and risk dictates (usually 1 to 4 week cycles). A functional executable must be prepared by each team for each review.
Collaboration - intra and inter-collaboration is expected during the project.
Object Oriented - each team will address a set of related objects, with clear interfaces and behavior.
Designed to be flexible throughout the development process
Provides for Control mechanisms for planning a project release and then managing variables as the project progresses
Enables the customer to adjust the deliverables throughout the project allowing for the most relevant release
Collaborative teams are able to share knowledge more easily
Object oriented technology provides the basis for the AEGile methodology
> Definition of a new release along with an estimate of its schedule and cost.
> New systems consists of both conceptualization and analysis.
> Existing systems consist of limited analysis
Application Architecture / Functional Design
> Design how the backlog items will be implemented. This phase includes system architecture modification and high level design
Sprints (Iterative Development Cycle)
> Develop – new release functionality
> Wrap – Close packets and create an executable release
> Review – with Development team daily and customer at pre-planned intervals to raise issues and resolve problems
> Adjust – Consolidate information gathered in Review into affected packets for resolution in next Sprint
> Backlog Management
> Release / Packet / Change Management
> Risk Management
> Issues Management
Preparation for release, including final documentation, pre-release staged testing, and release