The Agile Manifesto: 4 Values and 12 Principles Every PMP Candidate Must Know

The Foundation of Everything Agile on the PMP Exam

The Agile Manifesto is the philosophical bedrock of agile project management. Written in 2001 by 17 software practitioners, it articulates four core values and twelve supporting principles that have reshaped how projects are managed worldwide. For the PMP exam, you need more than memorization — you need to understand how these values and principles guide decision-making in real project scenarios.

The Four Core Values

1. Individuals and Interactions Over Processes and Tools

This value prioritizes people and communication. A great team with mediocre tools will outperform a mediocre team with great tools. On the PMP exam, this translates to questions about team empowerment, face-to-face communication, and collaborative problem-solving. When a question offers a choice between implementing a new tool and improving team communication, the agile answer leans toward communication.

2. Working Software Over Comprehensive Documentation

The emphasis is on delivering functional results — not on producing extensive documentation for its own sake. This doesn't mean "no documentation." It means documentation should serve the product, not replace it. PMP questions may test whether you'd prioritize delivering a working increment over completing a detailed specification document.

3. Customer Collaboration Over Contract Negotiation

Agile favors ongoing partnership with customers over rigid contractual terms. The goal is to work with the customer to discover what they need, not to hold them to requirements they defined months ago. For the exam, this value appears in questions about stakeholder engagement, feedback loops, and how to handle changing requirements.

4. Responding to Change Over Following a Plan

This is perhaps the most misunderstood value. It doesn't say "don't plan." It says that when reality diverges from the plan, adapt the plan rather than forcing reality to match it. PMP questions frequently test this with scenarios where scope, priorities, or market conditions change mid-project.

The Twelve Principles

Principles 1-4: Delivering Value

1. Highest priority is satisfying the customer through early and continuous delivery of valuable software. The exam tests whether you prioritize delivering value early rather than waiting for a "big bang" delivery at the end.
2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Don't resist change — evaluate it.
3. Deliver working software frequently. Shorter delivery cycles (weeks rather than months) enable faster feedback and course correction.
4. Business people and developers must work together daily. Sustained, direct communication beats periodic handoffs of written documents.

Principles 5-8: Team and Environment

5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. This is servant leadership in action.
6. Face-to-face conversation is the most efficient method of conveying information. While the modern interpretation includes video calls, the core point is that rich, real-time communication beats asynchronous written exchanges.
7. Working software is the primary measure of progress. Not percentage complete, not documents produced, not hours logged — working, tested, deliverable functionality.
8. Agile processes promote sustainable development. Sponsors, developers, and users should maintain a constant pace indefinitely. No death marches.

Principles 9-12: Technical and Process Excellence

9. Continuous attention to technical excellence and good design enhances agility. Shortcuts today create technical debt that slows you down tomorrow.
10. Simplicity — the art of maximizing the amount of work not done — is essential. Build only what's needed. Avoid gold-plating.
11. The best architectures, requirements, and designs emerge from self-organizing teams. Trust the team to find the best solutions rather than dictating from above.
12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. This is the retrospective principle — continuous improvement is not optional.

Applying the Manifesto on the PMP Exam

When you face an agile scenario question, filter your options through the Manifesto's values. The correct answer will almost always align with valuing people, delivering working results, collaborating with customers, and adapting to change.

Explore how these principles connect to specific PMP topics in our comprehensive topics library.