What are the knowledge areas of Project Scope Management?

i agree with Mr yakop , ayoub , alex..

Developing the project charter

Developing the project management plan

Directing and managing project execution

Monitoring and controlling project work

Performing integrated change control

Closure of the project or its phase

For managing all these facets, a project manager must be skillful at integration management; else the project may hit the skids.

According to the PMBOK, scope management has six processes:

1. Plan Scope Management: Planning the process, and creating a scope management plan.
2. Collect Requirements: Defining and documenting the stakeholder’s needs.
3. Define Scope: Developing a detailed project scope statement.
4. Create WBS: Subdividing project deliverables into smaller work units.
5. Validate Scope: Formalizing the acceptance of the deliverables.
6. Control Scope: The ongoing process of monitoring and managing changes to the project scope.

The knowledge area of Project Scope Management consists of the following processes -

Scope Management Processes

Plan Scope Management

Collect Requirements

Define Scope

Create WBS

Validate Scope

Control Scope

The knowledge area of Scope Management includes the processes required to ensure that the project includes all the work, and only all the work required to complete the project successfully. It is primarily concerned with controlling what is and what is not in the scope.

Respect Excellent answers.

A. Project Planning: Collection of data and requirements--Defining scope of the project--Create WBS.

B.Project Control--Verifying and controlling the scope.

• 3. Product Scope Versus Project ScopeProduct scope refers to the features,characteristics and functions of the product,service or result.Project scope refers to all the work to be donein order to create the product, service orresult.
• 4. Gold plating Versus Scope creep Vs
• 5. Gold plating Versus Scope creepGold plating - comes into play when team introducesfunctionality or feature not scoped from the requirementsdocuments, because they consider it to be useful to customeror end users. Customer may end up asking such feature to beremoved from deliverable, which may increase cost, time andeffort.Scope creep - happens when team agrees to introduce asmall feature request made by customer (or any stakeholder)without letting it come through change control process. Andsoon enough this change snow-balls into something really big.Since it was not planned initially, such changes will end uptaking lot of effort, time and resources, potentially impactingone or more project constraints.
• 6. Collect Requirements process
• 7. Collect Requirements process..is simply about understanding theneeds of stakeholders that shouldbe fulfilled by the project.
• 8. Collect Requirements process• Inputs - project charter document and stakeholder register. Project charter is required as it contains the high level business needs to refer to. Stakeholder register is required in order to know who to talk to for understanding requirements.• Tools & Techniques – Quite a few. Including interviews, focus groups, facilitated workshops, group creativity techniques, group decision making techniques, questionnaires and surveys, observations and prototypes.• Outputs - requirements documents, requirement management plan, and traceability matrix.
• 9. Download this poster from this post!
• 10. Requirements Management PlanIs a document that,• explains how requirements are analyzed, documented and managed• defines how configuration management is to be done• shows how product metrics are used• defines traceability structure
• 11. What is Requirements Traceability Matrix (RTM)RTM is the way in which baselined requirementsare linked across different baselined data suchas use case, design, test plan and test case.
• 12. Define Scope process
• 13. Define Scope process• Inputs - project charter, requirements documentation, organizational process assets• Tools & Techniques - expert judgment, product analysis, alternative identification and facilitated workshops• Outputs - Project scope statement, project document updates
• 14. Download from this post!
• 15. Create WBS process
• 16. Create WBS processWBS stands for Work BreakdownStructure.This process is about representingdelivery-oriented hierarchicaldecomposition of the work to bedone on the project.
• 17. Create WBS process• Inputs of this process are quite logical - project scope statement and requirements documentation. Then there are organizational process assets to the help!• There is only one from tools and techniques - Decomposition• No surprise on the outputs -WBS, WBS dictionary and scope baseline, and project document updates
• 18. What is100% ruleA completed WBS represents all the deliverables of theproject - including the outcome of project managementactivities, such as documents and plans.If you are at the leaf node of the WBS (one that does nothave further child nodes) and roll up all of the nodes intotheir parent, and roll up parents into their parents, till allthe way up - it would cover ALL of the work that projectteam ever does. Hence this technique ensures that teamdoes only requirements related work, nothing more,nothing less. This is100% rule.
• 19. Sample WBS
• 20. Verify Scope process
• 21. Verify Scope processThis process is about formallyaccepting completed projectdeliverables.
• 22. Verify Scope process• Inputs - Validated deliverables, requirements documentation, requirements traceability matrix, project management plan.• Tools and Techniques - Inspection.• Outputs - accepted deliverables, change requests(when deliverables are not matching requirements), and changes to project documents.
• 23. Control Scope process
• 24. Control Scope processThis process is about monitoringstatus of the project and managingchanges to scope baseline.
• 25. How is a Change implemented?
• 26. Control Scope process• Inputs - project management plan, work performance information, requirements documentation, requirement traceability matrix, organizational process assets.• Tools and Techniques - variance analysis.• Outputs - work performance measurements, organizational process assets updates, change requests, project management plan updates, project documents updates.

Scope Management knowledge areas has 5  processes:

• Collect Requirements
• Define Scope
• Create WBS
• Verify Scope
• Control Scope