1. BDD & Agile Requirements doit right!Wiktor onowskiCode Sprintershttp://agileszkolenia.plhttp://fb.com/CodeSprintershttp://blog.testowka.plhttp://fb.com/innypunktwidzenianajakoscTwitter: @streserPragmatic Codershttp://pragmaticcoders.comhttp://fb.com/pragmaticcoders@pragmaticcoders

2. Three aspects of BDD & Agile RequirementsRequirements:What the stakeholders require?Requirements => User StoriesFunctional Specification:What the product will do to meet requirements?Functional Specification => Examples, Acceptance Tests,Given/When/ThenTechnical Specification:How the product will provide the functionalityTechnical Specification => Unit Tests, Functional Tests,Integration Tests@streser 3. @streserRequirementsAs an I want So As an userI want to log in into applicationSo I will be logged inIn order to As an I want 4. @streserCoaching?G oalR ealityO pportunitiesW ork 5. @streserIt is all about removing requirementswhich doesn't make any sense...https://leanpub.com/agiletransformacje 6. Complicated3. There is at least oneperson in our organizationwho know how it works2. There are at least fewpeople who know that@streserCynefinSimpleComplexChaoticDisorder1. Everyone knows how todo this4. Someone, somewherealready done that before5. No one ever done thisbeforeBDDExperimentsLibrariesDo not use BDD for everything!https://cognitiveedge.com/library/more/articles/http://lizkeogh.com/2013/07/21/estimatingcomplexity/ 7. Questions?Wiktor onowskiCode Sprintershttp://agileszkolenia.plhttp://fb.com/CodeSprintershttp://blog.testowka.plhttp://fb.com/innypunktwidzenianajakoscTwitter: @streserwiktor.zolnowski@pragmaticcoders.comPragmatic Codershttp://pragmaticcoders.comhttp://fb.com/pragmaticcoders@pragmaticcoders