Agile Estimation Techniques & User Stories Flashcards

What best describes 'relative estimation' in the context of Agile?

Answer: Comparing items to each other to determine relative effort, complexity, or size

Relative estimation compares items against each other (e.g., 'this story is about twice as complex as that one') rather than assigning absolute time values, which tends to produce more consistent results.

What is a 'spike' in Agile, and what is its primary purpose?

Answer: A time-boxed research or exploration task designed to reduce uncertainty before estimation

A spike is a time-boxed effort to investigate a technical question or reduce uncertainty, allowing the team to make more informed estimates or design decisions on subsequent stories.

What does a 'Definition of Ready' (DoR) ensure about User Stories before Sprint Planning?

Answer: That User Stories meet agreed lightweight criteria making them clear and small enough to plan

The Definition of Ready ensures stories have met lightweight criteria — such as being small enough and having clear acceptance criteria — so the team can confidently plan and execute them in a Sprint.

T-shirt sizing (XS, S, M, L, XL) is best used for which estimation scenario?

Answer: Initial high-level estimation of many backlog items, especially when details are still uncertain

T-shirt sizing is a quick, relative estimation technique ideal for early-stage backlog grooming when items lack sufficient detail for precise story point estimates.

According to the INVEST criteria, what does 'Negotiable' mean for a User Story?

Answer: The story's scope and details can be discussed and adapted through team collaboration

Negotiable means a User Story is not a rigid contract; its scope and implementation details are open for collaborative discussion between the team and the Product Owner.

Why should the Developers, not the Product Owner, be responsible for estimating User Stories?

Answer: The Developers do the actual work and therefore have the most accurate understanding of effort

Since Developers perform the actual work, they have the deepest understanding of technical complexity, risk, and effort involved, making their estimates most accurate and credible.

What is 'affinity estimation' and when is it most effectively used?

Answer: A fast, silent group technique for sizing many backlog items by grouping similarly-sized items

Affinity estimation is a rapid, silent technique where team members group items by relative size, making it especially efficient for quickly sizing large backlogs without lengthy discussion per item.