A brief description of a software feature written from the end user's perspective, typically following the format 'As a [user type], I want [functionality] so that [benefit].' It captures requirements in simple, non-technical language.
Coined in the late 1990s by Extreme Programming practitioners who needed a simpler alternative to formal requirements documents. 'User' comes from Latin 'uti' (to use) and 'story' from Greek 'historia' (inquiry, knowledge acquired by investigation).
User stories revolutionized software development by shifting focus from technical specifications to human needs and behaviors. The three-part format was specifically designed to force teams to think about WHO needs something, WHAT they need, and WHY they need it—preventing feature bloat!
Complete word intelligence in one call. Free tier — 50 lookups/day.