The agile methodology continues to be the key framework for software development projects. The implementation of agile has been a key factor in the technological revolution that has occurred over the last two decades.

The defining document termed the Agile Manifesto has been the guide for this innovation and has helped bring us to the modern age that we now live in.

The origin story

In 2001 a group of seventeen software developers met against the backdrop of the Wasatch Mountains, in Snowbird, Utah. They came together to discuss the future of software development. The group shared a common frustration with the way Software and IT projects were being planned and delivered.

They shared the frustration that Corporations were so focused on the planning and documentation of projects that it stifled the innovation necessary to produce products that had never been seen before. In fact, the high level of analysis, planning and documentation meant the key element of customer satisfaction was missing.

The group of developers who called themselves the Agile Alliance developed an online document that survives today. In the document the developer’s stated that the goal was not anti-methodology, rather “to restore credibility to the word methodology”.  

Another frustration was that Corporations were touting values such as “excellence” and “integrity” but this did little to help software developers to find a better way. Especially with the ground-breaking developments that were imminent.

The role of the meeting was not to rip up traditional frameworks, rather to find a balance between the existing ways of development and new alternatives. They admit to accepting the use of documentation but only if it has a beneficial use to the project. Flexibility and a culture of change were also viewed as important, as developers believed that excessive planning stifled the innovation necessary for such projects. The manifesto focuses on valuing interactions and individuals over processes and tools.

From this meeting a 68 word Agile manifesto was produced which was a defining moment in the software and IT industries but has also resonated in many industries since. The following values and principles have been used by countless corporations, individuals and teams since its introduction.

Four values

The Agile Manifesto introduced four values to uncover ways to improve software development. The manifesto emphasised that while there is value in the items on the right, they value the items on the left more.

The values are:

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan.

The manifesto also incorporated twelve principles that were very focused on the timely efficient and adaptability of software development.

It is interesting to note that Scrum, Kanban, Extreme Programming and Dynamic Systems Development Methods were all documented methodologies before the manifesto was formed.

However, all of these frameworks are now known as agile software development methods.

Who were the Snowbird 17 that became the Agile Alliance?

Kent Beck
Mike Beedle
Arie van Bennekum
Alistair Cockburn
Ward Cunningham
Martin Fowler
James Grenning
Jim Highsmith
Andrew Hunt
Ron Jeffries
Jon Kern
Brian Marick
Robert C. Martin
Steve Mellor
Ken Schwaber
Jeff Sutherland
Dave Thomas

The 12 Principles

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

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

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

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

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

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

Principle 7 – Working software is the primary measure of progress.

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

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

Principle 10 – Simplicity–the art of maximizing the amount of work not done–is essential.

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

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

The Agile Debate

The Snowbird 17 were successful in bringing together different approaches or frameworks in the development of software and IT projects. They did this by bringing together these methodologies into four key values and twelve principles.

With twenty years passed since the meeting in Utah, how has the Agile manifesto held up in light of the almost weekly introduction of new methodologies? It seems that everyone has their view on the way projects should be developed.

The beauty of Agile is its flexibility and its ability to be used in whole or part to add value to the project delivery. The experiences project practitioner will be able to assess what aspects of agile to bring into the project based on factors such as willingness of the project team, how much change anticipated through the project and also the built up learning within the organisation.

Agile has also morphed from the software and IT space into other areas of industry. These areas include product development, marketing campaigns, change management, design and

A great example of Agile in action outside of software and IT projects is the Lonely Planet travel guide organisation. In 2012 they adopted the Agile approach using whiteboards, task cards, stand up meetings and implementing weekly iterations.

Is the Manifesto Still Relevant?

Although Agile has morphed into many different versions the values and 12 core principles of the agile methodology still hold up. It is the foundation of the Agile conversation and frames the conversation around methodologies for fast paced, ever changing, dynamic projects.

So rather than re-writing the manifesto, maybe project practitioners should be focusing on how to bring in the essence of the document and apply it your own projects, project team or organisation. Use the built-up knowledge within your organisation and bring to life a culture that accepts change, reduces the amount of documentation, encourages collaboration and values individuals and interactions.