The Agile Manifesto
Introduction: Why This Matters
At the heart of Agile project management lies the Agile Manifesto, a declaration created in 2001 by seventeen software developers who sought a better way to deliver value in rapidly changing environments. It distilled Agile into four values and twelve guiding principles.
For the PMP exam, the Agile Manifesto is foundational because it underpins all Agile frameworks such as Scrum, Kanban, SAFe, and Extreme Programming (XP). In practice, it reshaped the way organizations deliver projects, shifting the focus from rigid processes to adaptive, people-centered value delivery.
Purpose and Objectives
Primary Purpose: To establish values and principles that prioritize adaptability, collaboration, and customer value over strict adherence to processes and documentation.
Key Objectives:
- Explain the four values of the Agile Manifesto.
- Recall the twelve Agile principles and their application to projects.
- Understand how Agile differs from predictive approaches.
- Apply Agile values to situational questions on the PMP exam.
- Recognize how Agile philosophy improves stakeholder satisfaction and adaptability.
Overview
This lesson breaks down what the Agile Manifesto is, what it prioritizes, and how it shows up in both PMP exam questions and real-world project decisions.
- Four Values: The trade-off priorities Agile uses when tension exists between people, process, documentation, contracts, and plans.
- Twelve Principles: The behaviors and operating mindset that make Agile “real” in day-to-day execution.
- Exam Application: How the PMP tests Agile philosophy through situational judgment questions.
Characteristics
- Value-first decision making: When trade-offs occur, Agile prioritizes collaboration, adaptability, and deliverable value.
- Continuous delivery mindset: Work is delivered in small, usable increments instead of “big bang” delivery at the end.
- Stakeholder partnership: Customers and stakeholders stay engaged throughout, not just during kickoff and sign-off.
- Human-centered execution: Motivated people, trust, and communication are treated as primary drivers of success.
Practical Example
Context: A university launches an online learning platform.
Activities:
- Predictive challenge: A traditional waterfall plan required a year of design before coding. Stakeholders became frustrated because they saw no progress.
- Agile solution: Using Agile values, the team prioritized working software over documentation, releasing a small but functional module within four weeks. Regular stakeholder feedback guided design improvements, while motivated, self-organizing teams adapted quickly to changing needs.
Outcome: Stakeholders gained confidence, students had early access to features, and the project delivered higher value sooner.
Common Pitfalls
Misusing Agile Principles
- Pitfall: Misinterpreting values as absolutes, treating Agile as “no planning” or “no documentation.”
- Prevention: Remember Agile still values planning and documentation. The values only clarify what gets priority when trade-offs happen.
Forgetting the Human Focus
- Pitfall: Relying on tools and ceremonies while neglecting trust, communication, and collaboration.
- Prevention: Reinforce daily collaboration and remove barriers so the team can deliver value consistently.
Applying Agile Without Context
- Pitfall: Forcing Agile onto projects with stable requirements and heavy regulatory or compliance constraints without tailoring.
- Prevention: Use a hybrid approach when needed. Tailor delivery method to risk, uncertainty, and stakeholder needs.
Skipping Retrospectives
- Pitfall: Ignoring continuous improvement, even though it is one of the core principles.
- Prevention: Hold consistent retrospectives and implement at least one concrete improvement each iteration.
Sensei Tip : When the exam gives you two “reasonable” options, choose the one that prioritizes collaboration, learning, and adaptable value delivery. That is the Agile Manifesto showing up in disguise.
Exam Alert : The Agile Manifesto values are not “anti-process” or “anti-documentation.” The exam loves to trap people who treat the right-side items as useless. Agile simply prioritizes the left-side items when trade-offs occur.
Exam Lens
Patterns on the PMP Exam:
- Expect situational questions that test Agile philosophy, especially collaboration, adaptability, and value delivery.
- Questions may contrast Agile versus predictive priorities to see which trade-off you choose.
- Look for answers that embrace change, seek feedback early, and keep stakeholders engaged throughout.
Sample Question
Question: A customer requests a major change late in development. The Agile team accepts it, even though it disrupts the plan. Which Agile value supports this action?
- Individuals and interactions over processes and tools
- Responding to change over following a plan
- Customer collaboration over contract negotiation
- Working software over comprehensive documentation
Correct Answer: B. Responding to change over following a plan.
Quick Recap Table
| Value | Focus | Exam Watch Point |
|---|---|---|
| Individuals & Interactions | People and teamwork | Do not undervalue tools, but prioritize people |
| Working Software | Deliver usable results | Not anti-documentation; value is simply higher |
| Customer Collaboration | Ongoing engagement | Not just upfront contracts |
| Responding to Change | Adaptability | Plans exist, but adaptation has priority |
Key Takeaways
- The Agile Manifesto is the philosophical foundation of Agile project management.
- Four values and twelve principles guide Agile practices.
- Agile emphasizes adaptability, collaboration, and early delivery of value.
- The PMP exam frequently tests whether you can apply Agile values in real scenarios.
- Agile does not eliminate predictive practices; it prioritizes flexibility when trade-offs arise.
Next Step
With the Agile Manifesto covered, we now proceed to Scrum, the most widely used Agile framework, to see how Agile principles are put into structured practice.
Bibliography
Agile Manifesto. (2001). Manifesto for Agile Software Development.