← to blog

Are Acceptance Criteria a section of a backlog item?

From project to project I see that acceptance criteria for a PBI1 are in 99% of cases just a section in the task description. Those who write requirements add sections like User Story, links to designs or diagrams.

I don’t agree, and hear me out.

My take is that a ticket is a Card from the 3C model. So Conversation and Confirmation happen upon a ticket. While a physical card was limited (due to its physical nature), today’s card are not limited and must contain wider amount of context for a task. In other words, a card should contain ‘all necessary information to complete it’.2

Conventional View
Context why, what problem, for whom
🔗 Design, screenshot or flow
☑ Acceptance criteria
My View
Context why, what problem, for whom
Acceptance criteria
Design Knowledge base NFRs Scenarios Design system Screenshots

For me the must is Context. A description in any wording of why a card exists, what problem it solves and for whom. The rest can actually live somewhere outside the card: in a knowledge base, in a design system.

Then, I’d add a link to a design, a screenshot, or a flow. And the ACs.

Are ACs the only ACs? If you do not mention in ACs “The result follows the design” — but add a link inside the card or in a specific field — does it mean that there’s no such requirement? I think, the fact that there’s a link somewhere means that there’s a requirement and an AC!

Why do I think so?

  1. A developer creates new feature based on full context, not only several short ACs.
  2. A QA checks the whole card and its context against what is actually done, not the ACs part of the card.
  3. A visualisation may present the same info, but without text. We can use a variety of visualisation techniques to show a requirement, and any of them may be better than pure text: a clickable prototype, UML / BPMN, a screenshot with red-pen redlines showing what to do. If we limit ourselves to text, we ignore a very good way of communication.

Examples

As text
Acceptance criteria

The text next to checkbox is changed from “Remember this card” to “Save card for one-tap pay”

As a picture
Checkout
•••• •••• •••• 4242
Remember this cardSave card for one-tap pay
Pay $24

Risks

  1. Changes. Your links to sources should point to a specific version. You can do it both in Figma and in Confluence.
  2. Inertia. For decades people have thought that an AC is a short text describing a feature, while in fact it is something we use for judgement: accept or not.

An AC is anything you’ll use to accept or reject the work.

  1. Product Backlog Item. It is something you add to your task tracker. ↩

  2. Updated on 2026-10-08. ↩

— Aliaksei