Free agile lean waterfall business analysis techniques for product owners

Write Given-When-Then (GWT) Scenarios Based on Business Rules

Acceptance Criteria stated as business rules make it easy to identify critical Scenarios or Scenario Outlines for Acceptance Testing

FREE

Author: Tom and Angela Hathaway
Video Duration: 7:13 minutes

This KnowledgeKnugget™ is part of this eCourse

Business rules are a form of requirements that must be implemented regardless of the technology. They are critical in the quest for the holy grail of business agility.

Decision Tables are a wide-spread tool to document Business Rules. A Decision Table lists all relevant conditions in the upper 4 rows and all outcomes in the lower 3 rows. The check marks show which combination of conditions leads to the individual outcomes.

Using a Decision Table, it is easy to identify critical Scenarios or Scenario outlines to create Acceptance Tests. Each column in a Decision Table is at least ONE Scenario!

Udemy Course: User Story Best Practices
for Agile and Business-side Teams

Learn How to Capture, Write, Prioritize, Rightsize and Split User Stories Plus Acceptance Tests with Given-When-Then Scenarios

Description

Extrapolate Scenarios from Business Rules Using Decision Tables

In their simplest definition, Business rules are an integral part of User Stories. They describe the processes, definitions and Constraints that apply to an organization. They relate to people, processes, business behavior, and computer systems. They are set up to help the organization achieve its goals.

What is the difference between a Business Rule, a Requirement, and a Scenario?

  • Business Rules give you the criteria and conditions for a decision.
  • A Requirement enables the implementation  n of and compliance with a Business Rule.
  • Scenarios are used to validate whether a Business Rule or User Story is implemented correctly.

One Business Rule can easily lead to multiple Scenarios. You could define Scenarios that cover all outcomes to ensure that the new applications takes these conditions properly into account.

User Story Best Practices for
Agile and Business-side Teams

How to Capture, Write, Prioritize, Rightsize and Split User Stories Plus Acceptance Tests with Given-When-Then Scenarios

Learn Lean / Agile Business Analysis Techniques

Book - Lean Agile User Stories and Features

Self-paced Course – Agile Business Analysis: Getting and Writing Lean Requirements

Lean Business Analysis for Lean Requirements: Techniques for Discovering and Writing User Stories, Acceptance Tests, Scenarios and Examples

Kick-start Your Business Analyst Career

Books, eBooks, and Online Courses at a Reasonable Cost
Written for the aspiring Business Analyst and anyone tasked with defining the business needs, requirements, or user stories for a future IT solution.

Pin It on Pinterest

Share This