BDD & Agile Requirements - do it right!

Wiktor onowskiCode Sprintershttp://agileszkolenia.pl http://fb.com/CodeSprinters http://blog.testowka.pl http://fb.com/innypunktwidzenianajakosc Twitter: @streser

Pragmatic Codershttp://pragmaticcoders.comhttp://fb.com/pragmaticcoders@pragmaticcoders

Three aspects of BDD & Agile Requirements

Requirements:
What the stakeholders require?

Functional Specification:
What the product will do to meet requirements?

Technical Specification:
How the product will provide the functionality

Requirements => User Stories

Functional Specification => Examples, Acceptance Tests, Given/When/Then

Technical Specification => Unit Tests, Functional Tests, Integration Tests

@streser

@streser

As an
I want
So

As an user
I want to log in into application
So I will be logged in

In order to
As an
I want

Requirements

@streser

Coaching?

G oal
R eality
O pportunities
W ork

@streser

It is all about removing requirements which doesn't make any sense...

https://leanpub.com/agile-transformacje

@streser

Cynefin

Simple

Complicated

Complex

Chaotic

Disorder

1. Everyone knows how to do this

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 before

BDD

Experiments

Libraries

Do not use BDD for everything!

https://cognitive-edge.com/library/more/articles/
http://lizkeogh.com/2013/07/21/estimating-complexity/

Questions?

Wiktor onowskiCode Sprintershttp://agileszkolenia.pl http://fb.com/CodeSprinters http://blog.testowka.pl http://fb.com/innypunktwidzenianajakosc Twitter: @streser

wiktor.zolnowski@pragmaticcoders.comPragmatic Codershttp://pragmaticcoders.comhttp://fb.com/pragmaticcoders@pragmaticcoders