Agile Manifesto: Principles and Values

The Agile Manifesto uncovers better ways of developing software by doing it and helping others do it. These are the values and principles.

In February 2001, 17 developers produced the “Agile Manifesto” for Agile Software Development at The Lodge at Snowbird ski resort in Utah.

The Agile Manifesto – Authors

 – Alistair Cockburn

 – Andrew Hunt

 – Arie van Bennekum

 – Brian Marick

 – Dave Thomas

 – James Grenning

 – Jim Highsmith

 – Jeff Sutherland

 – Jon Kern

 – Ken Schwaber

 – Kent Beck

 – Martin Fowler

 – Mike Beedle

 – Ron Jeffries

 – Robert C. Martin

 – Steve Mellor

 – Ward Cunningham

The Agile Manifesto – 4 Values

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

Note: while there is value in the items on the right, we value the items on the left more. In other words, one thing is not a substitute for the other.

The Agile Manifesto – 12 Principles

In the Agile Manifesto, some statements for the future of agile are shared:

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

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

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

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

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

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

Working software is the primary measure of progress.

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

Continuous attention to technical excellence and good design enhances agility.

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

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

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

I am incredibly grateful that you have taken the time to read this post.

Do you want to get new content in your Email?

Check my main categories of content below:

Navigate between the many topics covered in this website:

Agile Art Artificial Intelligence Blockchain Books Brazil Business Business Tales Career Coaching Communication Creativity Culture Cybersecurity Design DevOps Economy Emotional Intelligence Feedback Flow Focus Gaming Goals GPT Habits Health History Innovation Kanban Leadership Lean Life Managament Management Mentorship Metaverse Metrics Mindset Minimalism Motivation Negotiation Networking Neuroscience NFT Ownership Parenting Planning PMBOK PMI Politics Productivity Products Project Management Projects Psychological Safety Pulse Readings Routines Scrum Self-Improvement Self-Management Sleep Startups Strategy Team Building Technology Time Management Volunteering Work

Do you want to check previous posts about Project Management? Check these from the last couple of weeks:

Support my work by sharing my content with your network using the sharing buttons below.

Want to show your support tangibly? A virtual coffee is a small but nice way to show your appreciation and give me the extra energy to keep crafting valuable content! Pay me a coffee:

Leave a Reply

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