The notion of a user story is pretty simple. A user story is, literally, a story (using the standard dictionary definition of the word). It describes your end users performing domain-level work in order to achieve an outcome that's valuable in the domain. 1/5

Stories describe your user's work, not yours. 2/5

The point of using stories is to assure that the work that we're doing provides value (at the domain level) to our users. They describe a work task. Developer tasks don't necessarily do that. Developer tasks are not stories. Period. 3/5

A story *does not* describe a computer program or any modification you may or may not make to a computer program. It *is not* a code word for a developer task or a nonfunctional requirement. 4/5

It *is* small—ideally small enough that you could implement that work in a day or two. Details about how to implement the story should not be captured until "the last responsible moment"–just before the implementation work begins. 5/5