Acceptance tests for a Sprint Goal

Second half: There is no reasonable expectation of it being achieved in the first half of the Sprint, otherwise it may not be encompassing enough. If your team is regularly completing Sprint Goals early, consider having shorter Sprints!

Connective-free: It doesn't contain connectives such as the word 'and', commas, semicolons, slashes, etc.

Obviable: It has the potential to become obsolete. A Sprint Goal that cannot be invalidated is likely be too vague and not targeted at a specific enough use case. Also consider whether the team are engaging with the customer community to know when the market has moved on.

Negotiable: The team can reconfigure items on the Sprint Backlog (drop them, swap them) and still achieve the Sprint Goal.

Egalitarian: It can be verified by anyone on the Scrum Team as having been achieved. It may not be objective enough if it requires the subjective opinion of the PO.

#CreamFirst