Agile Manifesto: The 4 values and 12 principles explained

Editor’s note: This article was last updated on 23 January 2025.

The Agile Manifesto is the cornerstone of Agile product development, a professional framework that has redefined innovation far beyond its software origins. At its heart are four values and 12 principles that guide efficient software product development.

In this guide, we’ll explore what Agile means in practice, dive into the history of the Agile Manifesto, and then break down its four values and 12 principles to show how they apply to modern product development.

Before we get into the history of the Agile Manifesto and a detailed breakdown of how its tenets are implemented in practice, let’s start with the fundamentals — what are the core values and principles of the Agile Manifesto?

What are the 4 Agile Manifesto values?

The Agile Manifesto boils down to four key values that shape how teams work together, prioritize tasks, and adapt to change:

• Individuals and interactions OVER processes and tools
• Working software OVER comprehensive documentation
• Customer collaboration OVER contract negotiation
• Responding to change OVER following a plan

Here’s what they mean and how they look in action:

Individuals and interactions over processes and tools

Say a development team is working on a big feature for their app, but then an unexpected bug pops up. Instead of spending hours logging tickets in Jira, or waiting for a formal process to kick in, they huddle together — the developers, designers, and the PM all hash out a fix in real time.

Why this works — Tools and processes are good, but real conversations and teamwork solve problems faster and more effectively.

Working software over comprehensive documentation

Let’s say a small startup is working on building an MVP for their new fitness app. Instead of spending weeks perfecting every technical specification and user guides, they simply focus on building a prototype. Users test it, and they use these early customer insights to shape their next version. All the documentation is just built up along the way.

Why this works — A stack of untouched documents doesn’t work as well and delivers as much value as soon as a working prototype that’s under real feedback.

Customer collaboration over contract negotiation

Say a UX team is revamping their online fashion store. And midway through the project, they see, using usability testing, that the site’s navigation isn’t working for users. So, instead of sticking to the original scope outlined in the contract, they work with the client to tweak out the design. And they end up creating a better shopping experience that actually keeps customers engaged.

Why this works — It’s better to prioritize actual user needs and collaborate with clients than stick to previous rigid agreements and deadlines when needed. I’ve seen granular Gantt charts replaced with quarterly and monthly Gantt charts or higher-level Now-Next-Later roadmaps.

Responding to change over following a plan

Let’s say a SaaS company is working on developing a dashboard feature — but then a competitor launched something very similar to that, except with a twist. The product team quickly pivots ways and now focuses on features that set them apart. More likely that the end product shines this way, even if the original timeline took a hit.

Why it works — Being flexible helps stay ahead when the market or customer needs shift.

What are the 12 Agile principles?

To review and for quick reference, here are the 12 Agile Manifesto principles, in shorthand, explained with insights and examples:

1. Satisfy the customer

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

What does it mean?

This principle focuses on solving customer problems quickly and consistently by delivering value early and often. Instead of aiming for perfection, the goal is to get usable products or services into the hands of users to gather feedback and improve iteratively.

Say a food delivery startup starts by offering deliveries in only one small neighborhood. They use this first step to collect user feedback about speed, food quality, and customer service before they expand their reach or add more features. That’s a good use of this principle.

How to apply it:

• Focus on customers’ problems — Identify pain points and then build solutions that address them
• Build minimum viable products — Give something valuable to customers quickly
• Operate with minimum valuable processes — Get your workflows straightened out to speed up delivery
• Foster a culture of learning and iteration — Let your team know you value feedback as a gift, not as criticism

2. Welcome changing requirements

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

What does it mean?

Embrace uncertainty and change — even when it’s inconvenient or late. Markets constantly change, customer needs shift, and unexpected challenges arise. But to be competitive, not only should we anticipate change, we should welcome it.

An example would be a clothing brand that usually designs a fall collection, but then pivots to lighter fabrics after the year’s unseasonably warm weather changes customer demand.

How to apply it:

• Update sprint goals mid-sprint more frequently — Flexibility >>>
• Set the tone for adaptability — Show that changes are opportunities, not setbacks
• Celebrate pivots — Highlight successful adjustments to reinforce the mindset of celebrating changes
• Use continuous discovery habits — Stay attuned to changing markets and customer problems feedback

3. Deliver working software frequently

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

What does it mean?

