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

To write technical specifications for developers

Answer

To build the initial product prototype

Answer

To assign tasks to the development team

Question 2

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

Accepted Answer

Ethnographic observation

Answer

Brainstorming

Answer

Focus groups

Answer

Prototyping

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 technical; unstated are business requirements

Answer

Stated requirements come from users; unstated come from regulators

Answer

There is no practical difference in elicitation

Question 4

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

Accepted Answer

Brainstorming

Answer

One-on-one interviews

Answer

Document analysis

Answer

Surveys

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 specific test scenario for QA

Answer

A technical architecture diagram

Answer

A prioritized list of features

Question 6

Why is active facilitation important during requirements workshops?

Accepted Answer

To ensure all voices are heard and the session stays focused and productive

Answer

To reduce the number of stakeholders needed

Answer

To replace the need for follow-up documentation

Answer

To assign requirements to developers in real time