Prezentacja Wiktora Żołnowskiego z Agile Silesia #6

1. BDD & Agile Requirements ­do
it right!
Wiktor Żołnowski
Code Sprinters
http://agileszkolenia.pl
http://fb.com/CodeSprinters
http://blog.testowka.pl
http://fb.com/innypunktwidzenianajakosc
Twitter: @streser
Pragmatic Coders
http://pragmaticcoders.com
http://fb.com/pragmaticcoders
@pragmaticcoders

2. Three aspects of BDD & Agile Requirements
Requirements:
What the stakeholders require?
Requirements => User Stories
Functional Specification:
What the product will do to meet requirements?
Functional Specification => Examples, Acceptance Tests,
Given/When/Then
Technical Specification:
How the product will provide the functionality
Technical Specification => Unit Tests, Functional Tests,
Integration Tests
@strese
r

3. @strese
r
Requirements
As an <User>
I want <some action>
So <Goal>
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>

4. @strese
r
Coaching?
G oal
R eality
O pportunities
W ork

5. @strese
r
It is all about removing requirements
which doesn't make any sense...
https://leanpub.com/agile­transformacje

6. Complicated
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
@strese
r
Cynefin
Simple
Complex
Chaotic
Disorder
1. Everyone knows how to
do this
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/

7. Questions?
Wiktor Żołnowski
Code Sprinters
http://agileszkolenia.pl
http://fb.com/CodeSprinters
http://blog.testowka.pl
http://fb.com/innypunktwidzenianajakosc
Twitter: @streser
wiktor.zolnowski@pragmaticcoders.com
Pragmatic Coders
http://pragmaticcoders.com
http://fb.com/pragmaticcoders
@pragmaticcoders