The Agile Manifesto

In John Stenbeck’s book “PMI-ACP® and Certified Scrum Professional Exam Prep and Desk Reference”, he talks briefly about the origins of Agile Methodology, in particular the development of the Agile Alliance that grew out of a seminal meeting of seventeen luminaries in the field of software development who met in the Snowbird resort in Utah in February 2001.    Out of that Agile Alliance came the Agile Manifesto, the Agile Principles, and the Ethos of Agile Project Management.   This post describes the Agile Manifesto, the immediate outcome of the first meeting of the Agile Alliance.

The Agile Manifesto

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

John Stenbeck mentions a key point, that the manifesto is saying that, while there is value in the terms on the right, Agile software development values the items on the left even more.

This key point is crucial, because many people interpret the Agile Manifesto incorrectly by thinking that it says “Individuals and interactions instead of processes and tools”, etc.  This couldn’t be further from the truth:   processes and tools have their place, but individuals and interactions have priority over them.

The Agile Alliance then published the philosophical background behind the Agile Manifesto, in the Agile Principles, which I will describe in my next post.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: