Learning Loop Playbooks Learning Loop

Engineering, Product management

Acceptance Criteria

The conditions that must be met for a product, service, or system to be accepted by a customer, end user, or other stakeholder

Also called: Acceptance Standards, Acceptance Requirements, Exit Criteria, Exit Requirements, Success Criteria, Success Requirements, Quality Criteria, Quality Requirements, Definition of Done, and Definition of Acceptance

See also: Acceptance Test Driven Development, Acceptance Test, Built-In Quality

Relevant metrics: Number of stories accepted and Number of stories with acceptance tests associated

In this article

What are Acceptance Criteria?

Acceptance Criteria are a set of conditions that must be met in order for a product or feature to be accepted by a customer, stakeholder, or user. It is a definition of the scope of a project or product, and outlines the requirements that must be fulfilled in order for the product or feature to be accepted. Acceptance Criteria is typically used in the context of Product Management and Product Ownership (Scrum), and is used to ensure that the product or feature meets the customer’s expectations. It is also used to ensure that the product or feature is of a high quality and meets the standards of the customer.

Acceptance Criteria are typically written in a clear and concise manner, and is used to ensure that the product or feature meets the customer’s needs and expectations. Example criteria are:

1. The system must be able to process customer orders accurately and efficiently.
2. The system must be able to store customer data securely.
3. The system must be able to generate reports on customer orders.
4. The system must be able to integrate with other systems.
5. The system must be able to provide customer support.
6. The system must be able to handle large volumes of data.
7. The system must be able to provide real-time updates on customer orders.
8. The system must be able to provide a user-friendly interface.
9. The system must be able to provide a secure payment gateway.
10. The system must be able to provide analytics and insights.

Where did Acceptance Criteria come from?

Acceptance Criteria is a term used in software development to refer to the criteria that must be met in order for a product or system to be accepted by the customer. The term was first used in the early 1990s by software engineers and project managers to describe the criteria that must be met in order for a product or system to be accepted by the customer. The term has since become widely used in the software development industry and is now used to refer to the criteria that must be met in order for a product or system to be accepted by the customer.

Understanding the Role of Acceptance Criteria in Software Development

Acceptance criteria are an essential part of software development, as they provide a clear definition of what is expected from the end product. They are used to ensure that the software meets the requirements of the customer, and that it is fit for purpose. Acceptance criteria are used to evaluate the quality of the software, and to ensure that it meets the customer’s expectations.

They are typically defined by the customer, and are used to evaluate the software against the customer’s requirements – to ensure that the software meets the customer’s needs, and that it is fit for purpose. The criteria should be specific and measurable, and should be based on the customer’s requirements.

Acceptance criteria are also used to evaluate the performance of the software. They are used to ensure that the software meets the customer’s performance requirements, and that it is fit for purpose. The criteria should be specific and measurable, and should be based on the customer’s performance requirements.

Acceptance criteria are an important part of software development, as they provide a clear definition of what is expected from the end product. They are used to ensure that the software meets the customer’s requirements, and that it is fit for purpose. The criteria should be specific and measurable, and should be based on the customer’s requirements. By using acceptance criteria, software developers can ensure that the software meets the customer’s expectations, and that it is fit for purpose.

Understanding the Role of Acceptance Criteria in Software Development

In a strict setting using Acceptance Criteria to its full extend, the development team would wait for acceptance criteria to be established before starting development. The criteria would then be used to guide the development process, ensuring that the product is built according to the customer’s specifications (or the Product Manager’s or Q&A’s expectations if no customer was involved). They can also be used to test the product, ensuring that it meets the customer’s requirements.

They provide a clear set of guidelines for developers to follow, ensuring that the product meets the customer’s expectations and requirements. By taking the time to define and document the acceptance criteria, developers can ensure that the product is of the highest quality and meets the customer’s needs.

Types of Acceptance Criteria

Acceptance criteria can be divided into two main categories:

  1. Functional criteria
  2. Non-functional criteria.

Functional acceptance criteria are related to the functionality of the product, such as whether it meets the customer’s requirements or performs certain tasks. Non-functional acceptance criteria are related to the quality of the product, such as its usability, reliability, and security.

When establishing acceptance criteria, it is important to involve all stakeholders, and possibly customers or users, in the process. This will ensure that all requirements are taken into account and that the criteria are realistic and achievable. Additionally, it is important to ensure that the criteria are measurable and testable, as this will help to ensure that the product meets the customer’s expectations.

Establishing acceptance criteria helps to reduce the risk of costly rework and delays, as any issues can be identified and addressed early in the development process. Additionally, it helps to ensure that the product is of high quality, as it sets clear expectations for the development team.

