[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-243794-105":53,"doc-detail-243794-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","moscow-technique-template-prioritisation-categories-must-haveshould-havecould-havewont-have","MoSCoW Technique Template - Prioritisation Categories - Must Have/Should Have/Could Have/Won't Have","","MoSCoW Technique Template provides a structured prioritisation framework for project planning by organizing tasks and features into four clear categories: Must Have, Should Have, Could Have, and Won't Have. The template captures each item’s unique ID, description, and rationale for why it belongs to a given priority level, alongside the responsible person or team for delivery. It also records the project name, objectives and scope overview, session date, participants, and a notes section for constraints and additional considerations.",{"@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/moscow-technique-template-prioritisation-categories-must-haveshould-havecould-havewont-have/243794/",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/moscow-technique-template-prioritisation-categories-must-haveshould-havecould-havewont-have/243794.png","ImageObject",442,249,{"name":88,"@type":89},"Arica Lee","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-19","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 MoSCoW Technique used for in this template?","Question",{"text":109,"@type":110},"It structures how tasks or features are prioritised during planning by placing them into Must Have, Should Have, Could Have, and Won't Have categories.","Answer",{"name":112,"@type":107,"acceptedAnswer":113},"What fields are captured for each prioritisation category item?",{"text":114,"@type":110},"Each item includes an ID, description, rationale for the priority decision, and the responsible person or team.",{"name":116,"@type":107,"acceptedAnswer":117},"How does the template handle items excluded from the current scope?",{"text":118,"@type":110},"For Won't Have, it includes an explanation and rationale for exclusion and a note on whether it may be considered in future phases or releases.","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},243794,1791745651,{"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":73,"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},8796096645457,"https://ap-avatar.wpscdn.com/avatar/800003749518d68ffe3?x-image-process=image/resize,m_fixed,w_180,h_180&k=1779345340919836971","MoSCoW Technique Template  \nProject Name:  \nProject Description: A brief overview of the project objectives and scope.  \nDate: Current date or the date of the prioritisation session.  \nParticipants: List of stakeholders involved in the prioritisation process.  \nPrioritisation Categories  \nMust Have  \nID: Unique identifier for the task/feature.  \nDescription: A brief description of the task/feature.  \nRationale: Reason why it's considered a Must Have.  \nResponsible: Person or team responsible for delivering this requirement.  \nShould Have  \nID: Unique identifier for the task/feature.  \nDescription: A brief description of the task/feature.  \nRationale: Reason why it's considered a Should Have.  \nResponsible: Person or team responsible for delivering this requirement.  \nCould Have  \nID: Unique identifier for the task/feature.  \nDescription: A brief description of the task/feature.  \nRationale: Reason why it's considered a Could Have.  \nResponsible: Person or team responsible for delivering this requirement.  \nWon't Have  \nID: Unique identifier for the task/feature.  \nDescription: Explanation of the task/feature and why it won't be included in the current project scope.  \nRationale: Reason for exclusion from the current project scope.  \nPossible Future Consideration: Whether it might be considered in future phases/releases.  \nNotes  \nSpace for any additional notes, considerations, or constraints relevant to the prioritisation process.  \nFor more templates and techniques visit our ITSM free resources page.","cbCaioaBpxTw9JdX","https://ap.wps.com/l/cbCaioaBpxTw9JdX","pdf",47045,"English","# MoSCoW Technique Template\n## Project information\n## Prioritisation categories\n## Notes","[{\"question\":\"What is the MoSCoW Technique used for in this template?\",\"answer\":\"It structures how tasks or features are prioritised during planning by placing them into Must Have, Should Have, Could Have, and Won't Have categories.\"},{\"question\":\"What fields are captured for each prioritisation category item?\",\"answer\":\"Each item includes an ID, description, rationale for the priority decision, and the responsible person or team.\"},{\"question\":\"How does the template handle items excluded from the current scope?\",\"answer\":\"For Won't Have, it includes an explanation and rationale for exclusion and a note on whether it may be considered in future phases or releases.\"}]","MoSCoW Technique Template - Prioritisation Categories - Must Have/Should Have/Could Have/Won't Have | PDF",1789208672]