Scribd
Upload
11 views32 pages

03 Project Scope Management

Project Scope Management involves developing a scope management plan, assessing project requirements, and creating a work breakdown structure (WBS) to ensure all necessary work is included for project success. It encompasses processes such as collecting requirements, defining scope, and validating deliverables, while distinguishing between product scope and project scope. Effective scope definition and management are crucial to avoid scope creep and ensure clear communication among stakeholders.

Uploaded by

Muhammad Saud Dar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
11 views32 pages

03 Project Scope Management

Project Scope Management involves developing a scope management plan, assessing project requirements, and creating a work breakdown structure (WBS) to ensure all necessary work is included for project success. It encompasses processes such as collecting requirements, defining scope, and validating deliverables, while distinguishing between product scope and project scope. Effective scope definition and management are crucial to avoid scope creep and ensure clear communication among stakeholders.

Uploaded by

Muhammad Saud Dar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 32

Project Scope

Management
Project Scope Management

• Once all the stakeholders for a project have been identified, the project team
members develop a scope management plan, assess project requirements,
develop the project’s scope, and create a work breakdown structure (WBS).

• 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.
Project Scope Management
Project Scope Processes

• Project Scope Management processes (per PMBOK)


• Plan Scope Management
• Collect Requirements
• Define Scope
• Create WBS
• Validate Scope
• Control Scope
Project Scope Processes
Project Scope Management

Product Scope + Project Scope


• Product Scope: Outputs, the team will deliver to its customer.
• Project Scope: The work needed to be performed in order to deliver the
project’s outputs

• Project Scope is more work-oriented, (the hows,) while Product Scope is more
oriented toward functional requirements. (the whats.)
Project Scope Management
Product Scope & Project Scope

Product Scope = "What the app will include."


Project Scope = "What work needs to be done to develop and launch the app.

• Product Scope: The mobile app will include user authentication, in-app
messaging, location tracking, and push notifications."
• Project Scope: The project will involve designing the user interface,
developing the backend for user authentication, integrating location services,
testing the app, and deploying it to the app store, to be completed within 6
months.
Planning Scope Management

The purpose of the process of planning scope management is to determine how the project
scope will be defined, validated, and controlled.
• Validation: Means formal acceptance of deliverables
• Verification: Means the deliverable complies with a regulation, requirement or
specification.

"Are we building the product right?“ "Are we building the right


product?"
Collect Requirements

• Collecting requirements is a systematic effort to understand and


analyze stakeholder needs to define and document these
requirements.
• The PMBOK® Guide – Sixth Edition, defines a requirement as “a
condition or capability that is necessary to be present in a product,
service, or result to satisfy a business need.
Collect Requirements

• Collect Requirements process includes gathering and documenting stakeholder


needs and expectations.
• The process involves documenting project and product features and functions.
• Vague requirements is a common reason for project failure. Therefore, it is
critical for you to implement the Collect Requirements process accurately.
• The output of this process sets the foundation for cost, schedule, and quality
planning.
Scope Definition

• Good scope definition is crucial to project success because it.


o Helps improve the accuracy of time, cost, and resource estimates
o Defines a baseline for performance measurement and project control
o Aids in communicating clear work responsibilities

• A project scope statement describes product characteristics and requirements, user


acceptance criteria, and deliverables.

o Work that is not included in the scope statement should not be done.
o May explicitly state what is out of scope for the project under a section called project exclusions.
Project Scope Statement

• A successful project scope statement should be concise and clear.


• Anyone reading the statement should have a good idea of what the project
consists of (and what will not be part of the project).
• Scope statement will give a view of the project.
• It is also important to be specific in a project scope statement. For example,

• "The catalog will feature 100 products" is better than "The catalog will feature many
products" and
• "The project will be completed over six months" is preferable to "The project will be
completed over a period of time." The more specific you can be, the better.
Example: Writing a scope statement?
University Technology Upgrades

Initial Scope Statement

University X wants to upgrade its facilities to include WiFi


technologies accessible anywhere on campus. This project will
offer students, faculty, and staff the ability to be productive from
anywhere on campus. The project will take place over a time
period in which measurable results will be achieved.

http://www.brighthubpm.com/project-planning/57950-example-and-evaluation-of-project-scope-statements/
Project Scope Management 14
Example: Writing a scope statement?
University Technology Upgrades
Improved Scope Statement

• University X will upgrade the library, halls, offices, and then all campus buildings
to IEEE 802.11 technology, starting at the north side of campus with the library.
This project will facilitate productivity via computer of faculty, staff, and students.
The project will be complete by Fall semester, 2025.

You will notice that this scope statement includes specific directions for completion of
the project. The results are measurable - we can know how many buildings have been
upgraded. It is agreed upon, realistic (because we are taking a building-by-building
approach), and time bound - it will be completed by a specific date.

http://www.brighthubpm.com/project-planning/57950-example-and-evaluation-of-project-scope-statements/
Project Scope Management 15
Scope Creep
Scope Creep

• Adding additional features or functions of a new product, requirements, or


work that is not authorized (i.e., beyond the agreed-upon scope).
• Common causes of scope creep include:
• Unclear or poorly defined project scope at the outset.
• Frequent changes in requirements from stakeholders without proper change control
processes.
• Lack of communication among team members, stakeholders, or clients, leading to
misunderstanding or misalignment on project goals.
• Pressure to meet customer or stakeholder demands that weren’t initially considered.
• Adding new features or functionalities after the project has started without assessing
their impact.
Scope Creep
Project Scope Checklist
Project Scope
Statement
Work Break Down Structure (WBS)

Once the project scope document has been agreed on and prepared, the next step in
the planning phase is to create a detailed work breakdown structure (WBS)
Work Breakdown Structure (WBS)

Inputs: Project scope statement


Requirements documentation

The process of sub dividing the project deliverables and


project work into smaller and more manageable components .

The Work Breakdown Structure is the foundation for effective


project planning, costing and management.
Work Breakdown Structure (WBS)

The purpose of developing a WBS is to:


• Allow easier management of each component.
• Allow accurate estimation of time, cost, and resource requirements.
• Allow easier assignment of human resources.
• Allow easier assignment of responsibility for activities.
Work Breakdown
Structure (WBS)

• Graphic chart
or Tablular/Indented
list
WBS
Work Package (WP)

• A work package is a deliverable at the lowest level of the WBS.


• A work package is a definable unit of work within a project that can
be assigned to a specific team or individual for completion.
• Deliverable is output of work package
• Resource requirements and durations can be assigned
• Accountability can be assigned
• Project manager can monitor and control
WBS – Example
WBS – Example
WBS -Example
Responsibility Matrix

• A responsibility matrix defines who will be responsible for the work.


• Uses a P to designate primary responsibility and an S to indicate support
responsibility for a specific work item.
• P = Primary responsibility
• S = Support responsibility
Responsibility
Matrix
Summary

• The project scope defines what needs to be done.


• The project scope document usually contains the customer requirements,
statement of work, deliverables, acceptance criteria, and a work
breakdown structure.
• The work breakdown structure establishes the framework for how the
work will get done to produce the project deliverables.
• A responsibility assignment matrix defines who will be responsible for
the work.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy