[{"data":1,"prerenderedAt":93},["ShallowReactive",2],{"term-u\u002Fuser-story":3,"related-u\u002Fuser-story":74},{"id":4,"title":5,"acronym":6,"body":7,"category":53,"description":54,"difficulty":55,"extension":56,"letter":57,"meta":58,"navigation":59,"path":60,"related":61,"seo":68,"sitemap":69,"stem":72,"subcategory":6,"__hash__":73},"terms\u002Fterms\u002Fu\u002Fuser-story.md","User Story",null,{"type":8,"value":9,"toc":46},"minimark",[10,15,19,23,39,43],[11,12,14],"h2",{"id":13},"eli5-the-vibe-check","ELI5 — The Vibe Check",[16,17,18],"p",{},"A user story is a tiny description of a feature from the user's perspective, written in plain English: 'As a user, I want to reset my password, so that I can log in when I forget it.' It keeps the team focused on WHY they're building something, not just what.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25,26,30,31,34,35,38],{},"A user story is an informal description of a feature from an end-user perspective, following the template: 'As a ",[27,28,29],"span",{},"user type",", I want ",[27,32,33],{},"action"," so that ",[27,36,37],{},"benefit",".' They are the primary currency of Agile backlogs and are complemented by acceptance criteria.",[11,40,42],{"id":41},"when-youll-hear-this","When You'll Hear This",[16,44,45],{},"\"Write a user story for the password reset feature.\" \u002F \"The user story is too vague — add acceptance criteria.\"",{"title":47,"searchDepth":48,"depth":48,"links":49},"",2,[50,51,52],{"id":13,"depth":48,"text":14},{"id":21,"depth":48,"text":22},{"id":41,"depth":48,"text":42},"general","A user story is a tiny description of a feature from the user's perspective, written in plain English: 'As a user, I want to reset my password, so that I c...","beginner","md","u",{},true,"\u002Fterms\u002Fu\u002Fuser-story",[62,63,64,65,66,67],"Epic","Ticket","Backlog","Scrum","MVP","Agile",{"title":5,"description":54},{"changefreq":70,"priority":71},"weekly",0.7,"terms\u002Fu\u002Fuser-story","CzwQHgJKgPBsJ7AbsAFFfE9lhYb5RsZdJHrQREVVptI",[75,78,81,84,87,90],{"title":67,"path":76,"acronym":6,"category":53,"difficulty":55,"description":77},"\u002Fterms\u002Fa\u002Fagile","Agile is a philosophy of building software in short cycles, learning from real feedback, and adapting quickly instead of following a massive upfront plan.",{"title":64,"path":79,"acronym":6,"category":53,"difficulty":55,"description":80},"\u002Fterms\u002Fb\u002Fbacklog","The backlog is the master to-do list for a product — every feature, bug, and idea that hasn't been built yet, prioritised by importance.",{"title":62,"path":82,"acronym":6,"category":53,"difficulty":55,"description":83},"\u002Fterms\u002Fe\u002Fepic","An epic is a big chunk of work that's too large to finish in one sprint, so it gets broken down into smaller user stories.",{"title":66,"path":85,"acronym":66,"category":53,"difficulty":55,"description":86},"\u002Fterms\u002Fm\u002Fmvp","An MVP is the simplest version of your product that actually works well enough for real users to use and for you to learn from.",{"title":65,"path":88,"acronym":6,"category":53,"difficulty":55,"description":89},"\u002Fterms\u002Fs\u002Fscrum","Scrum is a specific recipe for doing Agile.",{"title":63,"path":91,"acronym":6,"category":53,"difficulty":55,"description":92},"\u002Fterms\u002Ft\u002Fticket","A ticket is a single unit of work in a project management tool — it could be a bug to fix, a feature to build, or a task to complete.",1776518321373]