Take baby steps. Focus on regular, incremental progress. Frequent releases reduce risk, provide quicker feedback loops, and consistently deliver value.

Think of how bakeries often introduce a new flavor of muffins each month based on customer feedback, instead of waiting to release a wholely overhauled menu.

How to apply it:

• Test how quickly your team can get a change live by making small changes — See how fast small adjustments, like a pricing tweak, can go live
• Break up stories into smaller pieces — Focus on smaller, manageable goals, such as shipping one feature at a time

4. Work together daily

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

What does it mean?

Agile thrives on collaboration. Teams — including business stakeholders — should have frequent touchpoints to ensure alignment and transparency. So, no matter who is involved, transparency and collaboration should be day-to-day normalcy.

Think of how a wedding planning company holds daily stand-ups with florists, venue coordinators, and caterers to ensure everyone is aligned with the client’s vision.

How to apply it:

• Invite stakeholders to team meetings — Create opportunities for non-tech teams like marketing or operations to stay informed and contribute
• Share accessible planning artifacts — Make planning and roadmap artifacts like kanban boards more accessible so everyone’s in the loop
• Bring in open communication — Use a shared Slack channel or informal check-ins

5. Build projects around motivated individuals

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

What does it mean?

There are a lot of words packed in the fifth agile principle. There’s motivation, environment, support, and trust — and individual people are at the center of it all.

A supportive environment will mean different things to different people. It comes down to knowing your team and how to communicate with and support the individuals within it.

You know how a restaurant manager trusts their chefs to create a seasonal special without micromanaging their recipe development process? That’s Agile Principle 5 in action.

How to apply it:

You might find this principle the most challenging because it cannot be isolated to a specific level in an organization. And then, as a product manager, your hands might be tied in many ways. But some things are always within your control. To improve the work environment as a manager, you can:

• Make work fun (whatever that means to you and your team)
• Get to know team members personally — Building trust starts with understanding each other
• Celebrate wins big and small — Publicly acknowledge achievements
• Establish a compelling product vision

6. Communicate face-to-face

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

What does it mean?

While written communication is useful, real-time conversations — whether in person or over video — lead to faster understanding and fewer misinterpretations.

How to apply it:

• Turn your video on — Encourage visual connection for remote teams
• Hold periodic in-person meetings — These will strengthen relationships
• Don’t be shy to jump on a quick call to hash something out in real-time (using Slack’s huddle feature, for example)
• When using text, sprinkle in emoji reactions to avoid any confusion about your tone

7. Measure progress by working products

Working software is the primary measure of progress.

What does it mean?

This principle can feel out of touch in a world where we value customer problem statements, fancy visual frameworks, user research, market research, analytics, and anthropology.

But real progress isn’t about perfect plans or presentations — it’s about delivering usable products or services that help users.

Think of how a fitness coach would track client success based on their performance metrics instead of written workout plans.

How to apply it:

• Build useful things now — Prioritize features or services that will solve problems immediately; document and plan as you go
• Double down on the first principle
• Review delivery cadence — Apply healthy pressure to teams by asking, “Have we actually helped customers lately?”

8. Maintain a constant pace indefinitely (marathons, not sprints)

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

What does it mean?

Agility means that burnouts, late nights, and last-minute emergencies should be rare. Agile teams prioritize sustainable workloads. Burnout and rushed projects just undermine long-term success.

How to apply it:

• Plan realistically and set achievable goals
• Build in breaks to ensure your team gets time to recharge between sprints

9. Pay continuous attention to technical excellence

Continuous attention to technical excellence and good design enhances agility.

What does it mean?

Vince Lombardi, the famed NFL head coach for whom the Super Bowl trophy is named, once said, “Perfection is not attainable, but if we chase perfection, we can catch excellence.”

Very in line with that, this principle suggests that quality should be a non-negotiable focus. Continuous improvement in processes and craftsmanship keeps work sustainable and competitive.

How to apply:

• Host lunch-and-learns and “brown bag” educational opportunities
• Build in time to incorporate tech debt into sprints
• Foster a culture in which team members are encouraged to maintain quality and sustainable implementations for longer-term agility

10. Keep it simple

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

What does it mean?

This phrase might seem counterintuitive at first glance and often strikes people as odd or unnecessarily confusing, but it’s actually pretty profound. Basically, it means less is more.

