Three aspects of BDD & Agile Requirements
What the stakeholders require?
Requirements => User Stories
What the product will do to meet requirements?
Functional Specification => Examples, Acceptance Tests,
How the product will provide the functionality
Technical Specification => Unit Tests, Functional Tests,
As an <User>
I want <some action>
As an user
I want to log in into application
So I will be logged in
In order to <business goal>
As an <stakeholder>
I want <visible change in system>
It is all about removing requirements
which doesn't make any sense...
3. There is at least one
person in our organization
who know how it works
2. There are at least few
people who know that
1. Everyone knows how to
4. Someone, somewhere
already done that before
5. No one ever done this
Do not use BDD for everything!