1- Explain Project Scope

Ans. Project scope is the part of project planning that involves determining and documenting a
list of specific project goals, deliverables, tasks, costs and deadlines. ... The scope statement also
provides the team with guidelines for making decisions about change requests during the
project.

2- Project scope Management

Ans. Project scope management is a process that helps in determining and documenting the list
of all the project goals, tasks, deliverables, deadlines, and budgets as a part of the planning
process. In project management, it is common for a big project to have modifications along the
way.

With the scope in the project management defined right in the beginning, it becomes much
easier for teams to manage and make the required changes.

3- Explain project scope management process according to PMBOK

Ans. Scope management, or rather the lack of it, is one of the biggest reasons for project failure.
Correctly defining what is and is not included in the project is absolutely foundational to good
project management. I’ve seen many projects go south even though they had the right
expertise, schedule, high quality deliverables, and even satisfied clients. But if the dreaded
“scope creep” bug is allowed to fester and multiply, all of your other amazing project
accomplishments will be as good as tossed out the window.

As a project manager, you must understand the importance of project scope.

Project scope management is the second knowledge area in the Project Management Institute’s
(PMI) Project Management Body of Knowledge (PMBOK). It includes the processes that ensure
all of the required work (and only the required work!) is included in the project.

project scope management overview

PMBOK’s scope management process flow diagram

According to the PMBOK, scope management has six processes:

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

4- Why project scope management is important

 Ans. Managing the expectations of clients and stakeholders can be one of the most difficult
tasks a project manager can face. With a distinct scope, it helps everyone to stay on the same
page throughout the life cycle of the project. A well-defined scope can help to avoid common
problems like:

-Requirements that constantly change

-Requirements that need a rethink mid-project
-The final outcome not being what the client expected
-The budget overrunning
-The project is way behind schedule

Effective scope management can help to avoid some of these issues by clearly defining and
communicating the scope to all parties involved in the project. Project scope helps to distinguish
what is and is not involved in the project and controls what is allowed or removed as it is
executed. Scope management establishes control factors, that can be used to address elements
that result in changes during the lifecycle of the project.

5- Explain plan scope management

Ans. In the first process in project scope management, you create a scope plan document that
you can refer to in the later stages. The document mainly helps in defining, managing,
validating, and controlling the project’s scope.

It includes:

-Detailed project scope statement

-Breakdown of all the project requirements
-Expected project deliverables
-Change control process

The document doesn’t have to be very detailed, it just has to fit the purpose. You can also use a
previous project’s scope management plan as a reference for this.

6- Explain Collect requirements process

Ans. The next step is to workout stakeholder requirements and expectations. You will be
required to document all the project requirements, expectations, budgets, and deliverables
through interviews, surveys, and focus groups.

This is a rather important step because more often than not, stakeholders can have unrealistic
requirements or expectations and the project managers would be required to step in to find a
solution that is acceptable by everyone from avoiding project delays.

At the end of the collection requirements stage, you should have the following:

Functional as well as non-functional requirements

 -Stakeholder requirements
-Business requirements
-Support and training requirements
-Project requirements

7- Explain Scope definition process

Ans. At this step, you need to turn your requirements into a well-detailed description of the
service or product that you are trying to deliver through the project. You will then have a project
scope statement that you can then refer to throughout your project.

While it is important to list what is in the scope of the project, it is just as important to note
down what is out of the project scope. Any kind of inclusions to the scope would then have to
go through the entire change control process to ensure the team is only working on things that
they are supposed to work on.

With a defined scope, you get a reference point for your project team and anyone else involved.
In case there is something that is not involved in the scope, it doesn’t need to be completed by
the team.

8- Explain Project scope statement.

Ans. The Project Scope Statement provides the documented basis for making all project
decisions and is used to direct the project effort and communicate the project scope to the
project team and other project stakeholders. Projects that do not have a Project Scope
Statement are plagued with scope creep issues.

9- Explain Work Breakdown Structure (WBS) process

Ans. Work breakdown structure (WBS) in project management is a method for completing a
complex, multi-step project. It's a way to divide and conquer large projects to get things done
faster and more efficiently.

The goal of a WBS is to make a large project more manageable. Breaking it down into smaller
chunks means work can be done simultaneously by different team members, leading to better
team productivity and easier project management.

In Wrike, you can build a WBS by creating folders and subfolders and can go further to divide
individual tasks into subtasks.

A work-breakdown structure (WBS) in project management and systems engineering, is a

deliverable-oriented breakdown of a project into smaller components. A work breakdown
structure is a key project deliverable that organizes the team's work into manageable sections.

10- Explain validate and control scope process

Ans. Validate Scope is the process of formalizing acceptance of the completed project
deliverables. The key benefit of this process is that it brings objectivity to the acceptance
process and increases the chance of final product, service, or result acceptance by validating
each deliverable. Control Scope is the process of monitoring the status of the project and
product scope and managing changes to the scope baseline. The key benefit of this process is
that it allows the scope baseline to be maintained throughout the project.