โ† All CPOA Flashcard Decks

Requirements Elicitation Flashcards

6 cards from real CPOA practice questions. Tap to flip, then mark Knew It or Still Learning โ€” missed cards come back until you master them.

Read the first 6 Requirements Elicitation flashcards as text
  1. What is a 'proto-persona' used for in requirements elicitation?

    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.

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

    Answer: Prototyping

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

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

    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.

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

    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.

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

    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.

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

    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.