Agree evidence of acceptance

What you will understand

• Distinguish quality expectations, requirements, specifications and acceptance criteria.
• Explain why acceptance arrangements belong in planning.
• Recognise the controlled use of quality tolerances.

The idea

“Easy to use” can mean different things to a developer, an occasional user and an accessibility adviser. Discovering those differences at the final demonstration is expensive. Quality planning turns broad expectations into clear requirements, product specifications and acceptance arrangements, while giving people a controlled way to refine what they learn during delivery.

User quality expectations express the characteristics and standards that matter to those who will use or benefit from the project product. They may initially be broad. Requirements make needs more explicit: for example, a volunteer must be able to book a room without administrator help. Requirements need discussion and prioritisation so the project does not assume that every stakeholder expects the same result or that every desirable feature is mandatory.

Acceptance criteria provide the agreed conditions against which the overall project product will be accepted. They should be measurable or objectively assessable, appropriately prioritised and linked to the relevant acceptance responsibilities. The project product description brings the overall result and these arrangements together. A senior manager’s enthusiasm at a demonstration does not replace evidence or acceptance authority agreed with the appropriate user representatives.

Individual product descriptions define the products and their quality specifications, the methods for checking them and relevant responsibilities. A specification might define response times under an agreed workload or the materials a public bench must use. A quality method explains how the specification will be checked. Product descriptions help suppliers understand what to build and reviewers understand what evidence to seek; they are not simply end-of-project paperwork.

Quality tolerance defines an acceptable range for a quality characteristic where variation is allowed. If a printed panel may be between 995 and 1005 millimetres wide, a 1002-millimetre result meets that particular specification. This is not permission to waive unrelated requirements or mandatory legal standards. Being late in the schedule does not expand an agreed tolerance. A forecast or actual failure needs assessment through the appropriate control arrangements.

The quality management approach describes the project’s standards, responsibilities, methods and procedures for quality. Plan quality activities alongside the work that produces the products, including specialist resources and acceptance evidence. Requirements can evolve as the project learns, especially with iterative delivery, but approved baselines must be changed through agreed authority. Controlled learning and product focus work together: neither requires all detail to be known on the first day, nor permits informal redefinition after an inconvenient test result.

Quality starts before testing

Points to remember

• Distinguish overall acceptance criteria from the specifications of an individual product.
• Agree who will accept and how acceptance will be demonstrated.
• Quality tolerance is an agreed range, not an informal waiver.

Your takeaway

Quality planning connects user expectations to explicit requirements, product specifications and acceptance evidence. Agree responsibilities and tolerances early enough to guide delivery, then control refinements as understanding improves.