How to write an Acceptance Criteria

Oscar de la Hera Gomez
<p>A flower that represents Project Management with the text “Acceptance Criteria” beneath it.</p>

A three step process to writing Acceptance Criteria.

An acceptance criteria, or AC, is the definition of done and defines the requirements for a feature, campaign, product, service, experience, user story, task, agile user story or subtask to be considered complete.

Step One: Write the User Story or Agile User Story

Define the task or subtask that you are trying to solve.

This step may be a part of the process of creating the Backlog or grooming the Backlog.

Step Two: Write the tests and requirements for completion

Write down the process that Quality Assurance must perform to guarantee that the task or subtask performs as expected.

These requirements should be:

  • Clear, so that everyone understands them.
  • Concise, so there's no ambiguity.
  • Testable by software tests or functional testing so that they can be verified.
  • Focused on the customer or end user.

Step Three: Confirm with Stakeholders

Meet with the client or member of leadership to verify that the criteria meets their desired outcome.

This may require you to update the task or subtask and that's OK.

Looking to learn more about Project Management, Technology and Strategy?

Search our blog to find educational content on project management, design, development and strategy.

Any Questions ?

We are actively looking for feedback on how to improve this resource. Please send us a note to inquiries@delasign.com with any thoughts or feedback you may have.
delasign logo

Book a Free Consultation.

An icon of an email.

Click here to email us.

Fill in the details below to book a free consultation or to let us know about something else. Whatever it is, we are here to help.

How can we help you ?

Contact Details