PMP Eliciting and Documenting Requirements for the Delivery Approach

Requirements elicitation matters because poor scope often begins with poor discovery. PMP questions in this area usually test whether the project manager uses the right elicitation technique for the stakeholder context and the delivery approach instead of collecting requirements in a one-size-fits-all way.

Choose Techniques That Fit the Situation

Useful elicitation methods may include:

• interviews
• workshops
• observation
• prototypes
• backlog refinement
• document analysis

The stronger answer usually chooses the method that best reveals the needed information. Complex cross-functional ambiguity may need workshops. Sensitive stakeholder concerns may need interviews. Adaptive work may need iterative discovery instead of one large upfront session.

    flowchart TD
	    A["Stakeholder and delivery context"] --> B["Choose elicitation technique"]
	    B --> C["Capture and clarify requirements"]
	    C --> D["Document in a form the team can use"]
	    D --> E["Revisit and refine as needed"]

Documentation Must Match the Delivery Model

The exam often tests whether the project manager recognizes that elicitation and documentation are linked. Requirements should be documented in a way the project can actually use:

• predictive work may emphasize detailed requirement statements and traceability
• adaptive work may use features, stories, and acceptance criteria
• hybrid work may need both formal control points and evolving detailed backlog items

The weaker answer documents requirements in a form that does not support planning, validation, or delivery.

Example

A stakeholder group cannot describe its needs clearly in a standard requirements meeting, but reacts well to prototypes. The stronger move is to use prototype-driven elicitation rather than keep asking the same abstract questions.

Common Pitfalls

• Using the same elicitation method for every situation.
• Collecting requirements without clarifying ambiguity.
• Documenting requirements in a form the team cannot apply.
• Assuming initial elicitation is always final.

Check Your Understanding

Sample Exam Question

Scenario: A project team is trying to gather requirements for a new workflow tool. Stakeholders struggle to describe their needs clearly in interviews, but when shown simple prototypes they quickly identify missing functions and process pain points. The current requirements notes are too vague for the delivery team to plan against.

Question: What response best protects project outcomes?

• A. Use a more suitable elicitation approach, such as prototypes or facilitated workshops, and document the clarified requirements in a form the team can plan and validate against
• B. Continue interviews only, because changing the method would reduce consistency
• C. Stop elicitation and let the team decide the details
• D. Treat the current vague notes as final requirements

Best answer: A

Explanation: The strongest answer is A because PMP questions in this area reward method fit and usable documentation. If current elicitation is not producing clear, workable requirements, the project manager should adapt the approach.

Why the other options are weaker:

• B: Consistency is weaker than effectiveness.
• C: Team assumptions are not a substitute for elicitation.
• D: Vague notes weaken planning and validation.

Key Terms

• Requirements elicitation: The process of discovering stakeholder needs and expectations.
• Facilitated workshop: A structured group session used to clarify and align requirements.
• Usable documentation: Requirement documentation in a form the team can plan, build, and validate against.