Scribd
Upload
47 views2 pages

Project Scope Management Notes

The document discusses project scope management and its key processes: planning scope management, collecting requirements, defining scope, creating a work breakdown structure, validating scope, and controlling scope. An example case study of developing a banking app is used to illustrate each process.

Uploaded by

Suswaram Sridhar
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
47 views2 pages

Project Scope Management Notes

The document discusses project scope management and its key processes: planning scope management, collecting requirements, defining scope, creating a work breakdown structure, validating scope, and controlling scope. An example case study of developing a banking app is used to illustrate each process.

Uploaded by

Suswaram Sridhar
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/ 2

Day #1 NOTES

Project Scope Management:


Simplified Explanation with Case Study Examples

Project Scope Management involves ensuring that a project includes all the necessary tasks
to complete the project successfully, and only those tasks. It's about defining and controlling
what is included and what isn't. Here's a breakdown of the key processes and some practical
examples:

1. Plan Scope Management

This is the initial phase where the scope management plan is developed. This plan outlines how
the scope will be defined, managed, and verified.

Case Study Example: Consider a software development project for a new banking app. The
project manager creates a scope management plan that specifies how the team will determine
which features (e.g., mobile deposits, balance checks, money transfers) will be included in the
app.

2. Collect Requirements

During this phase, project managers gather requirements from stakeholders to understand
what needs to be achieved. These requirements form the basis of the project deliverables.

Case Study Example: For the banking app, the project team may conduct surveys and focus
groups with potential users to gather their expectations and needs, such as high security for
transactions and an easy-to-use interface.

3. Define Scope

Here, the detailed description of the project and product, based on the collected requirements,
is developed. This is where the project's boundaries are clearly articulated.

Case Study Example: The project team decides the banking app will include features like
fingerprint authentication and real-time notifications for transactions, but will not include loan
or mortgage management features to keep the initial launch simple.

4. Create Work Breakdown Structure (WBS)

In this stage, the project scope is broken down into smaller, manageable parts, making it easier
to manage and execute.

Case Study Example: The development of the banking app is divided into several components:
user interface design, backend development, security features, and user testing.

1|Pa ge
Day #1 NOTES

5. Validate Scope

This process involves the formal acceptance of the project deliverables by the stakeholders,
ensuring that the deliverables meet the agreed-upon requirements.

Case Study Example: After a beta version of the banking app is developed, it's presented to a
focus group to ensure it meets their expectations and to gather feedback for improvements
before the final release.

6. Control Scope

The final phase is about monitoring the project scope and managing changes to the scope
baseline. This is crucial to prevent scope creep, which can lead to project overruns.

Case Study Example: During the development of the banking app, any request to add new
features (like integrating with other financial platforms) is evaluated against the project scope,
timeline, and budget before being approved or rejected.

Project Scope Management is a continuous process that requires regular revisits and
adjustments as the project progresses. Each step is interlinked and crucial for ensuring that a
project meets its objectives without overstepping its boundaries.

* End of document

2|Pa ge

You might also like