CIT 309 – IT Project Management
Project Scope
Management
By: Alfio I. Regla
Proto Credit: [Link]
• Explain the importance of scope management;
• Create document necessary for scope management
Intended
Learning
particularly the WBS; and
Outcomes • Analyze tools and techniques in each process of
project scope management;
WHAT IS PROJECT SCOPE MANAGEMENT?
Scope VS. Deliverable
• Scope refers to all the work involved in creating the
products of the project and the processes used to create
Discussion
them
• Deliverable can be product related, such as a piece of
hardware or software, or process related, such as a
planning document or meeting minutes.
WHAT IS PROJECT SCOPE MANAGEMENT?
- includes the processes involved in defining and controlling
what work is or is not included in a project.
- It ensures that the project team and stakeholders have the
Discussion same understanding of what products the project will
produce and what processes the project team will use to
produce them.
SIX MAIN PROCESSES IN PROJECT SCOPE MANAGEMENT
1. Planning Scope Management - involves determining
how the project’s scope and requirements will be manage.
2. Collecting requirements - involves defining and
Discussion documenting the features and functions of the products as
well as the processes used for creating them.
3. Defining scope involves reviewing the scope management
plan, project charter, requirements documents, and
organizational process assets to create a scope statement,
adding more information as requirements are developed
and change requests are approved.
SIX MAIN PROCESSES IN PROJECT SCOPE MANAGEMENT
4. Creating the WBS involves subdividing the major project
deliverables into smaller, more manageable components.
5. Validating scope involves formalizing acceptance of the
Discussion project deliverables.
6. Controlling scope involves controlling changes to project
scope throughout the life of the project—a challenge on many
IT projects.
PROJECT SCOPE MANAGEMENT PROCESSES SUMMARY
Discussion
Figure 1: Scope Management Summary(Schwalbe, 2014)
1. Why is good project scope management so
important on IT projects?
Learning
Check
PLANNING SCOPE MANAGEMENT
Information required on scope management plan:
a. How to prepare a detailed project scope statement
Discussion b. How to create a WBS
c. How to maintain and approve the WBS:
d. How to obtain formal acceptance of the completed
project deliverables
e. How to control requests for changes to the project
scope
SCOPE
MANAGE
MENT
Discussion
PLAN
Figure 2: Scope Management Plan Example (Schwalbe, 2014)
PLANNING SCOPE MANAGEMENT
Information required on requirements management
plan:
a. How to plan, track, and report requirements activities
Discussion
b. How to perform configuration management activities
c. How to prioritize requirements
d. How to use product metrics
e. How to trace and capture attributes of requirements
COLLECTING REQUIREMENTS
Several Ways to collect requirements:
a. Interviewing stakeholders - one on one is often very
effective, although it can be expensive and time
Discussion consuming.
b. Holding focus groups and facilitated workshops, and
using group creativity and decision-making techniques to
collect requirements are normally faster and less
expensive than one-on-one interviews.
c. Questionnaires and surveys - can be efficient ways to
collect requirements as long as key stakeholders provide
honest and thorough information.
COLLECTING REQUIREMENTS
Several Ways to collect requirements:
d. Observation - can also be a good technique for collecting
requirements, especially for projects that involve improving
Discussion work processes and procedures.
e. For software development projects, prototyping and
document analysis are common techniques for collecting
requirements, as are context diagrams, which help to clarify
the interfaces and boundaries of a project or process.
COLLECTING REQUIREMENTS
Several Ways to collect requirements:
f. On agile software development projects, the product owner
creates the prioritized product backlog for each sprint.
Discussion
g. Benchmarking, or generating ideas by comparing specific
project practices or product characteristics to those of other
projects or products inside or outside the performing
organization.
What is involved in collecting requirements for a
project? Why is it often difficult to do?
Learning
Check
DEFINING SCOPE
- Good scope definition is very important to project
success.
- The main tools and techniques used in defining
Discussion
scope include expert judgment, data analysis,
decision making, interpersonal and team skills, and
product analysis.
- The main outputs: project scope statement and
project documents updates.
Discussion
Discussion
SCOPE
DEFINITIO
N AND THE
SCOPE
Discussion STATEMEN
T
Figure 3: Scope Statement Example (Schwalbe, 2014)
CREATING THE WBS
- A work breakdown structure (WBS) is a deliverable-oriented
grouping of the work involved in a project that defines its
total scope.
Discussion - Inputs: project management plan, project documents,
enterprise environmental factors, and organizational process
assets are the primary inputs for creating a WBS.
- Expert judgment, the main tool or technique is
decomposition—that is, subdividing project deliverables into
smaller pieces.
- Outputs: scope baseline and project documents updates.
WBS
Discussion Figure 4: WBS by Product Area (Schwalbe, 2019)
Figure 5: WBS by Project Area (Schwalbe, 2014)
WBS
Discussion
Figure 5: WBS in Tabular Form
APPROACHES IN DEVELOPING WBS
a. Using guidelines
b. Analogy approach - use a similar project’s WBS as a
Discussion
starting point.
c. Top-down approach - start with the largest items of the
project and break them into subordinate items.
d. Bottom-up approach - team members first identify as
many specific tasks related to the project as possible.
e. Mind Mapping
WBS
Discussion
Figure 6: WBS by Mind Mapping (Schwalbe, 2007)
Photo Credit: [Link]
WBS
Discussion
Figure 6: WBS by Mind Mapping (Schwalbe, 2007)
Photo Credit: [Link]
WBS
Discussion
Figure 6: WBS by Mind Mapping (Schwalbe, 2007)
Photo Credit: [Link]
THE WBS DICTIONARY
• A WBS dictionary is a document that provides detailed
information about each WBS item.
• The term dictionary should not be confused with defining
Discussion terms or acronyms in this case; such definitions belong in a
glossary that would be included elsewhere in the project
documentation.
What are the different ways to develop a WBS? Explain each.
Learning
Check
WBS
Discussion
Figure 6: WBS by Mind Mapping (Schwalbe, 2007)
Photo Credit: [Link]
VALIDATING SCOPE
• Scope verification/validation refers to the
acceptance of the stakeholders completed
Discussion project scope.
• Even when the project scope is fairly well defined, many IT
projects suffer from scope creep—the tendency for project
scope to keep getting bigger and bigger.
• This acceptance is often achieved by a customer inspection
and then sign-off on key deliverables.
• To receive formal acceptance of the project scope, the
project team must develop clear documentation of the
project’s products and procedures to evaluate whether
they were completed correctly and satisfactorily.
What is the main technique/s used for validating scope?
Learning A. Expert Judgement
Check B. Data Analysis
C. Inspection
D. Decision Making
CONTROLLING SCOPE
• Scope control refers to controlling project scope changes.
• The goal is to impact some factors that causes changes in scope.
• Next, assurance that the changes in scope are processed within the
procedures stated during the integration change control.
Discussion • And manage the occurrences of the scope changes.
• An important tool for performing scope control is data analysis,
including variance analysis. Variance is a about the comparison of actual
and planned performances.
• Project scope statement has the following processes such
as:
• Scope planning
• Scope definition:
• Creating the WBS
SUMMARY • Scope verification
• Scope control
1. Why is good project scope management so important on IT
projects?
Learning 2. What is involved in collecting requirements for a project?
Activities Why is it often difficult to do?
2. Summarize the processes involved in scope
management and the importance of it on IT
Learning projects?
Activities 3. What are the ways in developing a WBS? Explain
based on its level of difficulty.
4. What is the importance of good WBS? Relate in
using the software. Give other software that will
assist in scope management.
Answer this case study from (Schwalbe, 2019)
You are working on a project to develop a new or enhanced system to help
people at your college, university, or organization to find jobs. The system
Learning must be tailored to your student or work population and be very easy to
Activities use. Write a short paper describing how you would collect requirements
for this system, and include at least five requirements in a requirements
traceability matrix.
• Formative Assessment
• Assignment
Assessment • Discussion about leadership and management
Tasks
• Schwalbe K. (2019),Information Technology Project Management, Ninth Edition. © 2019
Cengage.
• Schwalbe K. (2014),Information Technology Project Management, Seventh Edition. © 2014
Cengage.
Reference