Study guide
4.1 Determining Project Methodology
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
4.1 Determining Project Methodology
Key Takeaways Explain This Topic AI
The three primary project methodologies are Predictive (Waterfall), Adaptive (Agile), and Hybrid, each suited to different project requirements and uncertainties
Predictive approaches work best for projects with stable, well-defined requirements and low uncertainty, while Adaptive approaches excel when requirements are volatile
Hybrid project management combines waterfall planning at the phase level with agile execution within phases, increasing flexibility while maintaining structure
According to PMI's 15th Annual Pulse of the Profession report, adoption of hybrid frameworks has surged by 57.5% over the past three years
Under the 2026 Exam Content Outline, about 40% of PMP items use predictive approaches and about 60% use adaptive/agile or hybrid approaches, across all domains
Last updated: October 2026
Selecting the right project methodology is one of the most critical decisions a project manager makes. This choice influences everything from how requirements are gathered to how deliverables are produced and validated. The PMP exam tests your ability to assess situations and recommend appropriate methodologies.
The Three Primary Methodologies
Methodology Also Known As Best For Key Characteristic
Predictive Waterfall, Traditional Stable requirements, well-understood projects Sequential phases with detailed upfront planning
Adaptive Agile, Iterative Volatile requirements, innovative projects Incremental delivery with continuous feedback
Hybrid Blended, Tailored Mixed requirements, complex environments Combines predictive structure with agile flexibility
Predictive (Waterfall) Approach
The Predictive approach follows a linear, sequential process where each phase must be completed before the next begins. It emphasizes comprehensive planning upfront and assumes requirements are stable and well-understood.
- Key Characteristics
- Sequential phases : Requirements, Design, Development, Testing, Deployment
- Detailed upfront planning : Complete scope definition before execution
- Change control : Formal process for managing changes
- Documentation-heavy : Extensive documentation at each phase gate
- Fixed scope, estimates time and cost : Scope is locked early
- When to Use Predictive
- Requirements are stable and well-defined from the start
- The technology is well-understood with minimal technical risk
- Regulatory or compliance requirements demand extensive documentation
- Stakeholders prefer defined milestones and deliverables
- Projects where changes are costly or risky (construction, manufacturing)
- Advantages and Limitations
- Advantages Limitations
- Clear structure and milestones Inflexible to changes
- Easier cost and schedule estimation Late testing discovers issues late
- Comprehensive documentation Customer sees product only at the end
- Well-suited for fixed-price contracts Assumes requirements are complete
- Adaptive (Agile) Approach
The Adaptive approach embraces change and delivers value incrementally. Work is organized into short iterations (sprints) that produce working increments of the product.
- Key Characteristics
- Iterative delivery : Working increments produced every 1-4 weeks
- Continuous feedback : Regular stakeholder involvement
- Embraces change : Welcomes requirement changes even late in development
- Self-organizing teams : Empowered teams make tactical decisions
- Fixed time and cost, flexible scope : Prioritize valuable features
- Common Agile Frameworks
- Framework Focus Typical Use
- Scrum Team structure and ceremonies Software development
- Kanban Flow optimization and visualization Operations, maintenance
- XP (Extreme Programming) Engineering practices Software quality
- SAFe Enterprise scaling Large organizations
- When to Use Adaptive
- Requirements are uncertain or expected to evolve
- Rapid delivery and early feedback are priorities
- Innovation and creativity are valued
- Customer collaboration is continuous
- Technology is new or changing rapidly
- Hybrid Approach
Hybrid project management blends predictive and adaptive approaches to leverage the strengths of both. According to PMI, hybrid means using high-level waterfall planning with agile execution of actual work.
- Key Characteristics
- Phase-level waterfall : Major phases are planned sequentially
- Iteration-level agile : Work within phases uses agile methods
- Flexible integration : Tailored to project and organizational needs
- Balanced documentation : Appropriate level for context
- Common Hybrid Patterns
Pattern Description Example
Water-Scrum-Fall Waterfall bookends with agile middle Requirements waterfall, development agile, deployment waterfall
Agile in Waterfall Agile teams within traditional structure Marketing works predictively, development works agile
- Iterative Waterfall Waterfall with iterative design Prototype iterations before development phase
- Phased Hybrid Different approaches per phase Planning predictive, execution agile
- When to Use Hybrid
- Some requirements are stable while others are uncertain
- Organizational culture is transitioning to agile
- Regulatory requirements demand some waterfall documentation
- Multiple teams with different working styles must collaborate
- Project spans both innovation and compliance work
- Methodology Selection Criteria
Selecting the right approach requires analyzing multiple factors:
Factor Analysis Table
- Factor Predictive Indicator Adaptive Indicator
- Requirements Stability Well-defined, unlikely to change Uncertain, expected to evolve
- Customer Availability Limited involvement after requirements Continuous collaboration
- Risk Tolerance Low tolerance for uncertainty Comfortable with experimentation
- Delivery Pressure Final delivery acceptable Need early, continuous value
- Team Experience Traditional project experience Agile experience and mindset
- Regulatory Environment Strict compliance requirements Flexible compliance needs
- Decision Framework
Assess Requirements Clarity : Can you define 80%+ of requirements upfront?
Evaluate Change Probability : How likely are significant changes?
Consider Customer Needs : Do they need early delivery or can they wait?
Analyze Organizational Readiness : Is the organization agile-mature?
Review Contractual Constraints : Do contracts mandate specific approaches?
- Project Life Cycle Models
- Predictive Life Cycle [Requirements] → [Design] → [Build] → [Test] → [Deploy] → [Maintain]
- Each phase completed before next begins
- Formal gate reviews between phases
- Changes require formal change control
- Iterative Life Cycle [Iteration 1] → [Iteration 2] → [Iteration 3] → [Final Product]
- ↓ ↓ ↓
- [Feedback] [Feedback] [Feedback]
- Multiple iterations refine the product
- Feedback incorporated between iterations
- Full product delivered at the end
- Incremental Life Cycle [Increment 1] → [Increment 2] → [Increment 3]
- ↓ ↓ ↓
- [Usable Subset] [Expanded Features] [Complete Product]
- Each increment delivers usable functionality
- Customer receives value progressively
- Risk reduced through early delivery
- Adaptive (Agile) Life Cycle [Sprint 1] → [Sprint 2] → [Sprint 3] → ... → [Sprint N]
- ↓ ↓ ↓ ↓
- [Working [Working [Working [Final
- Increment] Increment] Increment] Release]
- Short, fixed-duration sprints (1-4 weeks)
- Working software delivered each sprint
- Continuous refinement based on feedback
- Tailoring the Approach
The PMP exam emphasizes that project managers should tailor their approach rather than blindly following a single methodology. Tailoring considerations include:
- Organization's culture and values
- Industry standards and regulations
- Team size and geographic distribution
- Stakeholder expectations
- Project complexity and duration
- Available tools and technology
- Tailoring in Practice
Remember: There is no "one size fits all" methodology. Effective project managers assess each project's unique characteristics and adapt their approach accordingly. The key is to deliver value while managing risk appropriately for the context.
- Key Takeaways
- Predictive works best when requirements are stable and well-understood
- Adaptive excels when requirements are volatile and early feedback is needed
- Hybrid combines the best of both approaches for complex environments
Methodology selection should be based on requirements stability , customer needs , risk tolerance , and organizational readiness