CPOA Requirements Elicitation 2

Question 1

What is a 'proto-persona' used for in requirements elicitation?

Accepted Answer

A quick, assumption-based user archetype used before formal research is conducted

Answer

A proto-persona is a provisional user archetype created from assumptions and early insights when there is insufficient time or data for full research-based personas.

Question 2

Which elicitation technique involves presenting a working or simulated version of the product to gather feedback?

Accepted Answer

Prototyping

Answer

Prototyping presents a tangible representation of the proposed solution, enabling stakeholders to interact with it and provide concrete, actionable feedback.

Question 3

What is the risk of relying solely on stakeholder interviews for requirements elicitation?

Accepted Answer

Stakeholders may only share what they consciously know, missing implicit or observed needs

Answer

Interviews capture what stakeholders can articulate, but may miss implicit assumptions, workarounds, or unarticulated pain points visible only through observation.

Question 4

What is 'requirements validation' in the context of product ownership?

Accepted Answer

Confirming that elicited requirements accurately reflect stakeholder needs and business objectives

Answer

Requirements validation ensures the documented requirements are correct, complete, and aligned with what stakeholders actually need before development begins.

Question 5

How does the 'Five Whys' technique contribute to requirements elicitation?

Accepted Answer

It helps uncover root causes behind stated needs to reveal true requirements

Answer

By repeatedly asking 'why,' the Five Whys digs beneath surface-level requests to expose the underlying problem or need the requirement is meant to address.

CPOA - Certificate in Product Ownership Analysis Practice Test

CPOA - Certificate in Product Ownership Analysis Practice Test

CPOA Requirements Elicitation 2