Agile Manifesto Explained

Agile Manifesto Explained


Since I read the agile manifesto the first time, I was wandering if there is some higher order rational behind the four statements. Although they seem to cover different dimension, there is somethin in common.

Presence vs. Past

For me it looks like that the agile manifesto is basically about presence over past:

  1. Interactions/individuals are now – processes/tools originate from past decisions.
  2. Working software works now – comprehensive documentation is (mostly) out of date
  3. In customer collaboration you know his current requirement – a contract manifests past decisions
  4. A change is happening now – a plan is (mostly) out of date.

5 thoughts on “Agile Manifesto Explained

  1. Mirko,

    I think it is an interesting observation but I see some bias here that might not be justified. I think your arguments can be easily turned around in some points.

    For example – you write the documentation now, the working software will be produced in the future. A change is something that results from the past decisions whereas plans always look towards the future (ignoring for a minute that they might be out of date).

    I would suggest that it’s more about outcomes over processes, and outcomes are indeed positioned in the future.

  2. The manifesto can also be read as “… can substitute for …”

  3. @Marcin: Your trasnlation into presence -> future supports the same arrow of time:
    documentation -> (working) software,
    plan -> change.
    Therefore, it’s not that different from me saying past -> presence.

Leave a Reply

Your email address will not be published. Required fields are marked *