Stories act as a “pidgin language,” where both sides (users and developers) can agree enough to work together effectively.

—Bill Wake, co-inventor of eXtreme Programming


Stories are the primary artifact used to define system behavior in Agile development. Stories are not requirements; they are short, simple descriptions of a small piece of desired functionality, usually told from the user’s perspective and written in the user’s language. Each is intended to support implementation of a small, vertical slice of system functionality, supporting highly incremental development. In Agile development, stories largely replace the traditional ...

Get SAFe® 4.0 Reference Guide: Scaled Agile Framework® for Lean Software and Systems Engineering now with the O’Reilly learning platform.

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