The quality of the product is crucial for a business. It may be raw material or finished goods. Product acceptance happens only when the product meets its intention.

In this article, you get information about product acceptance criteria, their importance, and what you must keep in mind while setting the criteria.

Product acceptance is the verification that a given purchased or manufactured item meets specifications and is usable for its intended purpose.

Product Acceptance

Product Acceptance Criteria

It is a set of business rules that a product or service must meet to be accepted by the user. They are distinctive for each user.

Good and realistic acceptance criteria help to avoid unwanted results in the end.

Product Acceptance Criteria

How to set product acceptance criteria

To set acceptance criteria, you need to follow some rules. Initially, based on the customer’s needs, the product manufacturer sets these criteria.

After that, the business analyst, requirement analyst, or development team member reviews these criteria with user stories. Then the whole team discusses the user stories and acceptance criteria.

What are the features of product acceptance criteria?

  • It should be capable of being proven right or wrong: The criteria should have the capacity to define the result yes or no.
  • It should be short and clear: No need to write complete documentation. Criteria must as simple and clear as possible.
  • It should be easily understandable: Set clear criteria so that your developers can understand it without much effort.
  • It should serve user viewpoint: Write the criteria in the situation of real user experience.

What is a User Story?

A user story is an informal, detailed description of the product or software feature written from the end-user point of view.

It contains the type of user, what does he want, and why does he want it. Usually, the client, end-user, manager, or development team member writes a user story.

It helps to describe the requirement of the product feature in a simplified manner.

To write a compelling user story, you need to concentrate on some necessary elements. They are who, what and why.

Here who describes the type of user, what means action, and why describes the benefits.

How does the user story template look like?

User story follows simple template like as a < type of user>, I want <action>, so that <benefit>.

  • Type of user means a person or a system who interacts with the implemented system to reach the goal.
  • Action means an assurance of the user that can be skilled by interacting with the system.
  • Benefit means value gets by the user because of the interaction with the system.

For example, As <Astha>, I want <to clean my work place>, so that<I can feel more comfortable>.

User stories may be written on an index card or small sticky notes, and they may be arranged on the table for discussion.

3C’s of user story

3C's of user story

3C’s are very important in user stories. They are card, conversation, and confirmation.

  • The card contains the user story format. It must address ‘who’, ‘what’, ‘why’.
  • Conversation means the conference between the owner of the product, end-user, team members, and other stakeholders. Most of the time conversation will be verbal and supported by documents.
  • Confirmation means confirmation by the product owner or end-user saying that the story has been successfully implemented and attained the requirements.

User story plays a vital role while setting acceptance criteria for product acceptance.

Important tips to write good Acceptance Criteria

  • Before development, record the criteria: Before actual development, documentation of acceptance criteria is necessary. Collect all customer needs before set the criteria. Make sure that the set criteria are acceptable to both parties ( vendors and buyers).
  • Don’t create too short acceptance criteria: Set the AC to fetch the input but not the final solution.
  • Set the realistic and achievable acceptance criteria: Realistic criteria help you to deliver efficiently.
  • Don’t create too broad acceptance criteria: It leads to an indefinite user story.
  • Don’t use technical words: Write AC in simple English so that your stakeholders, team members, and managers can easily understand.
  • Get consent from everyone: Communicate the acceptance criteria with your stakeholders & team members and make sure that everyone reviews AC because each and everyone has their own point of view of solving problems.
  • Create testable AC: Write AC in so that testers can easily confirm that all the requirements are met or not.

Importance of product acceptance criteria

  • It allows you to define the boundaries of a user story.
  • Because of acceptance criteria, employees of production company or development team of software company come to know what exactly they have to do to reach the customer requirements.
  • It helps you to plan and estimate the project accurately.
  • It acts as the basis for tests.

Get more definitions about product acceptance and other ERP-related terms here.


Subscribe to our Email Newsletter