The four values of the Agile Manifesto.
The Agile Manifesto consists of four key values:
Individuals and interactions over processes and tools.
Working software over comprehensive documentation.
Customer collaboration over contract negotiation.
Responding to change by following a plan.
In the past, many software teams focused on having the best possible tools or processes for building their software. The Agile Manifesto suggests that while those things are important, the people behind the processes are even more so.
Having the right group of individuals on your software team is vital to success. The best possible tools in the wrong hands are worthless. Perhaps even more important is how these individuals communicate with each other. The interactions between team members help them collaborate and solve any problems that arise.
Read more: 5 Important Types Of Agile Methodology
Previously, software developers would spend ages creating detailed documentation. That was before they even started writing a single line of code. And while documentation isn’t a bad thing, there comes a point when you should focus on providing your customers with working software.
The Agile Manifesto places shipping software to your customers among the highest priorities. You can then gather feedback to help you improve future releases.
You may want to read: Why Agile is a Game-Changer for Outsourced Software Projects
Once upon a time, contracts were king. You would draw up contracts with your customers, who would then detail the finished product. As a result, there was often a contrast between what the contract said, what the product did, and what the customer actually required.
According to the Agile Manifesto, the focus should be on continuous development. You need to build a feedback loop with your customers so you can consistently ensure your product works for them.
Can you imagine a time when you would draw up a roadmap that would never change? Well, in the past, that’s exactly what happened.
The trouble with static roadmaps is that we don’t live in a static world. Needs and requirements are always shifting, and priorities are always changing. That static roadmap will soon grow outdated.
That’s why the Agile Manifesto suggests that a software team should be able to pivot and change direction whenever needed, with a flexible roadmap that reflects this. A dynamic roadmap can change from quarter to quarter, sometimes even month to month, and agile teams can keep up with those changes.
The Agile Manifesto also consists of 12 principles. Read about them here.
In a no-risk discovery we look at how your work moves between your systems today and show what one connected system would do differently. You pay only if you proceed. Or see how we approach it.
More on the same problem:
Why Agile Development Will Dominate in 2025 and What It Takes (article)
Understanding the Value of UX Research and What It Uncovers (article)
Seventeen software practitioners wrote it in February 2001 at a meeting in Snowbird, Utah. They came from different lightweight methods of the time, including Scrum and Extreme Programming, and agreed on four values and twelve principles they shared. The document is short, deliberately, and has not been changed since. It is published online with the original signatories' names.
No. The manifesto says the items on the right have value; the items on the left have more. Documentation that helps people build, use and maintain the software is worth writing. Documentation produced to satisfy a process, which nobody reads and which is out of date on delivery, is what the value argues against. Working software is the measure of progress; documents support it.
With difficulty, which is why the third value favors collaboration over contract negotiation. A fixed scope and price assume requirements will not change. Agile teams working under such contracts usually agree a change process that lets the client swap a story of equal size rather than add one, keep the client in sprint reviews, and treat the contract as a budget envelope rather than a feature list.
The four values state what the authors prize more and less. The twelve principles make them concrete: deliver working software frequently, welcome changing requirements, business people and developers working together daily, sustainable pace, simplicity, self-organizing teams and regular reflection. Teams often quote the values and skip the principles, but the principles are where the practical guidance lives.
Yes, though the industry around it has changed. Frameworks, certifications and tools have grown up that sometimes contradict the first value by putting process ahead of people. The values themselves still describe what separates teams that ship useful software from those that produce plans. Reading the original is a useful corrective to any framework that has become ceremony.
"Something isn't working." "We're outgrowing our tools." "We're afraid to make the wrong move." No-Risk Discovery is a short, practical conversation that gets you clarity before you commit to anything big. We'll tell you if we're a fit. If we're not, we'll tell you that too.
Say who you are and ask. A person replies within one business day.