Study guide
7.1 Agile Mindset & Values
Project Management Professional PMP
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Introduction & Fundamentals
1.1 About the PMP Exam 1.2 What is a Project? 1.3 Project, Program & Portfolio Management 1.4 The Project Manager Role 1.5 PMBOK 7 Principles Overview 1.6 Performance Domains Overview 1.7 What Changed in the July 2026 PMP Exam
2 Chapter 2: People Domain Part 1
2.1 Managing Conflict 2.2 Leading a Team 2.3 Supporting Team Performance 2.4 Empowering Team Members 2.5 Training & Development 2.6 Building a Team 2.7 Removing Impediments
3 Chapter 3: People Domain Part 2
3.1 Negotiating Project Agreements 3.2 Collaborating with Stakeholders 3.3 Building Shared Understanding 3.4 Engaging Virtual Teams 3.5 Defining Team Ground Rules 3.6 Mentoring Stakeholders 3.7 Emotional Intelligence
4 Chapter 4: Process Domain - Planning
4.1 Determining Project Methodology 4.2 Integrating Project Planning 4.3 Planning & Managing Scope 4.4 Planning & Managing Schedule 4.5 Planning & Managing Budget 4.6 Planning & Managing Quality 4.7 Planning & Managing Resources 4.8 Planning & Managing Procurement
5 Chapter 5: Process Domain - Execution & Control
5.1 Executing with Urgency for Value 5.2 Managing Communications 5.3 Assessing & Managing Risks 5.4 Engaging Stakeholders 5.5 Managing Project Changes 5.6 Establishing Project Governance 5.7 Managing Project Issues 5.8 Managing Project Artifacts 5.9 Knowledge Transfer & Closure
6 Chapter 6: Business Environment Domain
6.1 Planning & Managing Compliance 6.2 Evaluating & Delivering Benefits 6.3 External Environment Changes 6.4 Supporting Organizational Change
7 Chapter 7: Agile & Hybrid Approaches
7.1 Agile Mindset & Values 7.2 Scrum Framework 7.3 Kanban & Lean 7.4 Extreme Programming (XP) 7.5 Hybrid Project Management 7.6 Agile Planning & Estimation 7.7 Agile Metrics & Tools
8 Chapter 8: Predictive (Waterfall) Approaches
8.1 Predictive Lifecycle 8.2 Scope Management 8.3 Schedule Management 8.4 Cost Management 8.5 Quality Management 8.6 Risk Management Process 8.7 Procurement & Contracts 8.8 Change Control
7.1 Agile Mindset & Values
Key Takeaways Explain This Topic AI
The Agile Manifesto, created in 2001 by 17 software practitioners, defines four core values and twelve guiding principles
About 60% of PMP exam items use adaptive/agile or hybrid approaches under the 2026 Exam Content Outline, making this knowledge essential
The four Agile values prioritize individuals, working software, customer collaboration, and responding to change
Agile leadership emphasizes servant leadership, removing impediments, and empowering self-organizing teams
- The mindset shift from predictive to adaptive approaches requires embracing uncertainty and iterative delivery
- Last updated: October 2026
The Agile mindset represents a fundamental shift in how projects are approached, managed, and delivered. For the PMP exam, understanding this mindset is critical -- about 60% of exam items use adaptive/agile or hybrid approaches under the 2026 Exam Content Outline.
The Birth of Agile
In February 2001, seventeen software practitioners gathered at a ski resort in Snowbird, Utah. Frustrated with heavyweight, documentation-heavy methodologies that often failed to deliver value, they drafted a 68-word document that would transform project management: The Agile Manifesto .
These 17 signatories -- including Kent Beck, Alistair Cockburn, Jim Highsmith, and Jeff Sutherland -- became known as the Agile Alliance, which has grown to over 72,000 members worldwide.
The Four Agile Values
The Agile Manifesto states: "We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:"
Value Statement What This Means
Individuals and interactions over processes and tools People drive project success; tools are enablers, not solutions
Working software over comprehensive documentation Deliver functional products, not just plans and specifications
Customer collaboration over contract negotiation Build partnerships with stakeholders; adapt to their evolving needs
- Responding to change over following a plan Embrace change as a competitive advantage
- Critical Understanding
- The Manifesto states: "While there is value in the items on the right, we value the items on the left more."
This does not mean processes, documentation, contracts, and plans are unimportant. Rather, when forced to choose, Agile teams prioritize the items on the left.
The Twelve Agile Principles
The Agile Manifesto is supported by twelve principles that guide Agile practice:
Customer Value Principles
Early and continuous delivery : "Our highest priority is to satisfy the customer through the early and continuous delivery of valuable software."
Welcome changing requirements : "Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage."
Frequent delivery : "Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale."
Collaboration Principles
Business-developer collaboration : "Business people and developers must work together daily throughout the project."
Motivated individuals : "Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done."
Face-to-face communication : "The most efficient and effective method of conveying information to and within a development team is face-to-face conversation."
Technical Excellence Principles
Working software as progress measure : "Working software is the primary measure of progress."
Sustainable development : "Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely."
- Technical excellence : "Continuous attention to technical excellence and good design enhances agility."
- Simplicity and Self-Organization Principles
Simplicity : "Simplicity -- the art of maximizing the amount of work not done -- is essential."
Self-organizing teams : "The best architectures, requirements, and designs emerge from self-organizing teams."
Regular reflection : "At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly."
The Mindset Shift: Predictive vs. Adaptive
- Aspect Predictive (Traditional) Adaptive (Agile)
- Planning Comprehensive upfront planning Just-in-time, iterative planning
- Requirements Fixed at project start Evolve throughout project
- Change Controlled through formal process Welcomed as competitive advantage
- Delivery Single delivery at project end Incremental, continuous delivery
- Customer involvement Primarily at start and end Continuous collaboration
- Team structure Hierarchical, specialized roles Self-organizing, cross-functional
- Success measure On-time, on-budget, on-scope Customer value delivered
- Agile Leadership
Agile leadership differs fundamentally from traditional command-and-control management.
Servant Leadership
An Agile leader practices servant leadership , characterized by:
- Removing impediments : Clearing obstacles that slow the team
- Coaching : Helping team members grow their skills
- Facilitating : Enabling effective collaboration and communication
- Protecting : Shielding the team from external distractions
- Empowering : Trusting teams to make decisions
- Leadership Behaviors
- Traditional Manager Agile Leader
- Assigns tasks Facilitates self-assignment
- Makes decisions Enables team decisions
- Controls information flow Promotes transparency
- Manages individuals Serves the team
- Focuses on utilization Focuses on flow and value
- Why the Agile Mindset Matters for PMP
PMI recognizes that modern projects often operate in complex, uncertain environments where:
- Requirements evolve rapidly
- Technology changes constantly
- Customer needs shift
- Market conditions are volatile
The 2026 PMP exam update places even greater emphasis on adaptive, real-world project dynamics. Understanding the Agile mindset is no longer optional -- it's essential.
PMP Exam Tips
Questions often present scenarios where Agile values apply -- look for keywords like "collaboration," "iteration," "adaptation," and "customer value"
- Remember that Agile is a mindset first, not just a set of practices
- The Manifesto values the items on the left more , not exclusively
- Servant leadership is the default leadership style in Agile contexts
- Key Takeaways
- The Agile Manifesto defines four values and twelve principles created by 17 practitioners in 2001
- Agile is a mindset shift from plan-driven to value-driven project management
- Servant leadership replaces command-and-control management
- Understanding Agile is critical for about 60% of PMP exam items
- Change is viewed as a competitive advantage , not a threat