Practise the collocations for estimating effort, breaking down tasks, sizing stories, and buffering for unknowns.
0 / 5 completed
1 / 5
Before committing to a delivery date, the engineering manager asked the team to ___ effort for each initiative.
Estimate effort is the standard project management collocation for assessing the amount of work required to complete a task or initiative. 'Guess along' and 'predict around' are informal. 'Calculate out' suggests false precision not applicable to estimation.
2 / 5
To make estimation more accurate, the team decided to ___ tasks into smaller, independently deliverable chunks.
Break down tasks is the standard project management collocation for decomposing large items of work into smaller, more estimable units. 'Split along' and 'divide around' are informal. 'Cut out' implies removal rather than decomposition.
3 / 5
The product team used story points in planning poker to ___ stories and align on complexity.
Size stories is the standard agile collocation for assigning a relative complexity measure to user stories during planning. 'Score along' and 'rate around' are informal. 'Weight out' is not a standard agile phrase.
4 / 5
The project manager advised the team to ___ for unknowns and not commit to an unrealistic timeline.
Buffer for unknowns is the standard project planning collocation for adding contingency time to estimates to account for uncertainty. 'Plan along' and 'allow around' are informal. 'Account out' is not a standard phrase.
5 / 5
After each sprint, the team tracked actual versus estimated hours to ___ estimation accuracy over time.
Improve estimation accuracy is the standard agile and project management collocation for refining a team's ability to predict effort over successive sprints. 'Increase along' and 'refine around' are informal. 'Correct out' does not convey continuous improvement.