CPOA Requirements Elicitation 2 — Questions and Answers
Question 1: What is a 'proto-persona' used for in requirements elicitation?
- A quick, assumption-based user archetype used before formal research is conducted (Correct answer)
- A detailed user profile based on extensive research
- A technical user role in the system database
- A placeholder for missing stakeholder information
Correct answer: A quick, assumption-based user archetype used before formal research is conducted
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?
- Interview
- Document analysis
- Prototyping (Correct answer)
- Survey
Correct answer: Prototyping
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?
- Interviews capture too many requirements
- Stakeholders may only share what they consciously know, missing implicit or observed needs (Correct answer)
- Interviews are too expensive to conduct
- They produce overly technical requirements
Correct answer: Stakeholders may only share what they consciously know, missing implicit or observed needs
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?
- Checking that code meets the requirements
- Confirming that elicited requirements accurately reflect stakeholder needs and business objectives (Correct answer)
- Approving user stories for a sprint
- Testing the product against the Definition of Done
Correct answer: Confirming that elicited requirements accurately reflect stakeholder needs and business objectives
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?
- It prioritizes backlog items by importance
- It helps uncover root causes behind stated needs to reveal true requirements (Correct answer)
- It measures stakeholder satisfaction levels
- It identifies the five most important user stories
Correct answer: It helps uncover root causes behind stated needs to reveal true requirements
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.
Question 6: What is the purpose of a 'requirements traceability matrix'?
- To map user stories to developer assignments
- To link requirements to their origins and track their fulfillment through development (Correct answer)
- To replace the product backlog in traditional projects
- To measure sprint velocity over time
Correct answer: To link requirements to their origins and track their fulfillment through development
A requirements traceability matrix traces each requirement from its source through design, development, and testing, ensuring all requirements are addressed.
CPOA Requirements Elicitation 2
What is a 'proto-persona' used for in requirements elicitation?