Scenarios are the central artifact of the Behavior Driven Development (BDD) process. Although many teams use scenarios and tools like Cucumber or SpecFlow to automate them, in many cases, their scenarios contain a lot of details, particularly test data, and therefore, they become too complicated to support collaboration with the business. The “essential” principle of scenario writing (scenario formulation) states that only those details that are relevant to the outcome should be included in the scenario. This interactive talk provides help for those who struggle to implement this principle or would be interested to learn how you can create brief and maintainable scenarios. We will look at and discuss the most common pitfalls and also discuss options to express details of complex business requirements in a form that can work as a shared specification for both the business and the delivery team.
Extra handout
According to a study conducted by McKinsey in conjunction with Agile Alliance in 2022, three out of four Agile transformations fail. The number one reason is the lack of cultural change.
Using a waterfall process for a transformation, as many comp…
