PROJSECT SCOPE MANAGEMEN PROCESSES

Project scope management includes the processes required to ensure that the
project includes all the work required and only the work required to complete
the project successfully. Its primary concerns is with defining and controlling
what is and not included in the project.
Scope refers to all the work involved in creating the deliverables of the project
and the processes used to create them.
Product scope is the features and functions that categorize product, service or
result. The product scope is all the product itself. It means the product scope
defines.
How the product look like?
How will it work?
What are its product features?
Project scope is the work performed to deliver the product, service and result
with specified features and functions (meetings, reports, analysis, design
documents)
The project scope is all the project and is also known as scope statements. It
defines the requirements of products, work required to create the product.
Defines what is in the scope or not.
Example: if we are told to build a application. We exactly need to know what
we need to do nothing else.
Project scope is more work oriented (How?), than product scope is more
oriented towards functional requirements (what?).

Collect Requirements: it is the first process is project scope management
knowledge area. It is process of determining, documentation and managing
stakeholder needs and requirements to meet project objective.
The key benefit is to provide the basis for defining and managing the project
scope. Its requirements includes the quantified and documented needs and
expectations of the sponsor, customer and other stakeholders. All the

requirements must be analyzed and recorded in a clear and detailed way to be
measured.
Below are the inputs of the process scope management
1. Scope management plan.
2. Stakeholder management plan.
3. Stakeholder register.
Tools and Techniques:
1. Interviews
2. Focus groups
3. Facilitated workshops.
4. Group creativity techniques.
5. Group decision making techniques.
6. Questionnaires & surveys
7. Observations
8. Prototypes.
OUTPUTS
1. Requirement documentation
2. Requirements traceability matrix.

Process scope management is define scope it develops detailed description of
project scope and product scope. It describes the project, service or result
boundaries by defining which of the requirements collected will be included in
and excluded from the project scope.
Inputs
1. Project charter.
2. Requirement documentation
3. Organization process assets.
Tools and techniques
1. Expert judgment
2. Product analysis
3. Alternatives identification.
Output

1. Project scope statement.

Next process in scope management is to create work breakdown structure it is
process of subdiving project deliverables and project work into smaller
manageable components. It provides a structured vision of what has to be
delivered.
Inputs
1. Scope management plan
2. Project scope statement
3. Requirements documentation.
Tools & Techniques
1. Decomposition
Output
1. Work breakdown structure.
2. WBS dictionary
3. Scope baseline

Control scope this process ensures that only IN Scope work is delivered and
scope creep is avoided.
It doesn’t mean that all changes must follow the change control process and all
changes must take into consideration on impact of schedule, cost , quality,
resources, risk and so forth.
Inputs
1. Scope baseline
2. Scope management plan
3. Change management plan
4. Requirements traceability matrix
5. Organizational process assets.
Tool and techniques
1. Variance analysis.

Output
1. Work performance information.
2. Change requests.
3. Scope baseline updates.