CAD Agile Planning and Estimation Questions and Answers Flashcards

A team is estimating a complex integration story. Three developers estimate 8 points while two estimate 13 points. What should happen next in Planning Poker?

Answer: The highest and lowest estimators explain their reasoning, then the team re-estimates

When estimates diverge in Planning Poker, the outliers discuss their reasoning to surface hidden assumptions before the team votes again.

What is the concept of 'yesterday's weather' in agile planning?

Answer: Using the team's most recent sprint velocity as the best predictor for the next sprint

Yesterday's weather assumes the team's recent past performance is the most reliable indicator of near-future capacity.

Which factor should NOT directly influence story point estimates?

Answer: The number of hours a specific developer needs

Story points measure relative complexity, effort, and uncertainty of work, not individual developer hours.

During sprint planning, the team has a velocity of 40 points but the product owner wants 55 points of work committed. What is the best response?

Answer: Commit to 40 points based on historical velocity and let the product owner reprioritize

Teams should commit based on proven velocity and let the product owner prioritize the most valuable items within that capacity.

What is the main benefit of using a product backlog burndown chart during release planning?

Answer: It visualizes remaining work against time to forecast the likely release date

A release burndown chart shows how quickly the team is working through the backlog, enabling data-driven release date forecasting.

When should a team re-estimate previously sized backlog items?

Answer: Only when the team gains significant new information that changes the perceived complexity

Re-estimation is warranted when new information materially changes the team's understanding of the work involved.