There was an error in this gadget

Saturday, May 9, 2009

The Agile Manifesto..and the principles behind it..

For anyone who is starting to work on Agile SW Development, or already managing an Agile Projects, this is where it should all start...even if you have never heard of Agile but have been in Software Development, you'll immediately understand why Agile has become the "catchphrase" now...

First the MANIFESTO ()

"We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value
:

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan


That is, while there is value in the items on
the right, we value the items on the left more
."

And now for the 12 principles behind the Manifesto (equally powerful ...if not more)

1) Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software.

2) Welcome changing requirements, even late in
development. Agile processes harness change for
the customer's competitive advantage.

3) Deliver working software frequently, from a
couple of weeks to a couple of months, with a
preference to the shorter timescale.

4) Business people and developers must work
together daily throughout the project.

5) Build projects around motivated individuals.
Give them the environment and support they need,
and trust them to get the job done.

6) The most efficient and effective method of
conveying information to and within a development
team is face-to-face conversation.

7) Working software is the primary measure of progress.

8) Agile processes promote sustainable development.
The sponsors, developers, and users should be able
to maintain a constant pace indefinitely.

9) Continuous attention to technical excellence
and good design enhances agility.

10) Simplicity--the art of maximizing the amount
of work not done--is essential.

11) The best architectures, requirements, and designs
emerge from self-organizing teams.

12) At regular intervals, the team reflects on how
to become more effective, then tunes and adjusts
its behavior accordingly.

Here's my 2 Cents to this: Take your time and read the manifesto and the principles several times(atleast 10 attempts) and try to assimilate or challenge each of these based on your experience...you'll realize that these ring the right bells in your mind..

That would be a right start for your move towards "Agile Reincarnation"...

1 comment:

Anonymous said...

Can you provide more details on the principles behind the manifesto?