Stories Are Promises for Conversation[2]

[2] Alistair Cockburn gave us this elegant description of story as promise for conversation. Buy his book!

User stories are made up of two components. The written card is the first. We recommend writing the story in just a couple of sentences on a card and pointing to any supporting documentation. The second component, and by far the most important, is the series of conversations that will take place between the customer and the programmers over the life of the story. These conversations will be captured as additional documentation that will be attached to the story, will be acted out during Class Responsibility Collaborator (CRC) design sessions, and, better yet, as acceptance tests and application code. ...

Get Extreme Programming Installed now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.