In Adaptive or Hybrid Projects, Ongoing Feedback Is Critical

PMBOK v8 Definition

In projects that use adaptive or hybrid approaches, the need for ongoing feedback is greater because the project teams are exploring and developing product elements within specific increments due to ambiguity and complexity. Adaptive approaches—also referred to as change-driven or agile approaches—are useful when a project's requirements and technical solution are subject to a high level of uncertainty and volatility and are likely to change significantly throughout the project. A clear vision is established at the start, and initial known requirements are progressively elaborated, changed, or replaced in accordance with stakeholder feedback, the environment, or unexpected events.

Why It Matters for the Exam

This concept appears frequently in PMI exam questions about development approach selection, stakeholder engagement, and quality management. Questions typically test your understanding of why feedback loops are more intensive in adaptive/hybrid contexts versus predictive approaches, and how feedback drives iteration planning and backlog prioritization. Expect scenario-based questions where you must identify the correct response to a situation involving ambiguity, changing requirements, or stakeholder input during increments.

Key Points to Remember (for the exam)

• Core Reason for Greater Feedback Need: Ambiguity and complexity force teams to explore and develop product elements within specific increments—feedback validates direction and reduces uncertainty.
• Adaptive Approach Definition: Change-driven approach used when requirements and technical solutions have high uncertainty and volatility; requirements are progressively elaborated, changed, or replaced based on stakeholder feedback.
• Feedback Timing: Occurs at the end of each iteration, feeding directly into backlog prioritization for subsequent iterations.
• Life Cycle Structure: Adaptive life cycles follow: Define Project and Product Visions → Backlog Prioritization → Iteration → Feedback → Backlog Prioritization (repeat).
• Hybrid Approach Reality: Most projects today require a hybrid approach combining adaptive and predictive elements; relying solely on one approach is no longer sufficient.
• Feedback Purpose: Feedback enables teams to adjust to changing conditions, unexpected events, and evolving stakeholder needs within the controlled structure of increments.
• Team Skills Required: Adaptive approaches benefit from teams with strong communication, collaboration, and problem-solving skills to effectively process and act on ongoing feedback.

Typical PMI Exam Example

A software development project uses an adaptive approach to build a new customer relationship management system. The requirements are highly uncertain due to evolving market conditions. After the first two-week iteration, the product owner reviews the delivered increment and provides feedback that changes the priority of features in the backlog. The project team uses this feedback to replan the next iteration. Question: What is the PRIMARY reason the need for ongoing feedback is greater in this project? Answer: Because the team is exploring and developing product elements within specific increments due to ambiguity and complexity.

PMI Exam Traps

• Trap: Confusing ongoing feedback with "continuous stakeholder approval" of every task

  • Reality: Feedback is about validating increments and adjusting backlog priorities, not micro-managing daily work

• Trap: Thinking feedback replaces the need for a clear project vision

  • Reality: A clear vision is established at the start; feedback refines requirements within that vision

• Trap: Assuming hybrid approaches need less feedback than pure adaptive approaches

  • Reality: Hybrid approaches still require ongoing feedback for their adaptive components; feedback frequency depends on the level of adaptive contribution

• Trap: Believing feedback only happens at project completion

  • Reality: In adaptive approaches, feedback occurs at the end of each iteration and directly drives the next cycle's backlog prioritization

Important PMI Connections

Quick Review Questions

1. In an adaptive project, what happens to initial known requirements as the project progresses?
2. What is the relationship between iteration completion and backlog prioritization in an adaptive life cycle?
3. Why do most modern projects require a hybrid approach rather than purely adaptive or predictive?
4. What three team skills are especially important for adaptive approaches that rely on ongoing feedback?
5. At which point in the adaptive life cycle does feedback directly influence the next cycle's work?

PMBOK v8 Reference

Section 4.2.2 – Adaptive Approaches Section 4.3.3 – Organization Figure 4-6 – Life Cycle With an Adaptive Development Approach