Agile Business Analysis FREE Agile Business Analysis User Stories and Modeling Questions and Answers 2

Question 1

Which technique helps an Agile team decompose a large user story (epic) into smaller, independently deliverable pieces?

Accepted Answer

Story mapping

Answer

Gantt charting

Answer

Critical path analysis

Answer

Work breakdown structure

Question 2

In the INVEST criteria for well-formed user stories, what does the 'N' stand for?

Accepted Answer

Negotiable

Answer

Necessary

Answer

Nominal

Answer

Non-functional

Question 3

What is the primary purpose of a persona in Agile business analysis?

Accepted Answer

To represent a fictional but realistic end-user archetype

Answer

To define system architecture constraints

Answer

To document regulatory compliance requirements

Answer

To assign tasks to specific team members

Question 4

When using the 'Given-When-Then' format for acceptance criteria, what does the 'Given' clause specify?

Accepted Answer

The precondition or initial context before the action

Answer

The action performed by the user

Answer

The expected outcome after the action

Answer

The non-functional performance requirement

Question 5

Which modeling technique uses a simple grid to show how different user roles interact with various system features?

Accepted Answer

Role-feature matrix

Answer

Sequence diagram

Answer

Entity-relationship diagram

Answer

Data flow diagram

Question 6

What distinguishes a spike from a regular user story in Agile?

Accepted Answer

A spike is time-boxed research to reduce uncertainty, not to deliver production code

Answer

A spike must always be completed within a single sprint

Answer

A spike replaces the need for acceptance criteria

Answer

A spike is used only for bug fixes