Maximizing the amount of work not done calls for a mental shift from doing more to doing less. Essentially, this means that you spend more time doing only what is necessary and waste less time complicating your processes.

How to apply it:

• Understand the reason and the vision for what you’re working on
• Focus on essentials — Use a light framework, such as MoSCoW or Needs vs. Nice-to-Haves, to prioritize must-haves
• Embrace minimalism — Look for straightforward solutions instead of overengineering

11. Trust your team to self-organize

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

What does it mean?

This isn’t about anarchy or some progressive operating model where people form their own clans and do whatever they want — remember, this statement was written in 2001.

Teams work best when given autonomy to plan and execute their work.

How to apply it:

• Create organizations of teams that are motivated and empowered. Train those teams on framing problems and divergent and convergent thinking
• Reduce micromanagement — Create teams that are cross-functional to minimize dependencies
• Reflect on how teams are measured and what behavior this encourages

12. Reflect and adapt

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

What does it mean?

Teams often run sprint retrospectives that are too predictable and too formal. Error. And there’s also often a lack of accountability. Too often, there is no follow-up or tracking of action items. Error.

I don’t believe every observation in a retrospective-like conversation needs to have an action item. Regularly evaluate how things are going, identify improvements, and adjust as needed.

How to apply it:

• Check-in regularly — Hold retrospectives to see what’s working and what isn’t
• Track action items and next steps — Follow up on agreed changes

Connecting the values and principles

The four core values of the Agile Manifesto aren’t just abstract ideas — they directly inform the 12 principles, giving us a framework for creating products and solving problems. I’ll now break down how each value connects to the principles.

1. Individuals and interactions over processes and tools

This value emphasizes the importance of people — team members, stakeholders, and customers. Processes and tools are helpful, but relationships drive innovation.

