Agile Project Management User Stories and Estimation 4

Question 1

What is an epic in Agile backlog terms?

Accepted Answer

A large body of work that can be broken into multiple stories

Answer

An epic is a large story too big for one sprint, decomposed into smaller stories.

Question 2

Why should story estimation involve the whole development team rather than just one person?

Accepted Answer

Diverse perspectives surface risks and produce more accurate estimates

Answer

Collective estimation captures different expertise and reduces individual bias.

Question 3

A product owner keeps adding implementation details to every story before the sprint. Which INVEST principle does this risk violating?

Accepted Answer

Negotiable

Answer

Stories should remain negotiable, leaving room for collaborative detail during the sprint.

Question 4

What is the purpose of using T-shirt sizes (S, M, L, XL) for estimation?

Accepted Answer

Quick, coarse-grained sizing especially for high-level backlog items

Answer

T-shirt sizing offers fast relative estimation useful for rough or early-stage planning.

Question 5

When splitting a story, which split typically delivers the most value?

Accepted Answer

A vertical slice delivering working end-to-end functionality

Answer

Vertical slices deliver usable, demonstrable functionality each iteration.

Agile Practice Test