What changed in the last 20 years of Software Development Technology? Customers? I think that both... And especially Relations between business and IT changed. This is why we are looking for methods and frameworks like Scrum, Kanban or BDD
BDD and Agile Requirements (v 2.1)
BDD & Agile Requirements do it right!
What changed in the last 20 years in
And it is not the end...
Change is inevitable...
Three aspects of BDD & Agile Requirements
What the stakeholders require?
What the product will do to meet requirements?
How the product will provide the functionality
Requirements => User Stories
Functional Specification => Examples, Acceptance Tests,
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...
1. Write an acceptance test...
2. Go into TDD loop until Acceptance Test
1. Everyone knows how to
2. There are at least few
people who know that
3. There is at least one
person in our organization
who know how it works
4. Someone, somewhere
already done that before
5. No one ever done this
Do not use BDD for everything!
Single Bath Flow
Continuous Delivery does not mean that you need to
deliver every change to production...
Continuous Delivery means that you can deliver your
product to production at any time
User Stories is a great tool for discovering
requirements not only writing it down...
You do not have to use User Stories for everything...
Single Bath Flow will allow you to do real Continuous
Continuous Delivery is also for business not only for