NPD Jargon Buster: Acceptance Criteria

Learning Centre > NPD Jargon Buster: Acceptance Criteria

Acceptance criteria are the requirements that the product developers and product teams agree on for a specific part of their work.

Acceptance criteria are the requirements that the product developers and product teams agree on for a specific part of their work. Acceptance criteria are the requirements that the product developers and product teams agree on for a specific part of their work.
Contents

Acceptance criteria are the requirements that the product developers and product teams agree on for a specific part of their work. These requirements can be easy to understand.

Acceptance criteria are the things that a team agrees need to happen in order for work on a product to be complete.

When you make a list of the things that you want the product developers to build, be clear and concise. Write in plain language. Make it easy for them to understand what you want to be done by saying it in a way that makes sense. Talk with the developers before making this list so they know what you need from them when they do their work.

Acceptance criteria for each story or task should be verified before a product developer completes their work. The list of acceptance criteria is what you and the product team will use to tell if the work done on a product meets your requirements. If it does, then you can release it to customers.

Innovolo uses a technique called functional specification to write acceptance criteria.

Not every requirement is an acceptance criterion, so be careful not to overuse them. Acceptance criteria should only be used for what you will verify before moving on with your work. It can be easy to include too many of them and catch yourself up making sure everything is done perfectly, but then you give away all your time and energy achieving nothing.

Acceptance criteria should be prioritised as well. Only include those criteria that are the most important to the success of your product.

No items found.

Acceptance criteria are the requirements that the product developers and product teams agree on for a specific part of their work. These requirements can be easy to understand.

Acceptance criteria are the things that a team agrees need to happen in order for work on a product to be complete.

When you make a list of the things that you want the product developers to build, be clear and concise. Write in plain language. Make it easy for them to understand what you want to be done by saying it in a way that makes sense. Talk with the developers before making this list so they know what you need from them when they do their work.

Acceptance criteria for each story or task should be verified before a product developer completes their work. The list of acceptance criteria is what you and the product team will use to tell if the work done on a product meets your requirements. If it does, then you can release it to customers.

Innovolo uses a technique called functional specification to write acceptance criteria.

Not every requirement is an acceptance criterion, so be careful not to overuse them. Acceptance criteria should only be used for what you will verify before moving on with your work. It can be easy to include too many of them and catch yourself up making sure everything is done perfectly, but then you give away all your time and energy achieving nothing.

Acceptance criteria should be prioritised as well. Only include those criteria that are the most important to the success of your product.

Key Takeways

Related Articles

Join 70+ companies accelerating their product development with Innovolo
Farm+Stable is a client of Innovolo, a product development as a service provider offering R&D teams globally extra capacity, capability, and momentum in their product development and obsolescence management projects. As a company that specializes in the development and engineering of products for the agriculture and construction industries, Farm+Stable has benefited from Innovolo's expertise in helping to bring new products to market quickly and efficiently. In particular, Farm+Stable has been able to rely on Innovolo's team of experienced engineers to help with the design and development of a new line of products that are designed to be more durable and longer-lasting than previous models. With Innovolo's help, Farm+Stable has been able to bring these new products to market in a timely manner, and they have been well-received by customers. Thanks to Innovolo's innovative product development solutions, Farm+Stable has been able to stay ahead of the competition and continue to grow their business.
Innovolo is a product development as a service provider. It offers R&D teams globally extra capacity, capability, and momentum in their product development and obsolescence management projects. Its services are used by clients in a variety of industries, including automotive, aerospace, consumer electronics, and medical devices. One of its clients is Kawneer, a leading manufacturer of aluminum products for the architectural and construction industries. Kawneer has been using Innovolo's services to help develop new products and to manage the obsolescence of its existing products. Thanks to Innovolo, Kawneer has been able to speed up its product development cycle and to reduce its costs. As a result, Kawneer has been able to bring new products to market faster and to better meet the needs of its customers.

Related Tools and Templates

No items found.

Brands Mentioned

No items found.