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 detailed user profile based on extensive research

Answer

A technical user role in the system database

Answer

A placeholder for missing stakeholder information

Question 2

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

Accepted Answer

Prototyping

Answer

Interview

Answer

Document analysis

Answer

Survey

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 too many requirements

Answer

Interviews are too expensive to conduct

Answer

They produce overly technical requirements

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

Checking that code meets the requirements

Answer

Approving user stories for a sprint

Answer

Testing the product against the Definition of Done

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

It prioritizes backlog items by importance

Answer

It measures stakeholder satisfaction levels

Answer

It identifies the five most important user stories

Question 6

What is the purpose of a 'requirements traceability matrix'?

Accepted Answer

To link requirements to their origins and track their fulfillment through development

Answer

To map user stories to developer assignments

Answer

To replace the product backlog in traditional projects

Answer

To measure sprint velocity over time