is a way of software requirements documentation focused on user-centered design

- Stackoverflow.com Wiki
1 articles, 1 books. Go to books ↓

Summed up, the problem with user stories is that it’s too many assumptions and doesn’t acknowledge causality. When a task is put in the format of a user story ( As a [type of user], I want [some action], so that [outcome] ) there’s no room to ask ‘why’ — you’re essentially locked into a particular sequence with no context.