Agile Business Analysis Agile Business Analysis-FREE Agile Business Analysis 1

Question 1

Which Agile artifact serves as the single authoritative source of work for the development team, containing all features, enhancements, and bug fixes?

Accepted Answer

Product backlog

Answer

The product backlog is the single authoritative, ordered list of everything that might be needed in the product. It is owned by the Product Owner and serves as the sole source of requirements for any changes to be made to the product.

Question 2

In Agile business analysis, what is a 'spike' used for?

Accepted Answer

To timeboxed research or investigation to reduce uncertainty on a technical or business question

Answer

A spike is a timeboxed activity used to research an uncertainty or explore a solution so the team can better estimate or implement a future story. It produces knowledge rather than shippable product.

Question 3

What is the primary difference between a user story and a use case in Agile business analysis?

Accepted Answer

User stories focus on the user's goal and value in plain language; use cases describe detailed system interactions and flows

Answer

User stories capture WHO wants WHAT and WHY in simple language, intentionally leaving details for conversation. Use cases describe step-by-step actor-system interactions in more formal detail. Both capture requirements but at different levels of abstraction.

Question 4

During iteration planning, the Agile business analyst's key responsibility is to:

Accepted Answer

Clarify requirements and acceptance criteria so the team fully understands each story before committing

Answer

The business analyst's primary role in iteration planning is to serve as the bridge between business needs and the development team — answering questions, clarifying acceptance criteria, and ensuring stories are ready ('Definition of Ready') so the team can commit confidently.

Question 5

Which of the following best describes 'Definition of Ready' (DoR) in Agile business analysis?

Accepted Answer

A set of conditions a user story must meet before the team pulls it into a sprint

Answer

The Definition of Ready is a shared agreement on the minimum conditions — such as clear acceptance criteria, estimated size, and no blocking dependencies — that a backlog item must satisfy before the team will bring it into a sprint for development.

Agile Business Analysis Practice Test

Agile Business Analysis Practice Test

Agile Business Analysis Agile Business Analysis-FREE Agile Business Analysis 1