CST Agile Estimation Techniques & User Stories

Question 1

What is the primary advantage of using story points rather than hours for estimating in Scrum?

Accepted Answer

They enable relative estimation that is team-specific and avoids time-pressure anchoring

Answer

They satisfy stakeholder reporting requirements more efficiently

Answer

They align with PMI estimation standards for project management

Answer

They allow the Product Owner to assign work to individual developers

Question 2

Why does Planning Poker typically use a Fibonacci-like sequence (1, 2, 3, 5, 8, 13) rather than a linear scale?

Accepted Answer

The increasing gaps reflect growing uncertainty in larger estimates

Answer

The Scrum Guide mandates this sequence for all estimation activities

Answer

The sequence ensures no single story can exceed one Sprint in duration

Answer

It was chosen because all Agile coaches agreed it produces the most accurate results

Question 3

During Planning Poker, two team members consistently submit very different estimates. What is the BEST action for the Scrum Master to take?

Accepted Answer

Facilitate a discussion so both team members share their reasoning

Answer

Average the two estimates and record the result to keep the session moving

Answer

Ask the higher estimator to lower their card to avoid inflating velocity

Answer

Escalate to the Product Owner to cast the deciding vote

Question 4

Which of the following best describes a well-formed User Story?

Accepted Answer

A short, simple description of a feature from the perspective of the person who desires it

Answer

A detailed specification document reviewed and approved by the Product Owner

Answer

A technical task assigned to a specific developer in the Sprint Backlog

Answer

A Scrum artifact that replaces the traditional requirements document

Question 5

What does the 'I' in the INVEST acronym for well-formed User Stories stand for?

Accepted Answer

Independent

Answer

Integrated

Answer

Important

Answer

Incremental

Question 6

What is the recommended action when a User Story is too large to complete within a single Sprint?

Accepted Answer

Split it into smaller stories that each individually deliver value

Answer

Extend the Sprint length to accommodate the larger story

Answer

Assign the story to multiple team members working in parallel without splitting it

Answer

Convert it to an Epic and defer it to a future Program Increment

Question 7

A team consistently over-commits in Sprint Planning and fails to complete all selected items. What is the most likely root cause?

Accepted Answer

The team's velocity calculation is not accounting for overhead, meetings, and interruptions

Answer

The Product Owner is violating Scrum by adding items to the Sprint mid-cycle

Answer

The Scrum Guide recommends teams take on slightly more work than they can complete

Answer

Story points are an inherently inaccurate estimation technique that should be replaced