• Principles like working together daily (#4) and building around motivated individuals (#5) embody this. When teams collaborate effectively, magic happens

• The focus on face-to-face communication (#6) reinforces that meaningful conversations (whether in-person or virtual) beat long email threads or Slack messages any day

2. Working software over comprehensive documentation

It’s not about skipping documentation but about prioritizing what really matters — getting functional, valuable products into users’ hands.

• Principles such as delivering working software frequently (#3) and measuring progress by working products (#7) echo this value. The ultimate goal? Ship something real, even if it’s not perfect yet

• Keeping things simple (#10) also ties in — you focus on building what’s necessary instead of wasting time on overcomplicated processes

3. Customer collaboration over contract negotiation

This value reminds us that success comes from understanding and adapting to customers’ needs, not just sticking to a rigid agreement.

• Satisfy the customer (#1) through ongoing delivery and feedback loops. By doing so, you build trust and deliver more valuable products

• Welcome changing requirements (#2) because customer needs evolve. Staying flexible helps you create solutions that truly solve their problems

4. Responding to change over following a plan

Life happens, markets shift, and priorities change. This value is about staying adaptable and open to new ideas.

• Principles like maintaining a constant pace (#8) ensure your team isn’t burning out while reacting to change
• The idea of reflecting and adapting (#12) encourages regular self-check-ins to see what’s working and what’s not

Timeline: History of the Agile Manifesto

1960s–1970s: Early beginnings	Computers primarily served scientific needs; programming was slow, limited, and expensive, and primarily served scientific purposes rather than business needs Developers experimented with early methods, laying the foundations for future practices
1980s: The waterfall era	Waterfall methodology dominated with rigid, sequential stages like requirements, design, implementation, and testing Developers and businesses began to feel constrained by the rigidity and inefficiency of heavyweight processes
1990s: Lightweight frameworks emerge	Dissatisfaction with the rigidity of waterfall paved the way for frameworks like Scrum, Extreme Programming (XP), and Crystal Focus shifted to adaptability, collaboration, and faster delivery cycles
2001: Agile Manifesto is born	17 engineers frustrated with traditional methods, convened at the Snowbird ski resort in Utah; together, they created a bold declaration emphasizing individuals, working solutions, customer collaboration, and responsiveness to change Introduced four values and twelve principles, redefining software development forever
2000s: Agile adoption takes off	Scrum became the most popular framework Larger organizations adapted agile methods through frameworks like SAFe and LeSS Agile principles extended into areas like marketing, HR, and operations, showing their versatility
2010s: Agile becomes mainstream	Agile was no longer an “alternative” — it was the industry standard for software development Companies in finance, healthcare, and manufacturing industries embraced agile for faster innovation
2020s: Agile in the modern era	Remote work reshaped agile practices during the COVID-19 pandemic Agile now incorporates concepts like DevOps, design thinking, and continuous delivery, ensuring its relevance in an ever-changing landscape Modern agile emphasizes delivering business and customer value over adhering to specific frameworks

FAQs about the Agile Manifesto

What is the Agile Manifesto?

It’s a key document from 2001 that sets out core values and principles to guide agile software development, focusing on collaboration, flexibility, and delivering value.

What are the 4 values of the Agile Manifesto?

1. People and interactions over tools
2. Working software over heavy documentation
3. Customer collaboration over contract negotiation
4. Responding to change over sticking to a plan

What are the 12 principles of Agile project management?

Key principles include frequent delivery of value, embracing change, promoting teamwork, keeping things simple, and working at a sustainable pace. They help teams work effectively with agility.

What’s the purpose of the Agile Manifesto?

To offer a shared philosophy for software development, emphasizing adaptability, collaboration, and delivering real value to customers in a fast-paced world.

When was the Agile Manifesto published?

It was published in February 2001 by 17 software experts in Snowbird, Utah.

Who wrote the Agile Manifesto?

A group of 17 experts, including Kent Beck, Martin Fowler, and Jeff Sutherland, all pioneers in lightweight development methods.

Is the Agile Manifesto still relevant?

Absolutely! Its values still shape modern development practices, including DevOps, remote work, and continuous delivery.

What’s the difference between Scrum and the Agile Manifesto?

Scrum is a framework that follows agile principles, focusing on iterative cycles, roles, and ceremonies. The Agile Manifesto, on the other hand, is the guiding philosophy behind frameworks like Scrum, XP, and Kanban.

Is the Agile Manifesto still relevant today?

The Agile Manifesto has aged remarkably well. It still challenges both tech and business professionals to prioritize what really matters — flexibility, collaboration, and delivering value.

Its relevance extends beyond software development. Many industries, from marketing to human resources, have adopted Agile principles, often with just a few tweaks to references about “software.” This adaptation has helped teams across the board deliver outcomes more efficiently.

Despite countless alternatives, extensions, and even calls to replace the Agile Manifesto, it’s clear that the original document has stood the test of time. Critics often claim that Agile doesn’t work for every situation, but their arguments tend to overlook the fact that Agile isn’t a rigid framework — it’s a flexible mindset. While it may not be a perfect fit for highly regulated industries or large-scale enterprises, its core principles remain valuable.

Emerging trends and hybrid methodologies

Agile continues to evolve. The rise of DevOps is a prime example. By integrating development with operations, DevOps speeds up the development and delivery process. This synergy with Agile promotes faster, automated pipelines, making Agile even more relevant.

The shift to remote-first teams has also reshaped Agile practices. While Agile’s focus on collaboration and flexibility aligns well with remote work, it requires extra attention to communication tools, transparency, and trust.

Then, there are hybrid methodologies. Many organizations now blend Agile with waterfall, lean, and design thinking to create more customized approaches. These combinations allow teams to progress incrementally while still meeting the demands of larger, more complex projects. This is particularly useful in regulated industries like healthcare, finance, and government.

Even with all the new methodologies and critiques, the principles behind the Agile Manifesto continue to resonate. Flexibility, collaboration, and a focus on customer outcomes will always be in demand.

Any new manifesto would need to be groundbreaking to replace what Agile has already achieved.

Conclusion

Agile’s all about keeping things flexible, collaborative, and focused on real value. The values and principles are there to guide teams to build things that actually work for customers, adapt to changes, and keep everything moving at a steady pace.

Take these four points away:

1. People over processes — Collaboration and communication are key. Tools are great, but real interactions solve problems
2. Working software beats docs — Get that product out there early, test it with real users, and iterate
3. Customer collaboration is essential — Flexibility and collaboration with customers help build better products, not just sticking to a contract
4. Responding to change > sticking to a plan — Markets and user needs evolve. Embrace change and adapt on the fly

If you’re looking to dive deeper into Agile or want more resources to enhance your practices, check out our Agile-related articles on our blog. Happy Agile-ing!