{"id":5003366,"date":"2015-12-17T00:19:07","date_gmt":"2015-12-17T08:19:07","guid":{"rendered":"https:\/\/aadev22.local\/?post_type=aa_glossary&#038;p=5003366"},"modified":"2024-05-10T11:35:10","modified_gmt":"2024-05-10T18:35:10","slug":"user-stories","status":"publish","type":"aa_glossary","link":"https:\/\/agilealliance.org\/glossary\/user-stories\/","title":{"rendered":"User Stories"},"content":{"rendered":"<p>In consultation with the customer or\u00a0<a href=\"https:\/\/agilealliance.org\/glossary\/product-owner\/\">product owner<\/a>, the team divides up the work to be done into functional increments called \u201cuser stories.\u201d<\/p>\n<p>Each user story is expected to yield, once implemented, a contribution to the value of the overall product, irrespective of the order of implementation; these and other assumptions as to the nature of user stories are captured by the\u00a0<a href=\"https:\/\/agilealliance.org\/glossary\/invest\/\">INVEST<\/a>\u00a0formula.<\/p>\n<p>To make these assumptions tangible, user stories are reified into a physical form: an index card or sticky note, on which a brief descriptive sentence is written to serve as a reminder of its value. This emphasizes the \u201catomic\u201d nature of user stories and encourages\u00a0<a href=\"http:\/\/en.wikipedia.org\/wiki\/Direct_manipulation_interface\">direct physical manipulation<\/a>: for instance, decisions about scheduling are made by physically moving around these \u201cstory cards.\u201d<\/p>\n<h2>Common Pitfalls<\/h2>\n<ul>\n<li>a classic mistake consists, in teams where the Agile approach is confined to the development team or adopted after a non-Agile requirements phase, to start from a requirements document in narrative format and derive user stories directly based on its structure: for instance one story for each section of the document<\/li>\n<li>as the\u00a0<a href=\"https:\/\/agilealliance.org\/glossary\/three-cs\/\">3 C\u2019s<\/a> model emphasizes, a user story is not a document; the term encompasses all of the knowledge required to transform version V of the product into version V\u2019 which is more valuable with respect to a particular goal<\/li>\n<li>the level of detail corresponding to a user story is not constant, it evolves over time as a function of the \u201cplanning horizon\u201d; for instance, a user story that is scheduled for the next iteration should be better understood than one which will not be implemented until the next release<\/li>\n<li>a user story is not a Use Case; although it is often useful to compare and contrast the two notions, they are not equivalent and do not admit a one-to-one mapping<\/li>\n<li>a user story does not in general correspond to a technical or user interface component: even though it may sometimes be a useful shortcut to talk about e.g. \u201cthe search dialog story\u201d, screens, dialog boxes, and buttons are not user stories<\/li>\n<\/ul>\n<h2>Expected Benefits<\/h2>\n<p>For most Agile teams user stories are the main vehicle of\u00a0<a href=\"http:\/\/guide.agilealliance.org\/guide\/incremental.html\">incremental<\/a>\u00a0software delivery, and offer the following benefits:<\/p>\n<ul>\n<li>mitigating the risks of delayed feedback, all the more so<\/li>\n<li>if the increments are small<\/li>\n<li>if the software is\u00a0<a href=\"https:\/\/agilealliance.org\/glossary\/frequent-release\/\">released<\/a>\u00a0to production frequently<\/li>\n<li>for the customer or product owner, the option to change their mind on the details or the scheduling priority of any user story not yet implemented<\/li>\n<li>for developers, being given clear and precise acceptance criteria, and ongoing feedback as they complete work<\/li>\n<li>promoting a clear separation of responsibilities between defining the \u201cwhat\u201d (province of the customer or product owner) and the \u201chow\u201d (province of the technical team), leveraging the skills and creativity of each<\/li>\n<\/ul>\n<h2>Potential Costs<\/h2>\n<p><a href=\"https:\/\/agilealliance.org\/glossary\/incremental-development\/\">Incremental development<\/a> in general, and the \u201cnano-incremental\u201d strategy embodied in user stories in particular, have significant impacts on projects\u2019 testing strategies, and in particular all but mandate significant test automation.<\/p>\n<p>This follows from the so-called \u201c<a href=\"http:\/\/www.hans-eric.com\/wp-content\/uploads\/2011\/05\/Incremental-development-and-regression-testing.pdf\">quadratic growth<\/a>\u201d problem: after the implementation of feature F1 it is normal to test that feature. After the implementation of feature F2, the risk of regression dictates re-testing F1 as well as testing F2. A test sequence assuming incremental development therefore goes: F1,F1+F2,F1+F2+F3, etc. \u2013 this grows as the square of the number of features, and can therefore quickly become unmanageable as projects grow in size. Test automation (in a particular <a href=\"http:\/\/guide.agilealliance.org\/guide\/unittest.html\">unit<\/a>\u00a0and\u00a0<a href=\"http:\/\/guide.agilealliance.org\/guide\/acceptance.html\">acceptance<\/a>\u00a0testing) mitigates this effect, although it does come at a cost.<\/p>\n<h2>Origins<\/h2>\n<p>User Stories originate with\u00a0<a href=\"https:\/\/agilealliance.org\/glossary\/xp\/\">Extreme Programming<\/a>, their first written description in 1998 only claims that customers define project scope \u201cwith user stories, which are like use cases\u201d. Rather than offered as a distinct practice, they are described as one of the \u201cgame pieces\u201d used in the \u201cplanning game\u201d.<\/p>\n<p>However, most of the thrust of further writing centers around all the ways user stories are \u201cunlike\u201d use cases, in trying to answer in a more practical manner \u201chow requirements are handled\u201d in Extreme Programming (and more generally Agile) projects. This drives the emergence, over the years, of a more sophisticated account of user stories.<\/p>\n<ul>\n<li>cf. the\u00a0<a href=\"https:\/\/agilealliance.org\/glossary\/role-feature\/\">Role-feature-benefit template<\/a>, 2001<\/li>\n<li>cf. the\u00a0<a href=\"https:\/\/agilealliance.org\/glossary\/three-cs\/\">3 C\u2019s model<\/a>, 2001<\/li>\n<li>cf. the\u00a0<a href=\"https:\/\/agilealliance.org\/glossary\/invest\/\">INVEST checklist<\/a>, 2003<\/li>\n<li>cf. the\u00a0<a href=\"https:\/\/agilealliance.org\/glossary\/gwt\/\">Given-When-Then template<\/a>, 2006<\/li>\n<\/ul>\n<h2>Signs Of Use<\/h2>\n<ul>\n<li>the team uses visual planning tools (release plan,\u00a0<a href=\"https:\/\/agilealliance.org\/glossary\/story-mapping\/\">story map<\/a>,\u00a0<a href=\"https:\/\/agilealliance.org\/glossary\/taskboard\/\">task board<\/a>) and index cards or stickies on these displays to reflect product features<\/li>\n<li>the labels on cards that stand for user stories contain few or no references to technical elements (\u201cdatabase\u201d, \u201cscreen\u201d or \u201cdialog\u201d) but generally refer to end users\u2019 goals<\/li>\n<\/ul>\n<h2>Skill Levels<\/h2>\n<p>An Agile team will benefit if the skills that underpin the effective use of user stories are widely distributed among the team; however, it is likely that people with a background in \u201crequirements analysis\u201d or with a history in \u201canalyst\u201d roles will have a leg up in acquiring these skills.<\/p>\n<p>As an individual contributor:<\/p>\n<p>Beginner<\/p>\n<ul>\n<li>able to start from another formalism for requirements (narrative document, use cases) and transpose that to user stores<\/li>\n<li>knows at least one standard format for expressing user stories<\/li>\n<li>able to illustrate a user story with an example (including the user\u2019s goal, existing context, user\u2019s actions, and expected outcomes)<\/li>\n<\/ul>\n<p>Intermediate<\/p>\n<ul>\n<li>able to divide up the functional goals of a development effort into user stories (possibly\u00a0<a href=\"https:\/\/agilealliance.org\/glossary\/epic\/\">epics<\/a>), ensuring no gaps are left<\/li>\n<li>knows several formats for expressing user stories and can choose the most appropriate one<\/li>\n<li>able to express the acceptance criteria for a user story in terms that will be directly usable as an automated\u00a0<a href=\"https:\/\/agilealliance.org\/glossary\/acceptance\/\">acceptance test<\/a><\/li>\n<li>knows or can identify the relevant user roles and populations and refers to them appropriately in user stories<\/li>\n<li>can assess a user story using the INVEST checklist or an equivalent, and rephrase or\u00a0<a href=\"https:\/\/agilealliance.org\/glossary\/split\/\">split<\/a>\u00a0the user story as necessary<\/li>\n<\/ul>\n<p>Advanced<\/p>\n<ul>\n<li>able to interpret so-called \u201cnon-functional requirements\u201d in terms of user stories<\/li>\n<li>able to link user stories to higher-level descriptions of project goals (e.g. <a href=\"https:\/\/agilealliance.org\/glossary\/project-chartering\/\">project charter<\/a>) and to provide grounds for the relevance and business value of each user story<\/li>\n<\/ul>\n<p>Collectively, as a team:<\/p>\n<p>Beginner<\/p>\n<ul>\n<li>the team organizes project activities around user stories<\/li>\n<li>the team is able to obtain, \u201cjust in time\u201d, the information necessary to implement user stories, for instance by having access to the product owner or domain expert<\/li>\n<\/ul>\n<p>Intermediate<\/p>\n<ul>\n<li>the team formalizes all activity as work on user stories, each team member can answer at any moment the question \u201cwhat user story are you working on at the moment\u201d<\/li>\n<\/ul>\n<p>Advanced<\/p>\n<ul>\n<li>at any moment, any member of the team can answer the question \u201cwhat is the most important user story in the backlog, and why\u201d<\/li>\n<\/ul>\n<h2>Further Reading<\/h2>\n<ul>\n<li><a href=\"http:\/\/www.amazon.com\/User-Stories-Applied-Software-Development\/dp\/0321205685\">User Stories Applied<\/a>, by Mike Cohn<\/li>\n<li><a href=\"http:\/\/www.amazon.com\/Software-Numbers-Low-Risk-High-Return-Development\/dp\/0131407287\">Software By Numbers<\/a>\u00a0examines the economics of iterative software development<\/li>\n<\/ul>\n<h2>Academic Publications<\/h2>\n<ul>\n<li><a href=\"http:\/\/faculty.ksu.edu.sa\/zohair\/Documents\/CSC541\/Chap2-SWE%20processes\/Agile%20Requirements%20Eng.pdf\">\u201cAgile requirements engineering practices: An empirical study\u201d<\/a>\u00a0discusses an investigation of 16 software development organizations\u2019 Agile requirements practices, and provides an overview of some previous literature on Agile requirements and user stories. (The study takes a mildly adversarial attitude to Agile and comes to somewhat strange conclusions, such as ranking\u00a0<a href=\"http:\/\/guide.agilealliance.org\/guide\/tdd.html\">test-driven development<\/a>\u00a0among requirements engineering practices.)<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>In consultation with the customer or product owner, the team divides up the work to be done into functional increments called &#8220;user stories.&#8221;<\/p>\n","protected":false},"author":8027401,"featured_media":8067461,"parent":0,"menu_order":0,"comment_status":"open","ping_status":"closed","template":"","categories":[908],"tags":[802,805],"class_list":["post-5003366","aa_glossary","type-aa_glossary","status-publish","has-post-thumbnail","hentry","category-process","tag-incremental-development","tag-invest"],"acf":[],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 4.9.10 - aioseo.com -->\n\t<meta name=\"description\" content=\"In consultation with the customer or product owner, the team divides up the work to be done into functional increments called &quot;user stories.&quot;\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"352 Dev Ops\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/agilealliance.org\/glossary\/user-stories\/\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 4.9.10\" \/>\n\n\t\t<!-- Global site tag (gtag.js) - Google Analytics -->\n<script async src=\"https:\/\/www.googletagmanager.com\/gtag\/js?id=UA-17319182-1\"><\/script>\n<script>\n window.dataLayer = window.dataLayer || [];\n function gtag(){dataLayer.push(arguments);}\n gtag('js', new Date());\n\n gtag('config', 'UA-17319182-1');\n<\/script>\n\t\t<meta property=\"og:locale\" content=\"en_US\" \/>\n\t\t<meta property=\"og:site_name\" content=\"Agile Alliance | Promoting a more effective, humane, and sustainable way of working\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"What are User Stories?\" \/>\n\t\t<meta property=\"og:description\" content=\"In consultation with the customer or product owner, the team divides up the work to be done into functional increments called &quot;user stories.&quot;\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/agilealliance.org\/glossary\/user-stories\/\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/agilealliance.org\/wp-content\/uploads\/2017\/06\/glossary-featured-banner-social.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/agilealliance.org\/wp-content\/uploads\/2017\/06\/glossary-featured-banner-social.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"726\" \/>\n\t\t<meta property=\"og:image:height\" content=\"380\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2015-12-17T08:19:07+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2024-05-10T18:35:10+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/agileallianceofficial\/\" \/>\n\t\t<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n\t\t<meta name=\"twitter:site\" content=\"@AgileAlliance\" \/>\n\t\t<meta name=\"twitter:title\" content=\"What are User Stories?\" \/>\n\t\t<meta name=\"twitter:description\" content=\"In consultation with the customer or product owner, the team divides up the work to be done into functional increments called &quot;user stories.&quot;\" \/>\n\t\t<meta name=\"twitter:image\" content=\"https:\/\/agilealliance.org\/wp-content\/uploads\/2017\/06\/glossary-featured-banner.jpg\" \/>\n\t\t<script type=\"application\/ld+json\" class=\"aioseo-schema\">\n\t\t\t{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/agilealliance.org\\\/glossary\\\/user-stories\\\/#breadcrumblist\",\"itemListElement\":[{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/agilealliance.org#listItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/agilealliance.org\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/agilealliance.org\\\/category\\\/process\\\/#listItem\",\"name\":\"Process\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/agilealliance.org\\\/category\\\/process\\\/#listItem\",\"position\":2,\"name\":\"Process\",\"item\":\"https:\\\/\\\/agilealliance.org\\\/category\\\/process\\\/\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/agilealliance.org\\\/glossary\\\/user-stories\\\/#listItem\",\"name\":\"User Stories\"},\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/agilealliance.org#listItem\",\"name\":\"Home\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/agilealliance.org\\\/glossary\\\/user-stories\\\/#listItem\",\"position\":3,\"name\":\"User Stories\",\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/agilealliance.org\\\/category\\\/process\\\/#listItem\",\"name\":\"Process\"}}]},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/agilealliance.org\\\/#organization\",\"name\":\"Agile Alliance\",\"description\":\"Promoting a more effective, humane, and sustainable way of working\",\"url\":\"https:\\\/\\\/agilealliance.org\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"url\":\"https:\\\/\\\/agilealliance.org\\\/wp-content\\\/uploads\\\/2025\\\/02\\\/pmi-aa-logo-temp.png\",\"@id\":\"https:\\\/\\\/agilealliance.org\\\/glossary\\\/user-stories\\\/#organizationLogo\",\"width\":798,\"height\":252,\"caption\":\"NOT FINAL\"},\"image\":{\"@id\":\"https:\\\/\\\/agilealliance.org\\\/glossary\\\/user-stories\\\/#organizationLogo\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/agileallianceofficial\\\/\",\"https:\\\/\\\/www.pinterest.com\\\/agilealliance\\\/_created\\\/\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/4860067\\\/admin\\\/\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/agilealliance.org\\\/author\\\/8027401#author\",\"url\":\"https:\\\/\\\/agilealliance.org\\\/author\\\/8027401\",\"name\":\"352 Dev Ops\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\\\/\\\/agilealliance.org\\\/glossary\\\/user-stories\\\/#authorImage\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/780d271bd140fb829f7a4f5bf51bb99689cbe8fe8bbe1c60fa103e7b13835a74?s=96&d=mm&r=g\",\"width\":96,\"height\":96,\"caption\":\"352 Dev Ops\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/agilealliance.org\\\/glossary\\\/user-stories\\\/#webpage\",\"url\":\"https:\\\/\\\/agilealliance.org\\\/glossary\\\/user-stories\\\/\",\"name\":\"What are User Stories? | Agile Alliance\",\"description\":\"In consultation with the customer or product owner, the team divides up the work to be done into functional increments called \\\"user stories.\\\"\",\"inLanguage\":\"en-US\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/agilealliance.org\\\/#website\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/agilealliance.org\\\/glossary\\\/user-stories\\\/#breadcrumblist\"},\"author\":{\"@id\":\"https:\\\/\\\/agilealliance.org\\\/author\\\/8027401#author\"},\"creator\":{\"@id\":\"https:\\\/\\\/agilealliance.org\\\/author\\\/8027401#author\"},\"image\":{\"@type\":\"ImageObject\",\"url\":\"https:\\\/\\\/agilealliance.org\\\/wp-content\\\/uploads\\\/2017\\\/06\\\/glossary-featured-banner.jpg\",\"@id\":\"https:\\\/\\\/agilealliance.org\\\/glossary\\\/user-stories\\\/#mainImage\",\"width\":972,\"height\":380,\"caption\":\"Agile Essentials Glossary\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/agilealliance.org\\\/glossary\\\/user-stories\\\/#mainImage\"},\"datePublished\":\"2015-12-17T00:19:07-08:00\",\"dateModified\":\"2024-05-10T11:35:10-07:00\"},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/agilealliance.org\\\/#website\",\"url\":\"https:\\\/\\\/agilealliance.org\\\/\",\"name\":\"Agile Alliance\",\"description\":\"Promoting a more effective, humane, and sustainable way of working\",\"inLanguage\":\"en-US\",\"publisher\":{\"@id\":\"https:\\\/\\\/agilealliance.org\\\/#organization\"}}]}\n\t\t<\/script>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"What are User Stories? | Agile Alliance","description":"In consultation with the customer or product owner, the team divides up the work to be done into functional increments called \"user stories.\"","canonical_url":"https:\/\/agilealliance.org\/glossary\/user-stories\/","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":"&lt;!-- Global site tag (gtag.js) - Google Analytics --&gt;\n&lt;script async src=\"https:\/\/www.googletagmanager.com\/gtag\/js?id=UA-17319182-1\"&gt;&lt;\/script&gt;\n&lt;script&gt;\n&nbsp;window.dataLayer = window.dataLayer || [];\n&nbsp;function gtag(){dataLayer.push(arguments);}\n&nbsp;gtag('js', new Date());\n\n&nbsp;gtag('config', 'UA-17319182-1');\n&lt;\/script&gt;"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"BreadcrumbList","@id":"https:\/\/agilealliance.org\/glossary\/user-stories\/#breadcrumblist","itemListElement":[{"@type":"ListItem","@id":"https:\/\/agilealliance.org#listItem","position":1,"name":"Home","item":"https:\/\/agilealliance.org","nextItem":{"@type":"ListItem","@id":"https:\/\/agilealliance.org\/category\/process\/#listItem","name":"Process"}},{"@type":"ListItem","@id":"https:\/\/agilealliance.org\/category\/process\/#listItem","position":2,"name":"Process","item":"https:\/\/agilealliance.org\/category\/process\/","nextItem":{"@type":"ListItem","@id":"https:\/\/agilealliance.org\/glossary\/user-stories\/#listItem","name":"User Stories"},"previousItem":{"@type":"ListItem","@id":"https:\/\/agilealliance.org#listItem","name":"Home"}},{"@type":"ListItem","@id":"https:\/\/agilealliance.org\/glossary\/user-stories\/#listItem","position":3,"name":"User Stories","previousItem":{"@type":"ListItem","@id":"https:\/\/agilealliance.org\/category\/process\/#listItem","name":"Process"}}]},{"@type":"Organization","@id":"https:\/\/agilealliance.org\/#organization","name":"Agile Alliance","description":"Promoting a more effective, humane, and sustainable way of working","url":"https:\/\/agilealliance.org\/","logo":{"@type":"ImageObject","url":"https:\/\/agilealliance.org\/wp-content\/uploads\/2025\/02\/pmi-aa-logo-temp.png","@id":"https:\/\/agilealliance.org\/glossary\/user-stories\/#organizationLogo","width":798,"height":252,"caption":"NOT FINAL"},"image":{"@id":"https:\/\/agilealliance.org\/glossary\/user-stories\/#organizationLogo"},"sameAs":["https:\/\/www.facebook.com\/agileallianceofficial\/","https:\/\/www.pinterest.com\/agilealliance\/_created\/","https:\/\/www.linkedin.com\/company\/4860067\/admin\/"]},{"@type":"Person","@id":"https:\/\/agilealliance.org\/author\/8027401#author","url":"https:\/\/agilealliance.org\/author\/8027401","name":"352 Dev Ops","image":{"@type":"ImageObject","@id":"https:\/\/agilealliance.org\/glossary\/user-stories\/#authorImage","url":"https:\/\/secure.gravatar.com\/avatar\/780d271bd140fb829f7a4f5bf51bb99689cbe8fe8bbe1c60fa103e7b13835a74?s=96&d=mm&r=g","width":96,"height":96,"caption":"352 Dev Ops"}},{"@type":"WebPage","@id":"https:\/\/agilealliance.org\/glossary\/user-stories\/#webpage","url":"https:\/\/agilealliance.org\/glossary\/user-stories\/","name":"What are User Stories? | Agile Alliance","description":"In consultation with the customer or product owner, the team divides up the work to be done into functional increments called \"user stories.\"","inLanguage":"en-US","isPartOf":{"@id":"https:\/\/agilealliance.org\/#website"},"breadcrumb":{"@id":"https:\/\/agilealliance.org\/glossary\/user-stories\/#breadcrumblist"},"author":{"@id":"https:\/\/agilealliance.org\/author\/8027401#author"},"creator":{"@id":"https:\/\/agilealliance.org\/author\/8027401#author"},"image":{"@type":"ImageObject","url":"https:\/\/agilealliance.org\/wp-content\/uploads\/2017\/06\/glossary-featured-banner.jpg","@id":"https:\/\/agilealliance.org\/glossary\/user-stories\/#mainImage","width":972,"height":380,"caption":"Agile Essentials Glossary"},"primaryImageOfPage":{"@id":"https:\/\/agilealliance.org\/glossary\/user-stories\/#mainImage"},"datePublished":"2015-12-17T00:19:07-08:00","dateModified":"2024-05-10T11:35:10-07:00"},{"@type":"WebSite","@id":"https:\/\/agilealliance.org\/#website","url":"https:\/\/agilealliance.org\/","name":"Agile Alliance","description":"Promoting a more effective, humane, and sustainable way of working","inLanguage":"en-US","publisher":{"@id":"https:\/\/agilealliance.org\/#organization"}}]},"og:locale":"en_US","og:site_name":"Agile Alliance | Promoting a more effective, humane, and sustainable way of working","og:type":"article","og:title":"What are User Stories?","og:description":"In consultation with the customer or product owner, the team divides up the work to be done into functional increments called &quot;user stories.&quot;","og:url":"https:\/\/agilealliance.org\/glossary\/user-stories\/","og:image":"https:\/\/agilealliance.org\/wp-content\/uploads\/2017\/06\/glossary-featured-banner-social.jpg","og:image:secure_url":"https:\/\/agilealliance.org\/wp-content\/uploads\/2017\/06\/glossary-featured-banner-social.jpg","og:image:width":726,"og:image:height":380,"article:published_time":"2015-12-17T08:19:07+00:00","article:modified_time":"2024-05-10T18:35:10+00:00","article:publisher":"https:\/\/www.facebook.com\/agileallianceofficial\/","twitter:card":"summary_large_image","twitter:site":"@AgileAlliance","twitter:title":"What are User Stories?","twitter:description":"In consultation with the customer or product owner, the team divides up the work to be done into functional increments called &quot;user stories.&quot;","twitter:image":"https:\/\/agilealliance.org\/wp-content\/uploads\/2017\/06\/glossary-featured-banner.jpg"},"aioseo_meta_data":{"post_id":"5003366","title":"What are User Stories? #separator_sa #site_title","description":"In consultation with the customer or product owner, the team divides up the work to be done into functional increments called &quot;user stories.&quot;","keywords":null,"keyphrases":{"focus":{"keyphrase":"","score":0,"analysis":{"keyphraseInTitle":{"score":0,"maxScore":9,"error":1}}},"additional":[]},"primary_term":null,"canonical_url":null,"og_title":"What are User Stories?","og_description":"In consultation with the customer or product owner, the team divides up the work to be done into functional increments called &quot;user stories.&quot;","og_object_type":"article","og_image_type":"custom_image","og_image_url":"https:\/\/agilealliance.org\/wp-content\/uploads\/2017\/06\/glossary-featured-banner-social.jpg","og_image_width":"0","og_image_height":"0","og_image_custom_url":"https:\/\/agilealliance.org\/wp-content\/uploads\/2017\/06\/glossary-featured-banner-social.jpg","og_image_custom_fields":null,"og_video":"","og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"summary_large_image","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":"What are User Stories?","twitter_description":"In consultation with the customer or product owner, the team divides up the work to be done into functional increments called \"user stories.\"","schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"WebPage","isEnabled":true},"graphs":[],"defaultGraph":null,"defaultPostTypeGraph":""},"schema_type":"default","schema_type_options":"{\"article\":{\"articleType\":\"BlogPosting\"},\"course\":{\"name\":\"\",\"description\":\"\",\"provider\":\"\"},\"faq\":{\"pages\":[]},\"product\":{\"reviews\":[]},\"recipe\":{\"ingredients\":[],\"instructions\":[],\"keywords\":[]},\"software\":{\"reviews\":[],\"operatingSystems\":[]},\"webPage\":{\"webPageType\":\"WebPage\"},\"blockGraphs\":[]}","pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":"-1","robots_max_videopreview":"-1","robots_max_imagepreview":"large","priority":null,"frequency":"default","local_seo":null,"breadcrumb_settings":null,"limit_modified_date":false,"ai":null,"created":"2021-02-02 20:01:00","updated":"2025-06-23 09:25:25","seo_analyzer_scan_date":null},"aioseo_breadcrumb":"<div class=\"aioseo-breadcrumbs\"><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/agilealliance.org\" title=\"Home\">Home<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">&raquo;<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/agilealliance.org\/category\/process\/\" title=\"Process\">Process<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">&raquo;<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\tUser Stories\n\t\t<\/span><\/div>","aioseo_breadcrumb_json":[{"label":"Home","link":"https:\/\/agilealliance.org"},{"label":"Process","link":"https:\/\/agilealliance.org\/category\/process\/"},{"label":"User Stories","link":"https:\/\/agilealliance.org\/glossary\/user-stories\/"}],"_links":{"self":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_glossary\/5003366","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_glossary"}],"about":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/types\/aa_glossary"}],"author":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/users\/8027401"}],"replies":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/comments?post=5003366"}],"version-history":[{"count":0,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_glossary\/5003366\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/media\/8067461"}],"wp:attachment":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/media?parent=5003366"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/categories?post=5003366"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/tags?post=5003366"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}