liveBook · Manning

Acceptance criteria

As explained in Build High Value Software Systems

Verifiable conditions that an output or implementation must satisfy to be considered acceptable.

Acceptance criteria are verifiable conditions an output or implementation must meet to be acceptable. Set them before work begins, then judge the result against the criteria rather than assumptions or memory. section 14.5 section 1.2.3

Make the conditions specific enough that different people would reach the same decision. For example, a refund-test prompt can require:

  • One test per business rule, with each test name stating the rule. section 14.5
  • No mocks, integration tests, or external dependencies; all tests run in under one second. section 14.5

For implementation work, treat clear acceptance criteria as an entry condition alongside an agreed architectural approach and a validated test environment. This helps prevent false starts caused by differing assumptions. section 1.2.3 section 1.2.4

Figure 14.4 The spec as the stable anchor in an AI-assisted workflow: the AI varies, the acceptance criteria don't.

The spec acts as a stable anchor when AI-generated output varies across model upgrades. section 14.5

How Build High Value Software Systems covers it

How deep it goes
Demonstrates concrete checks for generated tests and implementation readiness.
Examples
Uses refund-function tests and implementation entry checks as examples.
What you can do after
Evaluate generated output against explicit requirements and hold implementation until entry conditions are clear.
How it connects
Connects specifications, software testing, and pull-request readiness.

Also explained in

Compare how 9 books explain acceptance criteria →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Build High Value Software Systems. The section links point to the parts of the book it draws on.