CPOA Requirements Elicitation

Question 1

What is the primary goal of requirements elicitation in product ownership analysis?

Accepted Answer

To discover, capture, and understand stakeholder needs and expectations

Answer

Requirements elicitation focuses on understanding what stakeholders need so those needs can be translated into actionable product requirements.

Question 2

Which elicitation technique involves observing users in their natural work environment?

Accepted Answer

Ethnographic observation

Answer

Ethnographic observation (job shadowing or contextual inquiry) reveals how users actually work, uncovering implicit needs they may not articulate in interviews.

Question 3

What is the difference between stated and unstated requirements?

Accepted Answer

Stated requirements are explicitly communicated; unstated are assumed or implicit expectations

Answer

Stated requirements are directly expressed by stakeholders, while unstated requirements are implicit expectations that stakeholders assume will be met without saying so.

Question 4

Which elicitation technique is best for generating a wide range of ideas quickly from a group?

Accepted Answer

Brainstorming

Answer

Brainstorming encourages free-flowing idea generation in a group setting, quickly surfacing diverse perspectives without judgment.

Question 5

What is a 'use case' in requirements elicitation?

Accepted Answer

A description of how a user interacts with the system to achieve a goal

Answer

A use case describes the interaction between an actor (user or system) and the product to achieve a specific goal, capturing functional requirements in a structured way.

CPOA - Certificate in Product Ownership Analysis Practice Test

CPOA - Certificate in Product Ownership Analysis Practice Test

CPOA Requirements Elicitation