Conduct scenario grooming meetings

A scenario grooming meeting is a meeting in which business people and technical people collaboratively define the required scenarios. The goal of each meeting is to review a set of scenarios to ensure that there is a common understanding of what each scenario is testing and whether there is enough information to develop it.

If you are implementing Behavior Testing Framework for an implementation that is at or near inception, you can conduct scenario grooming as part of your user story grooming meetings. If the implementation is already significantly complete, then it may make more sense to have meetings devoted to scenario grooming.

Guidewire recommends that insurers design scenarios in a series of scenario groom meetings.

• Each meeting includes at least one business analyst, one developer, and one QA analyst. This mix of people helps ensure that the multiple perspectives of the problem are discussed, including the business view, technical limitations, and the aspects that require testing the most.
• At the beginning of the implementation, business analysts write scenario descriptions using a standard template. The following section contains an example template. As the implementation progresses, business analysts can switch to writing scenario descriptions directly in Gherkin.
• By the end of the meeting, all participants have a clear understanding of the goal of each scenario.

For additional information on problems that can occur with too little cross-team collaboration, refer to the anti-patterns section of the Cucumber documentation.