Behavior-Driven Development
Behavior-driven development (BDD) takes the position that you can turn an idea for a requirement into implemented, tested, production-ready code simply and effectively, as long as the requirement is specific enough that everyone knows what's going on. To do this, we need a way to describe the requirement such that everyone – the business folks, the analyst, the developer and the tester – have a common understanding of the scope of the work. From this they can agree on a common definition of 'done,' and we escape the dual gumption traps of 'that's not what I asked for' or 'I forgot to tell you about this other thing'.
The Structure of a Story
The idea is that the Title and optionally the Narrative of a user story are what is visible on our Kanban board. It's the one-sight identification of a deployable unit of work and needs to be as short as possible; just enough to remember what it is about...
