Agile estimation sessions have their own professional vocabulary. Learn the collocations for pointing stories, discussing divergent estimates, tracking velocity, splitting large tasks, and accounting for uncertainty in sprint planning.
0 / 5 completed
1 / 5
The team agreed to ___ the story using Fibonacci numbers to indicate relative complexity rather than absolute time.
Point the story is the Agile-specific collocation for assigning story points during planning poker. 'Estimate the story' is broader; 'score' sounds like grading; 'rate' implies comparison. 'Point a story' or 'point stories' is the natural verb used by Agile teams during estimation sessions.
2 / 5
A significant gap in estimates usually signals that team members have ___ assumptions about the scope.
Divergent assumptions is the natural collocation in Agile estimation language. 'Different assumptions' is accurate but informal; 'conflicting' implies opposition; 'mismatched' suggests a pairing problem. 'Divergent' captures the spread in understanding that planning poker is designed to surface and discuss.
3 / 5
After the estimation session, the scrum master updated the ___ velocity to reflect the team's sustainable pace.
Average velocity is the standard Agile collocation for the baseline used in sprint planning. 'Planned velocity' is what you forecast; 'target velocity' is a goal; 'expected velocity' is looser. 'Average velocity' is the technical term for the historical measurement used to plan sprint capacity.
4 / 5
Stories larger than 13 points were typically ___ into smaller tasks before entering the sprint backlog.
Split into smaller tasks is the natural Agile collocation for decomposing large stories. 'Broken down' is also idiomatic; 'divided' is mathematical; 'separated' implies disconnection. 'Split stories' or 'split into smaller tasks' is the standard Scrum and Kanban language for story decomposition.
5 / 5
The facilitator reminded the team to account for ___ when estimating stories with external API dependencies.
Account for uncertainty is the natural collocation in estimation and risk discussions. 'Account for risk' is also used but broader; 'account for unknowns' is informal; 'complexity' is a factor you estimate, not account for separately. 'Uncertainty' is the precise Agile term for estimation variance caused by incomplete information.