FUNDAMENTALS OF PROJECT

MANAGEMENT
LECTURE 4: PROJECT SCOPE
MANAGEMENT

COURSE INSTRUCTOR:
OWAIS TAHIR
PROJECT SCOPE MANAGEMENT
• Processes required to ensure that project
includes all the work required, and only the work
required, to complete project successfully
• There are two types of scope
1. Project scope
2. Product scope
Processes of Scope Management
• Plan Scope Management
• Collect Requirements
• Define Scope
• Create WBS
• Validate Scope
• Control Scope
Plan Scope Management
• When we are planning for scope, we are basically
producing the scope management plan
• Scope management plan is a document that
defines how a scope is defined, validated and
controlled. It entails how the scope will be created,
how it will be validated and controlled, who will
be responsible for it, what are the documentation
requirements and what processes will be followed
• Scope management plan will be the output of this
process
Inputs
• Project Charter
• Project Management Plan
• EEF
• OPA
Tools and Techniques
• Expert Judgment
• Meetings
Outputs
• Scope Management Plan, which will include
1. Process for preparing a detailed project scope
statement
2. Process that enables the creation of a WBS
3. Process that establishes how WBS will be
maintained and approved
4. Process to specify how acceptance of
completed project deliverables will be obtained
5. Process of how changes in the scope will be
made
• Requirements Management Plan, including
1. How requirements will be planned, tracked
and reported
2. Configuration management activities
3. Requirements prioritization process
4. Traceability structure
• Requirements management plan is a part of the
project management plan, but not part of the
scope management plan
Collect Requirements
• Process of documenting and managing
stakeholder needs and expectations from the
project, and creating a list of deliverables. It
provides the basis for defining the scope of the
project as well as the product.
• A project can only be successful if the
requirements of the stakeholders are identified
and then correctly converted into project scope
and deliverables.
• Requirements can include the product, service o r
result to be created, the deliverables to be provided,
the quality requirements, the documentation and
other ancillary detail required with the deliverables.
• These form the basis of the project, the scope
statement and the project management plan. It is
on these requirements that the project is monitored,
controlled, validated and finally handed over for
approval. WBS is created from these requirements.
• The project charter, stakeholder register and
stakeholder management plan provide the basis for
the requirements management plan.
Types of Requirements
• Business requirements (higher level)
• Stakeholder requirements (internal & external)
• Solution requirements (features, functions,
characteristics). These include functional and
non-functional requirements
• Transition requirements e.g trainings
• Quality requirements
• There can be many other
Inputs
• Scope Management Plan. Will give the project team
an idea about which type of requirements to collect
• Requirement Management Plan. Will describe how
requirements are to be collected, recorded and
used.
• Stakeholder Management Plan. Will describe the
stakeholder requirements related to
communication, level of stakeholder engagement
• Project Charter
• Stakeholder Register
Tools and Techniques
• Interviews
• Focus Groups
• Facilitated Workshops (e.g Caterpillar customer
conferences) (e.g development sessions in IT
industry)
• Group creativity techniques
1. Brainstorming
2. Nominal group technique
3. Mind mapping
4. Affinity diagram
• Group decision making techniques
1. Unanimity
2. Majority
3. Plurality
4. Dictatorship
• Questionnaires and Surveys
• Observations (environment based)
• Prototypes
• Benchmarking
• Context Diagram (process flow diagrams)
• Document Analysis (existing documents)
Outputs
• Requirements Documentation
1. Documents the requirements of the project
2. May be high level, may be detailed with supporting
documentation and evidence for each requirement
3. Requirements need to be complete, consistent,
measurable and traceable as well as acceptable to
the stakeholders.
4. Can include one or more of the following:
▫ business requirements, stakeholder requirements,
project requirement, assumptions, solution
requirements.
Requirements Traceability Matrix
• Matrix that connects a requirement from
inception to the ultimate deliverable that will
satisfy it
• This helps ensure that each requirement adds
value to the business, and also to trace each
requirement back to its origination. It also helps
ensuring that each requirement has been
fulfilled, and can also be helpful in validating
scope
• It provides a structure for changes to scope
• Attributes to be included in the matrix are up to
the organization to decide. However, the
following are usually included
1. Id
2. Textual description
3. Rationale
4. Source
5. Priority
6. Status
7. Status date
8. WBS activity
9. Associated deliverable