Observation and Conversation for Requirements Elicitation

PMBOK v8 Definition

Observation and conversation provide a direct way of viewing individuals in their environment to see how they perform their jobs or tasks and carry out processes. This technique is particularly helpful for detailed processes when the people who use the product have difficulty or are reluctant to articulate their requirements. Observation is also known as "job shadowing," where an observer externally views a business expert performing a job.

This technique belongs to the Scope Management knowledge area and is used during the Collect Requirements process within the Planning Process Group.

Why It Matters for the Exam

The PMI exam frequently tests observation and conversation as a requirements elicitation technique because it addresses a critical project challenge: stakeholders who cannot or will not express their needs verbally. Expect questions that ask you to identify the appropriate technique when users are unable to articulate requirements, when processes are highly detailed, or when tacit knowledge must be captured.

Key Points to Remember (for the exam)

• Primary Purpose: Used when people who use the product have difficulty or are reluctant to articulate their requirements
• Alternative Name: Also known as "job shadowing"
• Method: External observer views a business expert performing a job
• Key Differentiator: Provides direct viewing of individuals in their environment
• Application Context: Particularly helpful for detailed processes
• Communication Aspect: Team members should be aware of how they express themselves through both what they say and what they do not say
• Nonverbal Component: Includes body language, gestures, tone of voice, facial expressions, mirroring, and eye contact

Typical PMI Exam Example

A project manager is eliciting requirements for a complex manufacturing process. The operators have performed the same tasks for 15 years but cannot explain every step in detail. Which technique should the project manager use?

Answer: Observation and conversation (job shadowing), because it allows direct viewing of how individuals perform their jobs when they have difficulty articulating their requirements.

PMI Exam Traps

• Trap: Confusing observation with prototyping

  • Reality: Observation watches users in their environment; prototyping creates a working model for feedback

• Trap: Thinking observation is only for external stakeholders

  • Reality: Observation applies to any business expert performing a job, including internal team members

• Trap: Assuming observation replaces interviews

  • Reality: Observation complements interviews; use observation when users cannot articulate requirements verbally

• Trap: Believing the observer should participate in the work

  • Reality: The observer is external and views the business expert performing the job; participation is not required

Important PMI Connections

Quick Review Questions

1. A project team is working with factory workers who have performed the same assembly process for 20 years. The workers cannot describe every step in writing. Which requirements elicitation technique should be used?

2. What is the alternative name for observation and conversation as defined in PMBOK v8?

3. When observing a business expert, what should team members be aware of regarding their own communication?

4. In which Process Group and Knowledge Area is the observation and conversation technique primarily used?

5. What makes observation and conversation different from interviews as a requirements gathering technique?

PMBOK v8 Reference

Section 5.2 - Collect Requirements (Scope Management Knowledge Area, Planning Process Group)