[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-243187-105":53,"doc-detail-243187-en":127},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":120,"head_meta":122,"extra_data":124,"updated_unix":126},105,"en","a-user-story-primer-user-story-derivation-and-application","A User Story Primer - User Story Derivation and Application","","A User Story Primer explains how user stories act as the primary agile artifact for carrying customer requirements through the software delivery value stream. The paper clarifies the role of user stories as a lightweight, nimble alternative to traditional requirements specifications, and frames the iterative loop of define, implement and test, demonstrate or deliver, capture feedback, and repeat. It also covers user story structure, voice, detail, acceptance criteria, and how to INVEST in good user stories.",{"@graph":63,"@context":119},[64,80,102],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":11,"@type":70,"position":76},"https://docshare.wps.com/template/presentations/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/a-user-story-primer-user-story-derivation-and-application/243187/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/a-user-story-primer-user-story-derivation-and-application/243187.png","ImageObject",442,249,{"name":88,"@type":89},"Levi","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-20","2026-09-12",true,{"@type":98,"interactionType":99,"userInteractionCount":101},"InteractionCounter",{"@type":100},"ViewAction",9,{"@type":103,"mainEntity":104},"FAQPage",[105,111,115],{"name":106,"@type":107,"acceptedAnswer":108},"What is the purpose of a user story in agile development?","Question",{"text":109,"@type":110},"A user story is a lightweight, nimble substitute for traditional software requirements specifications. It carries value from the delivery process to the user and helps enable rapid value delivery.","Answer",{"name":112,"@type":107,"acceptedAnswer":113},"How do user stories relate to requirements specifications and use cases?",{"text":114,"@type":110},"User stories are not requirements specifications or use case specifications. They serve as an agile mechanism for representing user value and guiding iteration.",{"name":116,"@type":107,"acceptedAnswer":117},"What does it mean to apply INVEST in good user stories?",{"text":118,"@type":110},"INVEST describes desirable qualities of good user stories, including being independent, negotiable and negotiated, valuable, estimable, small, and testable.","https://schema.org",{"og:url":78,"og:type":121,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":123,"canonical":78},"index,follow",{"doc_id":125,"site_id":56},243187,1791746220,{"code":4,"msg":5,"data":128},{"doc_id":125,"user_id":129,"nickname":88,"user_avatar":130,"doc_module":9,"category_id":8,"category_name":11,"doc_title":59,"doc_description":61,"doc_content":131,"file_id":132,"file_url":133,"file_type":134,"file_size":135,"view_count":101,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":30,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":61,"update_tm":140,"read_time":141},7971461740909,"https://ap-avatar.wpscdn.com/davatar_155a257f0dc6eb9ab79c44ca47cae57d","Leffingwell, LLC.  \nA User Story Primer  \nBy Dean Leffingwell  \nwith Pete Behrens  \nNote: This whitepaper is an earlier work by the primary authors Dean Leffingwell and Pete Behrens. It provides an overview on the derivation and application of user stories, which are the primary mechanism that carries customer’s requirements through the agile software development value stream. This paper is extracted from the book Agile Software Requirements: Lean Requirements Practices for Teams, Programs and the Enterprise. A special thanks to Jennifer Fawcett and Don Widrig for their contributions as well.  \n© 2009, Leffingwell, LLC. All Rights Reserved.  1  \nIntroduction .......................................................................................................................................... 3  \nUser Story Overview.......................................................................................................................... 3  \nUser Stories Help Bridge the Developer – Customer Communication Gap ...................................... 4  \nUser Stories Are Not Requirements .................................................................................................. 4  \nUser Story Form .................................................................................................................................... 5  \nCard, Conversation and Confirmation ............................................................................................... 5  \nUser Story Voice ................................................................................................................................ 5  \nUser Story Detail ............................................................................................................................... 6  \nUser Story Acceptance Criteria ......................................................................................................... 6  \nINVEST in Good User Stories ................................................................................................................. 7  \nIndependent ...................................................................................................................................... 7  \nNegotiable... and Negotiated ............................................................................................................ 8  \nValuable ............................................................................................................................................ 8  \nEstimable ........................................................................................................................................... 9  \nSmall .................................................................................................................................................. 9  \nTestable ........................................................................................................................................... 11  \nSplitting User Stories ........................................................................................................................... 11  \nSpikes .................................................................................................................................................. 14  \nGuidelines for Spikes ....................................................................................................................... 14  \nStory Modeling with Index Cards ........................................................................................................ 15  \nSummary ............................................................................................................................................. 16  \nA User Story Primer  \nThey have been at a great feast of languages, and stol'n the scraps.--Moth to Costard, Love's Labor's Lost, Act 5, scene 1, William Shakespeare  \nIntroduction  \nIn agile development, the user story is a lightweight and more nimble ","cbCainut240JujAd","https://ap.wps.com/l/cbCainut240JujAd","pdf",2363295,"English","# Introduction\n# User Story Overview\n## User Stories Help Bridge the Developer – Customer Communication Gap\n## User Stories Are Not Requirements\n## User Story Form\n## Card, Conversation and Confirmation\n## User Story Voice\n## User Story Detail\n## User Story Acceptance Criteria\n## INVEST in Good User Stories\n### Independent\n### Negotiable and Negotiated\n### Valuable\n### Estimable\n### Small\n### Testable\n## Splitting User Stories\n## Spikes\n### Guidelines for Spikes\n## Story Modeling with Index Cards\n# Summary","[{\"question\":\"What is the purpose of a user story in agile development?\",\"answer\":\"A user story is a lightweight, nimble substitute for traditional software requirements specifications. It carries value from the delivery process to the user and helps enable rapid value delivery.\"},{\"question\":\"How do user stories relate to requirements specifications and use cases?\",\"answer\":\"User stories are not requirements specifications or use case specifications. They serve as an agile mechanism for representing user value and guiding iteration.\"},{\"question\":\"What does it mean to apply INVEST in good user stories?\",\"answer\":\"INVEST describes desirable qualities of good user stories, including being independent, negotiable and negotiated, valuable, estimable, small, and testable.\"}]","A User Story Primer - User Story Derivation and Application | PDF",1789201017,6]