TL;DR: We use rule-oriented and scenario-oriented acceptance criteria for test definition and clarity. Is this OK?
I am seeing more and more descriptions of stories where the user scenarios or bullet pointed acceptance criteria are used, but not both. E.g.:
We use the scenarios to define what is required as functional change and for automated test definitions.
We use bullet pointed acceptance criteria to define yes/no human pass/fail conditions in as concise terminology as possible.
Having read this post I would like to know if it is appropriate to use both acceptance criteria and Scenarios in the same Behaviour-Driven Development stories?
I do it this way (as the Scrum Master) because it is how I was raised (in Agile) though I admit to finding difficulty in describing 'how to write bullet acceptance criteria' for my team.