Master the collocations used when defining, committing to, and reviewing sprint goals in agile teams.
0 / 5 completed
1 / 5
At the start of sprint planning, the team needs to ___ a sprint goal that aligns with the product roadmap.
Define a sprint goal is the standard Scrum terminology. The sprint goal is formally articulated ('defined'), not invented or produced. 'Make up' has an informal or deceptive connotation.
2 / 5
The development team ___ the sprint goal during the planning meeting by agreeing on what they could deliver.
Commit to a sprint goal is the Scrum framework collocation — teams make a commitment to the sprint goal. 'Promise about' is ungrammatical. 'Agreed on achieving' is wordy. 'Swore to' is too informal and informal.
3 / 5
The team celebrated when they managed to ___ their sprint goal three days early.
Achieve a sprint goal is the correct collocation in Scrum. You 'achieve' or 'meet' a goal. 'Complete up' and 'finish off' are not collocations with 'goal'. 'End a goal' is semantically incorrect.
4 / 5
The team had to ___ their sprint goal mid-sprint after a major dependency was removed.
Revise a sprint goal is the correct Scrum term for adjusting the sprint goal when conditions change. 'Rewrite' implies a full replacement. 'Redo' is too informal. 'Change around' is not a standard collocation.
5 / 5
The product owner worked with stakeholders to ___ acceptance criteria for each user story.
Set acceptance criteria is the standard agile collocation. Acceptance criteria are 'set' or 'define' — they represent agreed conditions for 'done'. 'Write down' is too informal. 'Invent' and 'build' do not collocate with 'criteria'.