CAD FREE CAD Agile Planning and Estimation Questions and Answers 2

Question 1

A development team consistently underestimates stories by 30-40%. Which technique would BEST help them improve estimation accuracy over time?

Accepted Answer

Track velocity trends and use historical data to calibrate future estimates

Answer

Assign estimation responsibility to the most senior developer only

Answer

Double all estimates to create a safety buffer

Answer

Replace story points with exact hour-based estimates

Question 2

During sprint planning, the Product Owner introduces a story that no team member has experience with. What is the MOST appropriate estimation approach?

Accepted Answer

Use Planning Poker and discuss assumptions before converging on an estimate

Answer

Skip estimating and commit to it anyway

Answer

Assign the highest possible point value automatically

Answer

Defer the story indefinitely until an expert joins the team

Question 3

What is the PRIMARY purpose of a release burndown chart in agile planning?

Accepted Answer

To visualize remaining work across multiple sprints toward a release goal

Answer

To track individual developer productivity metrics

Answer

To replace the need for sprint retrospectives

Answer

To assign blame for missed deadlines

Question 4

A team uses T-shirt sizing (XS, S, M, L, XL) for initial backlog estimation. What is the MAIN advantage of this approach?

Accepted Answer

It allows quick relative sizing of a large number of items without detailed analysis

Answer

It provides exact time estimates for project scheduling

Answer

It eliminates the need for sprint planning entirely

Answer

It guarantees accurate delivery dates for stakeholders

Question 5

In agile estimation, what does the concept of 'yesterday's weather' refer to?

Accepted Answer

Using the previous sprint's actual velocity as the forecast for the next sprint

Answer

Reviewing past project failures to avoid repeating mistakes

Answer

Checking external market conditions before planning

Answer

Adjusting estimates based on team member mood

Question 6

When should a team consider re-estimating previously sized product backlog items?

Accepted Answer

When significant new information emerges that changes the team's understanding of complexity

Answer

Every sprint regardless of changes

Answer

Only when the Scrum Master requests it

Answer

Never, because estimates should remain fixed once assigned

A development team consistently underestimates stories by 30-40%.Which technique would BEST help them improve estimation accuracy over time?

A development team consistently underestimates stories by 30-40%.
Which technique would BEST help them improve estimation accuracy over time?