nerdexam
PMI

CAPM · Question #116

A team was hired to develop a next generation drone. The team created a prototype and sent it to the customer for testing. The feedback collected was used to refine the requirements. What technique…

The correct answer is C. Progressive elaboration. Building a prototype, gathering customer feedback, and using that feedback to refine requirements is the iterative technique of progressive elaboration.

Adaptive Frameworks/Methodologies

Question

A team was hired to develop a next generation drone. The team created a prototype and sent it to the customer for testing. The feedback collected was used to refine the requirements. What technique is the team using?

Exhibit

CAPM question #116 exhibit

Options

  • AEarly requirements gathering
  • BFeedback analysis
  • CProgressive elaboration
  • DRequirements documentation

How the community answered

(30 responses)
  • A
    7% (2)
  • B
    3% (1)
  • C
    77% (23)
  • D
    13% (4)

Why each option

Building a prototype, gathering customer feedback, and using that feedback to refine requirements is the iterative technique of progressive elaboration.

AEarly requirements gathering

Early requirements gathering is not a recognized PMBOK technique and does not describe the iterative, prototype-based refinement process shown in the scenario.

BFeedback analysis

Feedback analysis is not a formally defined project management technique in the PMBOK Guide, and does not capture the iterative prototype cycle described.

CProgressive elaborationCorrect

Progressive elaboration is the iterative process of increasing the level of detail in a project plan as more information becomes available and requirements are better understood. Using a prototype to elicit customer feedback and then refining requirements based on that feedback is a textbook example of this technique. It acknowledges that requirements are not fully known at project start and are developed incrementally through customer interaction.

DRequirements documentation

Requirements documentation is an output artifact that records requirements, not a technique for eliciting or refining them through iteration.

Concept tested: Progressive elaboration through iterative prototyping

Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok

Topics

#Progressive elaboration#Requirements refinement#Iterative development#Feedback loops

Community Discussion

No community discussion yet for this question.

Full CAPM Practice