Backlog Grooming Prioritization Language Collocations
Practise the standard verbs for grooming and prioritizing a product backlog.
0 / 5 completed
1 / 5
Fill in: 'We ___ the backlog every sprint so a ticket opened months ago and no longer relevant doesn't just sit there cluttering every planning meeting.'
We 'groom a backlog' — the standard, established collocation for regularly cleaning up and refining a list of pending work. The other options aren't the recognised term here.
2 / 5
Fill in: 'Never grooming the backlog between sprints can ___ genuinely urgent work buried under hundreds of stale, half-relevant tickets nobody's touched in months.'
We say a neglected backlog will 'leave' urgent work buried — the standard, natural collocation for the resulting clutter. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ tickets by expected impact and effort together, rather than ranking purely by whoever raised their request the loudest in a meeting.'
We 'prioritize tickets' — the standard, simple collocation for ordering backlog items by a considered set of criteria. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ a vague ticket's effort as a team before it's scheduled into a sprint, so nobody discovers mid-sprint that a "quick fix" was actually a week of work.'
We 'estimate effort' — the standard, simple collocation for assigning an expected size to a piece of work. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ an oversized ticket into smaller, independently shippable pieces, rather than letting one sprawling task block an entire sprint's progress.'
We 'split a ticket' — the standard, established collocation for breaking a large piece of work into smaller units. The other options aren't the recognised term here.