[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-251607-105":53,"doc-detail-251607-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","sprint-planning-meeting-agenda-meeting-agenda","Sprint Planning Meeting Agenda - Meeting Agenda","","Sprint Planning Meeting Agenda outlines a structured workflow to align the Scrum team on immediate goals and delivery expectations. It specifies invitee roles, then guides introductions, purpose review, and ground rules. The agenda covers defining the sprint goal, capacity, story points, effective working hours, special circumstances, and reviewing the candidate backlog and user story readiness. It further details sprint backlog construction, verification including Definition of Done, missing items, risk identification, task board and burndown setup, and post-meeting follow-ups, with a reference-only disclaimer.",{"@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/sprint-planning-meeting-agenda-meeting-agenda/251607/",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/sprint-planning-meeting-agenda-meeting-agenda/251607.png","ImageObject",442,249,{"name":88,"@type":89},"Ivy","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-29","2026-09-13",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},"Who is required to attend the sprint planning meeting?","Question",{"text":109,"@type":110},"The required invitees are the ScrumMaster/facilitator (SM), the Product Owner/goal and priority setter (PO), and the Development Team (DT).","Answer",{"name":112,"@type":107,"acceptedAnswer":113},"What inputs does the meeting cover to define the sprint goal and scope?",{"text":114,"@type":110},"The agenda includes a situation overview, the sprint goal and accomplishment metric, sprint capacity based on velocity and experience, story points, effective working hours, special circumstances, and a candidate backlog review to ensure readiness and clarity.",{"name":116,"@type":107,"acceptedAnswer":117},"How does the agenda verify the sprint backlog is ready to execute?",{"text":118,"@type":110},"It includes checking for conflicts between stories, ensuring Definition of Done items are considered and achievable, identifying missing backlog items and making adjustments, confirming risks are identified with resolution plans, reviewing team commitment, and verifying the task board and burndown setup are ready.","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},251607,1791001140,{"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":76,"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":9},549758252649,"https://ap-avatar.wpscdn.com/avatar/8000253669c5317157?_k=1778319167496531819","SPRINT PLANNING MEETING AGENDA  \n| PURPOSE | Establishing immediate goal, identifying requirements through the development of user stories and supporting tasks. |  |\n| --- | --- | --- |\n| INVITEES | REQUIRED:\u003Cbr>• SM-ScrumMaster / facilitator\u003Cbr>• PO-Product Owner / goal and priority setting\u003Cbr>• DT-Development Team / Work planning and scheduling | OPTIONAL:\u003Cbr>Key Stakeholders\u003Cbr>Field Experts |\n|  |  |  |\n\nINTRODUCTION  \n\n| X | AGENDA ITEM | OWNER |\n| --- | --- | --- |\n|  | Team Introductions | SM / PO / DT |\n|  | Agenda and Purpose Review | SM / PO / DT |\n|  | Ground Rules Review | SM / PO / DT |\n|  | Note any team members absent | SM / PO / DT |\n\nSPRINT GOAL & USER STORIES  \n\n| X | AGENDA ITEM | OWNER |\n| --- | --- | --- |\n|  | SITUATION OVERVIEW: product vision, roadmap, plan / story map, etc. | PO |\n|  | SPRINT GOAL: define goal and accomplishment metric | PO |\n|  | SPRINT CAPACITY: How much can the team undertake based upon velocity and experience? | DT |\n|  | STORY POINTS: Define established velocity. With an aim to reach beyond past efforts, determine how many story points to accept. | DT |\n|  | HOURS: What is the team’s established effective / actual working hours per day? How many hours are available for this sprint? | DT |\n|  | SPECIAL CIRCUMSTANCES: detail any time considerations: holidays, scheduled time off, training, etc. | DT |\n|  | CANDIDATE BACKLOG REVIEW: | PO / DT |\n|  | • Is the sprint goal supported by each candidate user story? | PO / DT |\n|  | • What is the status of each user story? If it is not ready, how can it be made so quickly. | PO / DT |\n|  | • Is the desired outcome clear among all team members? | PO / DT |\n|  | • If the sum of all story points accepted for the sprint is greater than the amount set by the team, the Product Owner must choose which low priority items to omit. | PO / DT |\n\nSPRINT BACKLOG  \n\n| X | AGENDA ITEM | OWNER |\n| --- | --- | --- |\n|  | Determine the next item to deliver by defining the highest priority. | PO / DT |\n|  | Determine what is not yet understood about the story. | PO / DT |\n|  | Ensure that the deliverable is clear. | PO / DT |\n|  | Ensure that the requirements of the story are clear and adequately defined by the acceptance criteria. | PO / DT |\n|  | Is the implementation approach for this story understood? Is further story work required? | DT |\n|  | Define the tactical approach for story delivery. How are tasks organized and tracked? Review task list. | DT |\n|  | Defined estimated work effort for story delivery. | DT |\n|  | Ensure that all tasks are required for delivery; consider any tasks not listed that are crucial to the target outcomes. | DT |\n|  | Considering all planned tasks, determine if the work effort is still appropriately sized. | PO / DT |\n\nSPRINT BACKLOG VERIFICATION  \n\n| X | AGENDA ITEM | OWNER |\n| --- | --- | --- |\n|  | Consider any conflicts between individual stories in the sprint backlog. Find resolutions and make adjustments. | DT |\n|  | Ensure that everything from the team’s Definition of Done is being considered and is achievable. | DT |\n|  | Identify anything deemed “missing” from the backlog. Consider maintenance activities, overhead items, spikes, etc. | DT / PO |\n|  | Incorporate missing backlog items and make any necessary adjustments to the sprint. | DT / PO |\n|  | Ensure that all potential risks have been identified along with plans for resolution . | DT |\n|  | Discuss the team’s commitment to the sprint plan and delivery intent. | DT |\n|  | Ensure that the Task Board and Burndown Setup successfully capture the sprint and are ready to use. | DT / SM |\n\nSUMMARY  \n\n| X | AGENDA ITEM | OWNER |\n| --- | --- | --- |\n|  | Update the task board / agile tool with designated tasks. | DT |\n|  | Define what each team member is tasked with following the meeting. | DT |\n|  | Address any issues noted throughout the meeting for discussion before closing. | SM |\n|  | Document any issues designated for discussion or follow-up outside of the meeting ","cbCaivtTHPGgkicI","https://ap.wps.com/l/cbCaivtTHPGgkicI","pdf",103225,"English","# Introduction\n# Sprint Goal & User Stories\n# Sprint Backlog\n# Sprint Backlog Verification\n# Summary\n# Additional Items","[{\"question\":\"Who is required to attend the sprint planning meeting?\",\"answer\":\"The required invitees are the ScrumMaster/facilitator (SM), the Product Owner/goal and priority setter (PO), and the Development Team (DT).\"},{\"question\":\"What inputs does the meeting cover to define the sprint goal and scope?\",\"answer\":\"The agenda includes a situation overview, the sprint goal and accomplishment metric, sprint capacity based on velocity and experience, story points, effective working hours, special circumstances, and a candidate backlog review to ensure readiness and clarity.\"},{\"question\":\"How does the agenda verify the sprint backlog is ready to execute?\",\"answer\":\"It includes checking for conflicts between stories, ensuring Definition of Done items are considered and achievable, identifying missing backlog items and making adjustments, confirming risks are identified with resolution plans, reviewing team commitment, and verifying the task board and burndown setup are ready.\"}]","Sprint Planning Meeting Agenda - Meeting Agenda | PDF",1789258876]