Benefits of establishing Acceptance Criteria

  • Improved Quality. Acceptance criteria provide a clear definition of what is expected from the product, allowing for better quality control and assurance.
  • Increased Efficiency. By providing a clear set of criteria, acceptance criteria can help streamline the development process and reduce the amount of time spent on unnecessary tasks.
  • Improved Communication. Acceptance criteria can help ensure that all stakeholders are on the same page and that everyone understands the requirements of the product.
  • Reduced Risk. By providing a clear set of criteria, acceptance criteria can help reduce the risk of unexpected issues or delays in the development process.
  • Increased Visibility. Acceptance criteria can help provide visibility into the progress of the project, allowing stakeholders to track progress and identify potential issues.

Challenges of establishing Acceptance Criteria

  • Establishing Clear Criteria. Establishing clear acceptance criteria can be a challenge, as it requires a deep understanding of the project and its goals. It is important to ensure that the criteria are measurable and achievable, and that they are communicated to all stakeholders.
  • Ensuring Consistency. Ensuring consistency across acceptance criteria is essential for successful implementation. This requires careful planning and communication between stakeholders to ensure that all criteria are aligned and that any changes are communicated in a timely manner.
  • Managing Expectations. Managing expectations is key when implementing acceptance criteria. It is important to ensure that stakeholders understand the criteria and that they are realistic in their expectations.
  • Tracking Progress. Tracking progress against acceptance criteria is essential for successful implementation. This requires regular monitoring and reporting to ensure that the criteria are being met and that any issues are addressed in a timely manner.
  • The world can change. As you start to develop your solution, you might discover that customers would be better served with another set of features and acceptance criteria. Having established them from the start comes with the danger of the team blindly pursuing the criteria rather than evaluating what customers and the business actually desires and needs.
Relevant questions to ask
  • What is the purpose of the acceptance criteria?
    Hint The purpose of the acceptance criteria is to define the requirements that must be met for a project or product to be considered complete and accepted.
  • What are the specific requirements that must be met for the criteria to be considered accepted?
    Hint Specific requirements that must be met for the criteria to be considered accepted include the functionality of the product or project, the quality of the product or project, and any other requirements that have been set out in the project or product specifications.
  • What is the expected outcome of the acceptance criteria?
    Hint The expected outcome of the acceptance criteria is that the product or project meets the requirements set out in the specifications and is accepted by the customer or other stakeholders.
  • How will the acceptance criteria be evaluated?
    Hint The acceptance criteria will be evaluated by the customer or other stakeholders to ensure that the product or project meets the requirements set out in the specifications.
  • What is the timeline for meeting the acceptance criteria?
    Hint The timeline for meeting the acceptance criteria will depend on the complexity of the project or product and the resources available to complete it.
  • Who will be responsible for ensuring the acceptance criteria are met?
    Hint The person or team responsible for ensuring the acceptance criteria are met will depend on the project or product and the resources available to complete it.
  • What resources are available to help meet the acceptance criteria?
    Hint Resources available to help meet the acceptance criteria include project management tools, software development tools, and other resources that may be necessary to complete the project or product.
  • What risks are associated with the acceptance criteria?
    Hint Risks associated with the acceptance criteria include the possibility of the product or project not meeting the requirements set out in the specifications, or not being accepted by the customer or other stakeholders.
  • How will the acceptance criteria be documented?
    Hint The acceptance criteria will be documented in the project or product specifications.
  • How will changes to the acceptance criteria be managed?
    Hint Changes to the acceptance criteria will be managed by the project or product team, and any changes must be approved by the customer or other stakeholders.

You might also be interested in reading up on:

People who talk about the topic of Acceptance Criteria on Twitter
Relevant books on the topic of Acceptance Criteria
  • Kanban: Successful Evolutionary Change for Your Technology Business by David J. Anderson (2010)
  • Discover to Deliver: Agile Product Planning and Analysis by Mary Gorman and Ellen Gottesdiener (2012)
  • User Stories Applied: For Agile Software Development by Mike Cohn (2004)
  • Extreme Programming Explained: Embrace Change by Kent Beck (1999)
  • Agile Software Development: The Cooperative Game by Alistair Cockburn (2002)

Want to learn more?

Receive a hand picked list of the best reads on building products that matter every week. Curated by Anders Toxboe. Published every Tuesday.

No spam! Unsubscribe with a single click at any time.

Community events
Product Loop

Product Loop provides an opportunity for Product professionals and their peers to exchange ideas and experiences about Product Design, Development and Management, Business Modelling, Metrics, User Experience and all the other things that get us excited.

Join our community

Made with in Copenhagen, Denmark

Want to learn more about about good product development, then browse our product playbooks.