Agile Project Management Estimation Techniques 2

Question 1

In Planning Poker, why are Fibonacci-like numbers used instead of a linear 1-10 scale?

Accepted Answer

They reflect growing uncertainty as size increases

Answer

They are easier for managers to total

Answer

They force every story to be the same size

Answer

They map directly to calendar days

Question 2

A team consistently completes 30 story points per sprint. What is this measurement called?

Accepted Answer

Velocity

Answer

Capacity

Answer

Cycle time

Answer

Burn rate

Question 3

When should Planning Poker cards be revealed during estimation?

Accepted Answer

Simultaneously after everyone has chosen

Answer

One at a time starting with the most senior

Answer

Only by the Scrum Master

Answer

After the Product Owner approves each value

Question 4

Two developers reveal a 3 and a 13 for the same story. What should happen next?

Accepted Answer

They discuss the reasoning behind the extremes

Answer

Average the two to get 8

Answer

The higher estimate automatically wins

Answer

Skip the story and move on

Question 5

What does a story point primarily represent?

Accepted Answer

Relative effort, complexity, and uncertainty

Answer

Exact hours of coding time

Answer

The number of developers needed

Answer

The business priority of the item

Question 6

Why might a new team's velocity be unreliable for the first few sprints?

Accepted Answer

The team is still calibrating its shared sense of point sizing

Answer

Story points change value over time

Answer

Velocity only applies to mature products

Answer

Management hasn't approved the metric yet

Question 7

What is the main risk of converting story points directly into hours for stakeholders?

Accepted Answer

It reintroduces false precision and undermines relative estimation

Answer

It makes velocity increase

Answer

It improves estimate accuracy

Answer

It eliminates the need for sprints