Requirements Elicitation Flashcards

What is 'scope creep' and how does it relate to requirements elicitation?

Answer: The uncontrolled expansion of project scope due to poorly managed or continuously added requirements

Scope creep occurs when requirements are added beyond the agreed scope without proper change control, often resulting from incomplete initial elicitation.

Which type of requirement describes what a system must do in terms of behavior or functions?

Answer: Functional requirement

Functional requirements specify the behaviors, functions, and capabilities the system must provide to meet user and business needs.

What are non-functional requirements (NFRs) concerned with?

Answer: Quality attributes such as performance, security, scalability, and usability

NFRs define quality standards and constraints the system must meet, such as response time, uptime, security standards, and accessibility.

What is the benefit of conducting requirements workshops with diverse stakeholder groups?

Answer: It surfaces conflicting priorities early and builds shared understanding across groups

Cross-functional workshops expose conflicting priorities and assumptions early, enabling alignment before costly development work begins.

What does 'requirements decomposition' mean in product ownership?

Answer: Breaking down high-level requirements into smaller, actionable components

Requirements decomposition breaks large, complex requirements (like epics) into smaller, more manageable pieces (like user stories) that can be estimated and delivered.

Why is it important to capture the 'as-is' state during requirements elicitation?

Answer: To understand current processes and pain points before designing the future-state solution

Understanding the current 'as-is' state reveals existing pain points, workarounds, and inefficiencies that the new product must address.