Agile Software-Development

Agile software development permits the writing, embedding and testing of new or modified functional requirements at any time, even during the final phases of a project.

Rigid phases involving cumbersome design processes are replaced with briefer, cyclical procedures. The goal is the early delivery of software packets that can be implemented at once, so that the practical feedback gathered at regular intervals from the client can be immediately channelled into further development.

Requirements are often unclear or incomplete at the inception of a project. This makes the use of an iterative-incremental process, by which fully-functioning and tested partial results are realized in short cycles, highly advantageous. Thus the functionality, and therefore the quality, of the entire software solution augment per iteration – as does the know-how of the project team. This enables the experience and knowledge gained from one cycle to contribute directly to the next.

Central aspects of agile software development are a clear structure and economical programming. Together with maximum reusability of resources this also involves the KISS-Principle: "Keep It Simple, Stupid", whereby the simplest solution should end up being the right one. But what does "simple" mean here? "The art of maximizing the amount of work not done" says one of the twelve principles of the Agile Manifesto!

Important elements of agile software development are Test-driven Development and Refactoring, as well as early user acceptance tests. Awkward errors such as incorrect or insufficient workflow transfer or poorly extendable program code can thus be avoided from the outset. The customer's advantage: slim and future-proof solutions that efficiently support their business processes – even when the goal posts have to be moved.

Read about how AOE media makes use of agile software development: Requirement-driven, flexible solutions instead of change requests!