[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-250758-105":53,"doc-detail-250758-en":119},{"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":112,"head_meta":114,"extra_data":116,"updated_unix":118},105,"en","rapid-release-planning-session-workshop-rapid-release-planning","Rapid Release Planning Session & Workshop - Rapid Release Planning","","Rapid Release Planning Session & Workshop outlines roles and processes for accelerating product delivery within an Agile environment. It emphasizes recognizing prior progress, aligning with corporate vision, and using executive roadmaps to guide near-term delivery. The materials define responsibilities of the Product Owner, describe three analyst types supporting backlog creation, and explain the Product Ownership Cloud for large organizations. It further presents guidance for writing strong user stories using INVEST attributes such as independent, negotiable, valuable, testable, estimable, and appropriately sized stories.",{"@graph":63,"@context":111},[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/rapid-release-planning-session-workshop-rapid-release-planning/250758/",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/rapid-release-planning-session-workshop-rapid-release-planning/250758.png","ImageObject",442,249,{"name":88,"@type":89},"Paura","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-29","2026-09-12",true,{"@type":98,"interactionType":99,"userInteractionCount":101},"InteractionCounter",{"@type":100},"ViewAction",13,{"@type":103,"mainEntity":104},"FAQPage",[105],{"name":106,"@type":107,"acceptedAnswer":108},"What are the three types of Agile analysts and what do they contribute?","Question",{"text":109,"@type":110},"Technical analysts assess technological feasibility, functional analysts understand how the product works and business direction, and business analysts focus on customer needs and negotiate features into the product.","Answer","https://schema.org",{"og:url":78,"og:type":113,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":115,"canonical":78},"index,follow",{"doc_id":117,"site_id":56},250758,1789256089,{"code":4,"msg":5,"data":120},{"doc_id":117,"user_id":121,"nickname":88,"user_avatar":122,"doc_module":9,"category_id":8,"category_name":11,"doc_title":59,"doc_description":61,"doc_content":123,"file_id":124,"file_url":125,"file_type":126,"file_size":127,"view_count":101,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":128,"language":129,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":130,"faqs":131,"seo_title":132,"seo_description":61,"update_tm":118,"read_time":25},13056712833777,"https://ap-avatar.wpscdn.com/davatar_29158cc5080c5b710cf443261637dec0","Rapid Release Planning Session & Workshop  \nV. Lee Henson CST  \n1  \nV. Lee Henson CST  \n✤ Certified Scrum Trainer  \n✤ ADDIE Training Professional  \n✤ Agile Coach & Trainer  \n✤ Author of Agile Mentor Newsletter (Published Monthly)  \n✤ Author of The Definitive Agile Checklist  \n✤ Inventor of Rapid Release Planning  \n✤ Former Chairperson of the Scrum Alliance Certification Advisory Board  \n✤ Information Technology / Psychology Background  \nCopyright 2011 Davisbase LLC.  \n2  \nThe Setup:  \nCopyright 2011  \nDavisbase LLC.  \n3  \nWhen & Who Are We?:  \n✤ It is CRITICAL to recognize what has happened so far in the process and where we are now while we are performing these actions:  \n✤ 1) The corporate and product / project vision has been established. Teams have been exposed to this leadership position .  \n✤ 2) With the help of executive leadership we have laid out aroadmap outlining what items we anticipate will be delivered in the next few quarters . Teams are exposed to the roadmap to provide technical input.  \n✤ 3) The product Ownership Group, (PO, BA, FA, TA, Etc.), get together to brainstorm and create cards for candidates to be selected from for the upcoming release .  \nCopyright 2011  \nDavisbase LLC.  \n4  \nProduct Owner:  \n✤ Responsible for: Creation and maintenance of a stack ranked product backlog.  \n✤ Gathering of customer, business, and technical requirements and filtering them down to a single product backlog.  \n✤ Full understanding of the product and the process .  \n✤ Maintaining upward visibility.  \n✤ Representation of customer and or sponsor to the end team  \nCopyright 2011  \nDavisbase LLC.  \n5  \nAgile Analysts:  \n✤ There are 3 types of analysts to assist the product owner in creation and maintenance of the product backlog:  \n✤ 1) Technical Analyst-This analyst understands the way that the current product is built and can assist in determining technological feasibility of future enhancements .  \n✤ 2) Functional Analyst-This analyst knows exactly how the current product works and understands the direction in which the business hopes to take the future of the product. This analyst is also typically very savvy about how end users typically use the product.  \n✤ 3) Business Analyst-This analyst has a deep understanding of the customers wants, needs, and desires . They often negotiate with the business to get features into the product that the customer will actually use .  \nCopyright 2011  \nDavisbase LLC.  \n6  \nThe Product Ownership Cloud:  \n✤ A single product owner would have a very difficult time meeting the needs of a large organization.  \n✤ Many organizations introduce the concept of a product ownership cloud.  \n✤ Chief Product Owners lead the charge by capturing corporate direction and working towards implementation through multiple product owners .  \n✤ Each product owner works with a team of analysts and market specialists to best define the requirements .  \n✤ Architects or Principle Developers are often engaged early to determine technological feasibility and framework are in place .  \n✤ The team becomes involved at the release planning phase.  \n7  \nCopyright 2011 Davisbase LLC.  \nThe Product Ownership Cloud  \nPO  \nCPO  \nPO  \nPO  \nTA FA BA TA FA BA TA FA BA  \nCopyright 2011 Davisbase LLC.  \n8  \nWriting Great User Stories:  \nCopyright 2011  \nDavisbase LLC.  \n9  \nINVEST-Attributes of a Good Story  \n|  |  |\n| --- | --- |\n| Independent\u003Cbr>Avoid dependencies with other stories\u003Cbr>Write stories to establish foundation\u003Cbr>Combine stories if possible to deliver in a single iteration | Estimable\u003Cbr>Enough detail should be listed to allow the team to estimate\u003Cbr>The team will encounter problems estimating if the story is too big, if insufficient information is provided, or if there is a lack of domain knowledge |\n| Negotiable\u003Cbr>Stories are not a contract\u003Cbr>Too much detail up front gives the impression that more discussion on the story is not necessary\u003Cbr>Not every story must be negotiable, constraints may exist that prevent it |","cbCaijPm6OK1zAFo","https://ap.wps.com/l/cbCaijPm6OK1zAFo","pdf",4655908,42,"English","# The Setup\n# When & Who Are We?\n# Product Owner\n# Agile Analysts\n# The Product Ownership Cloud\n# Writing Great User Stories\n## INVEST-Attributes of a Good Story","[{\"question\":\"What are the three types of Agile analysts and what do they contribute?\",\"answer\":\"Technical analysts assess technological feasibility, functional analysts understand how the product works and business direction, and business analysts focus on customer needs and negotiate features into the product.\"}]","Rapid Release Planning Session & Workshop - Rapid Release Planning | PDF"]