Not much is said about software requirements in agile projects. Product backlog is all you need to run. Is it so simple? If so why there are so many misunderstandings about the functionality that shall be done. Where the bugs come from? Why customer is claiming that it should have worked in another way. Or why the well known swings cartoon was created? Behaviour Driven Development comes here with help to us. Each user story can be easily break down into scenarios. Scenarios are described as examples and understand in the same way by dev team and customer. Finally all scenarios are easily automated by specification frameworks like SpecFlow, Cucumber, JBehave. Silver bullet found? Is there any? In my talk I would like to talk about introduction Behaviour Driven Development in complex project with many dependencies. What we found good about BDD, what was taught. And why we failed… yes we failed . What are the challenges for you when you decide to follow this path and when you shouldn't because there is no sense.
Lecture language: Polish