[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-242653-105":53,"doc-detail-242653-en":126},{"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":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","scrum-cheat-sheet-quick-guide","Scrum Cheat Sheet - Quick Guide","","This quick guide summarizes core Scrum roles and artifacts and explains how Scrum events support transparency, inspection, and adaptation. It defines the responsibilities of the Product Owner, Scrum Master, and the cross-functional Scrum Team, including Product Backlog and Sprint Backlog maintenance. It also covers Burndown Charts, release handling at Sprint ends, and the “DONE” standard as potentially shippable. Sections outline Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective, plus key estimation concepts like user stories, story points, business value, capacity, and velocity.",{"@graph":63,"@context":118},[64,80,101],{"@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":51,"@type":70,"position":76},"https://docshare.wps.com/template/general/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/scrum-cheat-sheet-quick-guide/242653/",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/scrum-cheat-sheet-quick-guide/242653.png","ImageObject",442,249,{"name":88,"@type":89},"Pentious","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-09-20","2026-09-12",true,{"@type":98,"interactionType":99,"userInteractionCount":76},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"Who decides when a release happens in Scrum?","Question",{"text":108,"@type":109},"At the end of any given Sprint, the Product Owner can initiate a Release.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"What does “DONE” mean in this cheat sheet?",{"text":113,"@type":109},"“DONE” means potentially shippable, so functionality considered done can be demonstrated to the Product Owner and stakeholders.",{"name":115,"@type":106,"acceptedAnswer":116},"How long should tasks be estimated to take?",{"text":117,"@type":109},"Tasks should take no longer than 16 hours; if longer, the task should be broken down further.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},242653,1789192958,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":50,"category_name":51,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":76,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":9,"language":135,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":136,"faqs":137,"seo_title":138,"seo_description":61,"update_tm":125,"read_time":4},1374404730887,"https://ap-avatar.wpscdn.com/davatar_6f874abed73319feea01a86fa6f0fab8","Roles  \n\n| Scrum Team |\n| --- |\n|  Team is cross-functional and consists of 5-9 people |\n|  There are no set project roles within the team |\n|  Team defines tasks and assignments |\n|  Team is self-organizing and self-managing |\n|  Maintains the Sprint Backlog |\n|  Conducts the Sprint Review |\n|  |\n| Product Owner (PO) |\n|  Accountable for product success |\n|  Defines all product features |\n|  Responsible for prioritizing product features |\n|  Maintains the Product Backlog |\n|  Insures team working on highest valued features |\n|  |\n| Scrum Master (SM) |\n|  Holds daily 15 minute team meeting (Daily Scrum) |\n|  Removes obstacles |\n|  Shields the team from external interference |\n|  Maintains the Sprint Burndown Chart |\n|  Conducts Sprint Retrospective at the end of a Sprint |\n|  Is a facilitator not a manager |\n\n| Burndown Chart –(BC) |\n| --- |\n|  Chart showing how much work remaining in a Sprint |\n|  Calculated in hours remaining |\n|  Maintained by the Scrum Master daily |\n\n\n| Release Backlog –(RB) |\n| --- |\n|  Same as the Product Backlog. May involve one or |\n| more sprints dependent on determined Release date |\n\n“DONE”= Potentially Shippable!  \nFAQ  \n\n|  Who decides when a Release happens? At the end |\n| --- |\n| of any given Sprint the PO can initiate a Release. |\n|  Who is responsible for managing the teams? The |\n| teams are responsible for managing themselves. |\n|  What is the length of a task? Tasks should take no |\n| longer than 16 hours. If longer then the task should be |\n| broken down further. |\n|  Who manages obstacles? Primary responsibility is |\n| on the Scrum Master. However, teams must learn to |\n| resolve their own issues. If not able then escalated to |\n| SM. |\n|  What are two of the biggest challenges in Scrum? |\n| Teams not self-managing, Scrum Master |\n| managing not leading. |\n\nMeetings  \n\n| Sprint Planning – Day 1 / First Half |\n| --- |\n|  Product backlog prepared prior to meeting |\n|  First half – Team selects items committing to complete |\n|  Additional discussion of PB occurs during actual Sprint |\n| Sprint Planning – Day 1 / Second Half |\n|  Occurs after first half done – PO available for questions |\n|  Team solely responsible for deciding how to build |\n|  Tasks created / assigned – Sprint Backlog produced |\n\n\n| Daily Scrum |\n| --- |\n|  Held every day during a Sprint |\n|  Lasts 15 minutes |\n|  Team members report to each other not Scrum Master |\n|  Asks 3 questions during meeting |\n|  “What have you done since last daily scrum?” |\n|  “What will you do before the next daily scrum?” |\n|  “What obstacles are impeding your work?” |\n|  Opportunity for team members to synchronize their work |\n| Sprint Review |\n|  Team presents “done” code to PO and stakeholders |\n|  Functionality not “done” is not shown |\n|  Feedback generated- PB maybe reprioritized |\n|  Scrum Master sets next Sprint Review |\n| Sprint Retrospective |\n|  Attendees – SM and Team. PO is optional |\n|  Questions – What went well and what can be improved? |\n|  SM helps team in discovery – not provide answers |\n\nVisibility + Flexibility = Scrum  \nGlossary of Terms  \n\n|  Time Box-A period of time to finish a task. The end |\n| --- |\n| date is set and can not be changed |\n|  |\n|  |\n|  |\n|  |\n|  |\n\nSCRUM CHEAT SHEET  \nEstimating  \n| User Stories |\n| --- |\n|  A very high level definition of what the customer wants |\n| the system to do. |\n|  Each story is captured as a separate item on the |\n| Product Backlog |\n|  User stories are NOT dependent on other stories |\n|  Story Template: |\n|  “As a \u003CUser> I want \u003Cfunction> So that \u003Cdesired result> |\n|  Story Example: |\n|  As a user, I want to print a recipe so that I can cook it. |\n|  |\n| Story Points |\n|  A simple way to initially estimate level of effort expected |\n| to develop |\n|  Story points are a relative measure of feature difficulty |\n|  Usually scored on a scale of 1-10. 1=very easy through |\n| 10=very difficult |\n|  Example: |\n|  “Send to a Friend”Story Points = 2 |\n|  “Shopping Cart”Story Points =","cbCaickfoP7BryQp","https://ap.wps.com/l/cbCaickfoP7BryQp","pdf",178239,"English","# Roles\n## Product Owner (PO)\n## Scrum Master (SM)\n## Scrum Team\n# Artifacts and Visibility\n## Burndown Chart (BC)\n## Release Backlog (RB)\n# Meetings\n## Sprint Planning\n## Daily Scrum\n## Sprint Review\n## Sprint Retrospective\n# Estimating\n## User Stories\n## Story Points\n## Business Value\n## Estimate Team Capacity\n## Velocity\n# FAQ","[{\"question\":\"Who decides when a release happens in Scrum?\",\"answer\":\"At the end of any given Sprint, the Product Owner can initiate a Release.\"},{\"question\":\"What does “DONE” mean in this cheat sheet?\",\"answer\":\"“DONE” means potentially shippable, so functionality considered done can be demonstrated to the Product Owner and stakeholders.\"},{\"question\":\"How long should tasks be estimated to take?\",\"answer\":\"Tasks should take no longer than 16 hours; if longer, the task should be broken down further.\"}]","Scrum Cheat Sheet - Quick Guide | PDF"]