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
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?
- A developer creates new feature based on full context, not only several short ACs.
- A QA checks the whole card and its context against what is actually done, not the ACs part of the card.
- 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
The text next to checkbox is changed from “Remember this card” to “Save card for one-tap pay”
- When a user opens checkout, the system checks if the user has a saved card.
- If the user has a saved card, the system shows it first among the payment methods.
- The saved card is selected by default.
- When the user taps “Pay”, the system charges the saved card without asking for card details.
- If the user has no saved card, the system shows the card form.
- The card form has the checkbox “Save card for one-tap pay”, unticked by default.
- When the user fills in the form and taps “Pay”, the system charges the card.
- If the checkbox is ticked and the payment succeeds, the system saves the card.
- If the payment fails, the system does not save the card and shows the error.
- After a successful payment the system shows the confirmation screen.
- When a user opens checkout, the system checks if the user has a saved card.
- If the user has a saved card, the system shows it first among the payment methods.
- The saved card is selected by default.
- When the user taps “Pay”, the system charges the saved card without asking for card details.
- If the user has no saved card, the system shows the card form.
- The card form has the checkbox “Save card for one-tap pay”, unticked by default.
- When the user fills in the form and taps “Pay”, the system charges the card.
- If the checkbox is ticked and the payment succeeds, the system saves the card.
- If the payment fails, the system does not save the card and shows the error.
- After a successful payment the system shows the confirmation screen.
Risks
- Changes. Your links to sources should point to a specific version. You can do it both in Figma and in Confluence.
- 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.
— Aliaksei