Write acceptance criteria in the form of business rules
A business rule is a form of business requirement that, once created, does not require the programmer’s involvement to change. They are excellent acceptance criteria.
For example, if the marketing department wants to offer a 10% discount to students living in Florida during the winter months, the business rule must specify this option. Marketing wants to be able to make these changes on the fly to adapt to current market changes and stay competitive. Business rules give them that ability.
In its simplest definition, a business rule is a policy that defines, triggers, or restricts business activity. They are an integral part of user stories, describing the processes, definitions, and constraints that apply to your business.
Business rules are not just about technology, they are about people, processes, business behaviors and systems. They help an organization achieve its goals.
To clarify the conditions:
- Business rules provide criteria and conditions for decision making.
- User stories or business requirements enable the implementation and compliance of business rules.
Defining acceptance criteria for user stories in the form of business rules can quickly clarify complex stakeholder requirements. Below is a sample of this acceptance criteria type.
To reduce abandonment rates, underwriters can approve or deny auto insurance applications within three business days.
What time does the working day start and end? Are you open on weekends? Until we know the answers to these questions, we cannot measure whether the software correctly implements the user’s story.
The most common form of business rule is a statement of fact. To successfully implement this user story, you can write acceptance criteria that reference (or cite) specific business rules.
BR107: Business days end Monday through Friday, 8:00 am to 5:00 pm (UTC-7), excluding US holidays.
