Creating Value with Agile

Insights and Experiences from a Senior Software Engineer

[Home]
[Summary]
[Resources]

The Agile development methodology has its roots in the formalization effort initiated in the 1970's to model programming concepts independently from their implementation. In the beginning of the 1990's there thus existed over 50 object-based approaches, but only three of them were widely adopted:

Starting in 1994 their authors decide to unify their approaches and in 1997 the OMG organization validates the UML formalization as an international standard (UML 1.1).

Agile
.. → OMT → UML → RUP →
TDD →
Lean
Scrum
XP
→ Kanban → ..

The Agile discipline was officialized in April 2001 with the publication of the Agile Manifesto; its main message is:

People, not processes, are the key to shipping a product.

Following the spirit of Agile developers should iteratively implement and integrate, inspect and adapt the software product they are responsible for.

Common criticisms include (see also Stephens's book "Extreme Programming Refactored"):

Articles

In this series of articles we present a survey of common Agile frameworks and report on our experiences as software developer and project manager under the light of the Agile development process.

Resources