CPOA Requirements Elicitation 1 — Questions and Answers
Question 1: What is the primary goal of requirements elicitation in product ownership analysis?
- To write technical specifications for developers
- To discover, capture, and understand stakeholder needs and expectations (Correct answer)
- To build the initial product prototype
- To assign tasks to the development team
Correct answer: To discover, capture, and understand stakeholder needs and expectations
Requirements elicitation focuses on understanding what stakeholders need so those needs can be translated into actionable product requirements.
Question 2: Which elicitation technique involves observing users in their natural work environment?
- Brainstorming
- Ethnographic observation (Correct answer)
- Focus groups
- Prototyping
Correct answer: Ethnographic observation
Ethnographic observation (job shadowing or contextual inquiry) reveals how users actually work, uncovering implicit needs they may not articulate in interviews.
Question 3: What is the difference between stated and unstated requirements?
- Stated requirements are technical; unstated are business requirements
- Stated requirements are explicitly communicated; unstated are assumed or implicit expectations (Correct answer)
- Stated requirements come from users; unstated come from regulators
- There is no practical difference in elicitation
Correct answer: Stated requirements are explicitly communicated; unstated are assumed or implicit expectations
Stated requirements are directly expressed by stakeholders, while unstated requirements are implicit expectations that stakeholders assume will be met without saying so.
Question 4: Which elicitation technique is best for generating a wide range of ideas quickly from a group?
- One-on-one interviews
- Brainstorming (Correct answer)
- Document analysis
- Surveys
Correct answer: Brainstorming
Brainstorming encourages free-flowing idea generation in a group setting, quickly surfacing diverse perspectives without judgment.
Question 5: What is a 'use case' in requirements elicitation?
- A specific test scenario for QA
- A description of how a user interacts with the system to achieve a goal (Correct answer)
- A technical architecture diagram
- A prioritized list of features
Correct answer: A description of how a user interacts with the system to achieve a goal
A use case describes the interaction between an actor (user or system) and the product to achieve a specific goal, capturing functional requirements in a structured way.
Question 6: Why is active facilitation important during requirements workshops?
- To reduce the number of stakeholders needed
- To ensure all voices are heard and the session stays focused and productive (Correct answer)
- To replace the need for follow-up documentation
- To assign requirements to developers in real time
Correct answer: To ensure all voices are heard and the session stays focused and productive
Active facilitation manages group dynamics, prevents dominant voices from overshadowing others, and keeps discussions aligned with workshop objectives.
CPOA Requirements Elicitation 1
What is the primary goal of requirements elicitation in product ownership analysis?