User stories makes total sense when you focus on their purpose. A tenet of agile development is to quickly get functionality into the hands of the customer or

User stories makes total sense when you focus on their purpose. A tenet of agile development is to quickly get functionality into the hands of the customer or product owner, so they can provide feedback and get a better understanding of what they want. The user story describes a unit of functionality with can be presented for the product owner. It is described in terms of what the user experience (rather than underlying implementation) because this is what the product owner will evaluate. The article gets lost in definitions and classifications, which is the opposite of agile - that is, the agile which value people over process, not the Big Process agile. User stories are not requirements, because you don't know the requirements before the software is finished, at which point formal requirements are rather useless anyway.