[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-242654-105":53,"doc-detail-242654-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","cards-userstories-index-card-template","Cards-UserStories - Index card template","","Index card template for expressing Agile user stories in a Scrum-related format. Includes fields to capture story ID, simplified title, detailed description, and the feature/epic path when requirements are complex. Supports prioritization and planning through MoSCoW (Must/Should/Could/Won’t), business value sizing, risk level, and effort estimation using common scales such as Fibonacci story points.",{"@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":36,"@type":70,"position":76},"https://docshare.wps.com/template/forms/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/cards-userstories-index-card-template/242654/",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/cards-userstories-index-card-template/242654.png","ImageObject",442,249,{"name":88,"@type":89},"Stanley","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-12","2026-09-12",true,{"@type":98,"interactionType":99,"userInteractionCount":101},"InteractionCounter",{"@type":100},"ViewAction",7,{"@type":103,"mainEntity":104},"FAQPage",[105,111,115],{"name":106,"@type":107,"acceptedAnswer":108},"What information does this index card template include for a user story?","Question",{"text":109,"@type":110},"It includes a story ID, a simplified title, and a description written in user-story format, plus an optional feature/epic path for complex requirements.","Answer",{"name":112,"@type":107,"acceptedAnswer":113},"How does the template support prioritization?",{"text":114,"@type":110},"It uses MoSCoW to classify the story as Must, Should, Could, or Won’t based on customer needs.",{"name":116,"@type":107,"acceptedAnswer":117},"Which fields help estimate and manage the delivery effort?",{"text":118,"@type":110},"It provides Business Value, Risk (with level or scale), and Effort estimated as complexity, typically using story points from a Fibonacci-based scale.","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},242654,1790130432,{"code":4,"msg":5,"data":128},{"doc_id":125,"user_id":129,"nickname":88,"user_avatar":130,"doc_module":9,"category_id":35,"category_name":36,"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":25,"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":47},2336477405376,"https://ap-avatar.wpscdn.com/davatar_29158cc5080c5b710cf443261637dec0","Templates for yourepics and user stories  \nScrumDeskIntuitive management!  \n# Index card template\n\n\n| ID    | \u003CTITLE>   |  |  |  |\n| --- | --- | --- | --- | --- |\n| As  \u003Cbr>\u003Cuser>  \u003Cbr>\u003Cwhat>  \u003Cbr>I want  \u003Cbr>because \u003Cvalue>   |  |  |  |  |\n| Feature\\Epic name\\  \u003Cbr>SenumDpak   |  |  |  |  |\n| MoSCoW   |  | Bus.Value   | Risk   | Effort   |\n\n\n| ID   | Unique number identifying user story in product  \u003Cbr>backlog.Typically assigned by electronic tool   |\n| --- | --- |\n| TITLE   | Simplified title of user story.„Register new client“   |\n| Description   | Description of user story in user story format.   |\n| Feature\\Epic name   | The path to user story from user story map in case of  \u003Cbr>complex requirements   |\n| MoSCoW   | How customer needs this story:  \u003Cbr>M-must  \u003Cbr>S-should  \u003Cbr>C-could  \u003Cbr>W-won't   |\n| Business Value   | How important is this user story from our perspective  \u003Cbr>based on our business case.Different scales are  \u003Cbr>applied:S,M,L,XL,XLL or fibonacci numbers.   |\n| Risk   | The risk levele connected to development of this user  \u003Cbr>story.H,M,Lor0-10 scale.   |\n| Effort   | How complex is this user story.Typically evaluated in  \u003Cbr>storz points from Fibonnaci scale.   |\n\n|  |  |  |  |  |  |  |  |  |  |\n| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  | О БотнтОовК   |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  | О,вентОоом   |  |  |  |  | О ватнтОооК   |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  | гнтзОовК   |\n\n|  |  |  |  |  |  |  |  |  |  |\n| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  | О вентОоо   |  |  |  |  | О ватнтОооК   |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  | егштОовК   |  |  |  |  | orumDook   |\n\n|  |  |  |  |  |  |  |  |  |  |\n| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  | О вонтОовК   |  |  |  |  | OsonmDook   |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  | О вєгтОооК   |  |  |  |  | О воытРооК   |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  | О веутОооК   |  |  |  |  | О вегытЭввИ   |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  | О беитОооК   |  |  |  |  | О бвгнъОовК   |\n\n|  |  |  |  |  |  |  |  |  |  |  |\n| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |\n|  |  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  | О вонтОовК   |  |  |  |  | О воутОовК   |\n|  |  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  | OscmDook   |  |  |  |  | Ю быгытОооК   |\n|  |  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  | О веутОооК   |  |  |  |  | О вагтОвК   |\n|  |  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  | О вегитОов   |  |  |  |  | вгнтОовК   |\n\n|  |  |  |  |  |  |  |  |  |  |\n| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |\n|  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  ","cbCaioDsEuhHOtkD","https://ap.wps.com/l/cbCaioDsEuhHOtkD","pdf",716175,"English","# Index card template\n## User story fields\n## Planning fields (MoSCoW, value, risk, effort)","[{\"question\":\"What information does this index card template include for a user story?\",\"answer\":\"It includes a story ID, a simplified title, and a description written in user-story format, plus an optional feature/epic path for complex requirements.\"},{\"question\":\"How does the template support prioritization?\",\"answer\":\"It uses MoSCoW to classify the story as Must, Should, Could, or Won’t based on customer needs.\"},{\"question\":\"Which fields help estimate and manage the delivery effort?\",\"answer\":\"It provides Business Value, Risk (with level or scale), and Effort estimated as complexity, typically using story points from a Fibonacci-based scale.\"}]","Cards-UserStories - Index card template | PDF",1789192961]