[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-seo-244578-105":3,"detail-sidebar-cat-1-en-105":80,"doc-detail-244578-en":126},{"code":4,"msg":5,"data":6},0,"ok",{"site_id":7,"language":8,"slug":9,"title":10,"keywords":11,"description":12,"schema_data":13,"social_meta":73,"head_meta":75,"extra_data":77,"updated_unix":79},105,"en","project-scope-management-processes-requirements-and-wbs","Project Scope Management - Processes, Requirements and WBS","","Project scope management defines and controls what is included and excluded in a project to prevent scope creep and align stakeholders on requirements. It covers the core processes: planning scope management, collecting and validating requirements, defining scope, creating the WBS, and controlling scope changes. The document explains requirement types, methods to gather requirements (interviews, focus groups, surveys, observation, prototyping, benchmarking), and key artifacts like the scope management plan, requirements management plan, RTM, scope statement, and WBS.",{"@graph":14,"@context":72},[15,34,55],{"@type":16,"itemListElement":17},"BreadcrumbList",[18,23,27,31],{"item":19,"name":20,"@type":21,"position":22},"https://docshare.wps.com","Home","ListItem",1,{"item":24,"name":25,"@type":21,"position":26},"https://docshare.wps.com/template/","Template",2,{"item":28,"name":29,"@type":21,"position":30},"https://docshare.wps.com/template/general/","General",3,{"item":32,"name":10,"@type":21,"position":33},"https://docshare.wps.com/template/project-scope-management-processes-requirements-and-wbs/244578/",4,{"url":32,"name":10,"@type":35,"image":36,"author":41,"headline":10,"publisher":44,"fileFormat":47,"inLanguage":8,"description":12,"dateModified":48,"datePublished":49,"encodingFormat":47,"isAccessibleForFree":50,"interactionStatistic":51},"DigitalDocument",{"url":37,"@type":38,"width":39,"height":40},"https://docshare.wps.com/thumbnails/project-scope-management-processes-requirements-and-wbs/244578.png","ImageObject",442,249,{"name":42,"@type":43},"4398046744996","Person",{"url":19,"name":45,"@type":46},"DocShare","Organization","application/pdf","2026-09-20","2026-09-12",true,{"@type":52,"interactionType":53,"userInteractionCount":22},"InteractionCounter",{"@type":54},"ViewAction",{"@type":56,"mainEntity":57},"FAQPage",[58,64,68],{"name":59,"@type":60,"acceptedAnswer":61},"What is project scope management and why is it important for IT projects?","Question",{"text":62,"@type":63},"Project scope management defines and controls what is included and not included in a project. It helps verify deliverables, avoid scope creep, and ensure everyone understands the project requirements.","Answer",{"name":65,"@type":60,"acceptedAnswer":66},"What outputs are produced during planning scope management?",{"text":67,"@type":63},"Key outputs include the scope management plan and the requirements management plan. They describe how the scope statement and WBS are created and maintained, and how requirements are analyzed and managed.",{"name":69,"@type":60,"acceptedAnswer":70},"How are requirements collected, and what methods are listed?",{"text":71,"@type":63},"Requirements are collected using approaches such as stakeholder interviews, focus groups, questionnaires and surveys, observation, prototyping, and benchmarking. Each method has advantages and drawbacks related to cost, speed, accuracy, and resource needs.","https://schema.org",{"og:url":32,"og:type":74,"og:title":10,"og:site_name":45,"og:description":12},"article",{"robots":76,"canonical":32},"index,follow",{"doc_id":78,"site_id":7},244578,1789219173,{"code":4,"msg":81,"data":82},"success",[83,88,93,98,103,108,113,118,123],{"id":84,"doc_module":22,"doc_module_name":25,"category_name":85,"show_sort_weight":86,"slug":87},11,"Presentations",90,"presentations",{"id":89,"doc_module":22,"doc_module_name":25,"category_name":90,"show_sort_weight":91,"slug":92},12,"Resumes",80,"resumes",{"id":94,"doc_module":22,"doc_module_name":25,"category_name":95,"show_sort_weight":96,"slug":97},14,"Invoices",70,"invoices",{"id":99,"doc_module":22,"doc_module_name":25,"category_name":100,"show_sort_weight":101,"slug":102},15,"Posters",60,"posters",{"id":104,"doc_module":22,"doc_module_name":25,"category_name":105,"show_sort_weight":106,"slug":107},16,"Social Media",50,"social-media",{"id":109,"doc_module":22,"doc_module_name":25,"category_name":110,"show_sort_weight":111,"slug":112},17,"Forms",40,"forms",{"id":114,"doc_module":22,"doc_module_name":25,"category_name":115,"show_sort_weight":116,"slug":117},18,"Letters",30,"letters",{"id":119,"doc_module":22,"doc_module_name":25,"category_name":120,"show_sort_weight":121,"slug":122},21,"Paper Templates",5,"papers-templates",{"id":124,"doc_module":22,"doc_module_name":25,"category_name":29,"show_sort_weight":4,"slug":125},158,"general-158",{"code":4,"msg":81,"data":127},{"doc_id":78,"user_id":128,"nickname":42,"user_avatar":11,"doc_module":22,"category_id":124,"category_name":29,"doc_title":10,"doc_description":12,"doc_content":129,"file_id":130,"file_url":131,"file_type":132,"file_size":133,"view_count":22,"is_deleted":4,"is_public":22,"is_downloadable":22,"audit_status":22,"page_count":33,"language":134,"language_code":8,"site_id":7,"html_lang":8,"table_of_contents":135,"faqs":136,"seo_title":137,"seo_description":12,"update_tm":79,"read_time":26},4398046744996,"Scope refers to all the work involved in creating the product, service or result of the project and the processes involved in creating them.  \nDeliverable is anything produced as part of the project. Eg. some hardware or software, project documents  \nProject scope management involves defining and controlling the things included and not included in a project. It is important for IT projects because it aims to verify deliverables, avoid scope creep, and ensure that everyone has the same understanding of the project requirements.  \nProject scope management processes:  \n1. Planning scope management – determining how scope and requirements will be managed  \n2. Collecting requirements – defining and documenting the features and functions of the products, and how they will be created  \n3. Defining scope – reviewing the project charter, requirement documents, and organisational process assets to create a scope statement  \n4. Creating the WBS – subdividing project deliverables into more manageable components  \n5. Validating scope – formalising acceptance of the project deliverables  \n6. Controlling scope – managing and controlling changes to the scope  \nPlanning scope management  \nThere are two important outputs for planning scope management:  \n- Scope management plan – a document that details how to create a scope statement, how to create WBS, how to maintain and approve the WBS, how to achieve scope validation, and how to control change requests to the scope  \n- Requirements management plan – documents how the project requirements will be analysed, documented and managed  \nRequirement: a condition that must be met by the project to satisfy an agreement or a formal specification. A requirement must be defined, analysed and documented in enough detail to be included in the scope baseline, and it must also be measurable.  \nCollecting requirements  \nThis process is often the most difficult because requirements can change over time, and users often don’t really know what they need from the beginning, and instead give brief descriptions of what they want. Users may also not share information from the beginning due to cultural or political environments.  \nTasks involved in collecting requirements:  \n- Elicitation – determining what the requirements are  \n- Analysis – determining how to achieve the requirements  \n- Specification – coming up with a clear definition and description of what the requirement is  \n- Validation – having the requirement approved by the appropriate stakeholders  \nMethods for collecting requirements:  \n1. Interviewing stakeholders  \na. Pros – one-on-one is very effective for collecting detailed requirements  \nb. Cons – costly and time-consuming. Interviewers need to know what to ask, otherwise stakeholders won’t know what information to provide. Interview can’t be prejudice.  \n2. Focus groups  \na. Pros – faster and less expensive than one-on-one interviews  \nb. Cons – untrained facilitators may elicit negative or inadequate responses  \n3. Questionnaires and surveys  \na. Pros – gets the information needed as long as stakeholders provide honest answers  \nb. Cons – respondents might not provide accurate answers or misinterpret the question  \n4. Observation  \na. Pros – good for projects that aim to improve work processes and operations  \nb. Cons – requires people to observe, which can be expensive and time-consuming. Observations could be misinterpreted  \n5. Prototyping  \na. Pros – good for software development projects, helps clarify interfaces and boundaries  \nb. Cons – time-consuming and requires documentation, which can disrupt the flow of a process  \n6. Benchmarking  \na. Pros – generates ideas by comparing project practices or other project characteristics with other projects or products that may or may not be from other organisations  \nb. Cons – requires deep amount of research, which is costly and time-consuming  \nFunctional vs Non-functional requirements  \n- Functional – describes what the system should do  \n- Non","cbCaiaylgYuTsruP","https://ap.wps.com/l/cbCaiaylgYuTsruP","pdf",190546,"English","# Project Scope Management\n## Planning scope management outputs\n## Collecting requirements and methods\n## Functional vs non-functional requirements\n## Requirements Traceability Matrix (RTM)\n## Project scope statement\n## Work Breakdown Structure (WBS)\n## Methods for developing a WBS","[{\"question\":\"What is project scope management and why is it important for IT projects?\",\"answer\":\"Project scope management defines and controls what is included and not included in a project. It helps verify deliverables, avoid scope creep, and ensure everyone understands the project requirements.\"},{\"question\":\"What outputs are produced during planning scope management?\",\"answer\":\"Key outputs include the scope management plan and the requirements management plan. They describe how the scope statement and WBS are created and maintained, and how requirements are analyzed and managed.\"},{\"question\":\"How are requirements collected, and what methods are listed?\",\"answer\":\"Requirements are collected using approaches such as stakeholder interviews, focus groups, questionnaires and surveys, observation, prototyping, and benchmarking. Each method has advantages and drawbacks related to cost, speed, accuracy, and resource needs.\"}]","Project Scope Management - Processes, Requirements and WBS | PDF"]