Engineering Velocity Metrics: English Collocations
Engineering velocity metrics like deployment frequency, lead time, change failure rate, and MTTR are central to modern engineering discussions. This exercise covers the natural collocations professionals use when reviewing, improving, and communicating these metrics.
0 / 5 completed
1 / 5
The engineering team wants to ___ deployment frequency as a DORA metric.
Measure deployment frequency is the standard collocation — engineering teams measure DORA metrics to track delivery performance. 'Calculate' implies a formula, 'assess' is more qualitative, and 'review' means looking at existing data rather than capturing it.
2 / 5
We need to ___ a baseline for lead time before we can track improvement.
Establish a baseline is the natural collocation in metrics discussions. You 'establish' a baseline as a reference point for future comparison — it implies formal recognition and agreement, which 'create' or 'build' do not carry in this context.
3 / 5
The team's change failure rate has been ___ for three consecutive sprints.
Declining is the preferred collocation with a rate metric in formal engineering discussion — it implies a sustained, meaningful trend. 'Dropping' sounds informal, 'falling' is more general, and 'decreasing' is accurate but less idiomatic in this engineering context.
4 / 5
Leadership asked us to ___ our MTTR target from two hours to thirty minutes.
Tighten a target is the natural engineering collocation — it implies making a goal more demanding or precise, not just numerically smaller. 'Reduce', 'lower', and 'cut' describe the number changing but miss the nuance of raising the performance bar.
5 / 5
We should ___ velocity trends over the last quarter before committing to the roadmap.
Analyse velocity trends is the professional collocation — it implies structured examination of data over time. 'Check' is too informal, 'inspect' suggests looking for defects, and 'watch' implies passive observation rather than active interpretation.