Where are we

• We have completed the initiation process

We are ready to start the Project Planning Process

• Purpose of this Lecture:

• Defining Project Goals & Objectives
• Discovering Requirement
• Agreeing on Deliverables
• Determining Assumptions & Constraints
• Compiling the Project Scope Statement
• Creation of WBS and Scope Baseline
What is Scope?
Project Scope Management?

• Project Scope Management includes the processes required to ensure

that the project includes all the work required to complete the project
successfully, with all the requirements and characteristics agreed upon.

• Project Scope Management is primarily concerned with defining and

controlling what is and is not included in the project.
 S1. Plan Scope Management

Plan Scope Management is the process of creating a scope

management plan that documents how the project and
product scope will be defined, validated, and controlled.
The key benefit of this process is that it provides guidance
and direction on how scope will be managed throughout
the project
S1. Plan Scope Management
S1. Plan Scope Management T&T
• EXPERT JUDGMENT
Expertise should be considered from individuals or groups with specialized knowledge
or training or experience from Previous similar projects
• DATA ANALYSIS
A data analysis technique that can be used for collecting requirements, elaborating the
project and product scope, creating the product, validating the scope, and controlling
the scope are evaluated
• MEETINGS
Project teams may attend project meetings to develop the scope management plan.
Attendees may include the project manager, the project sponsor, selected project team
members and selected stakeholders
 Output: Plan Scope Management
• SCOPE MANAGEMENT PLAN
• The scope management plan is a component of the project management
plan that describes how the scope will be defined, developed, monitored,
controlled, and validated
• REQUIREMENT MANAGEMENT PLAN
• The requirements management plan is a component of the project
management plan that describes how project and product requirements
will be analyzed, documented, and managed
S2. Collect Requirements
S2. Collect Requirements
Inputs
How requirements can be collected?
S2. Collect Requirements T&T
 S2. Collect Requirements T&T
 Expert Judgment
(Industry/Focus area of the project, Duration & Budget estimation, Benefit
Measurement, Risk identification)
 Data Gathering
 Brainstorming (Idea generation & analysis)
 Questionnaire & Survey
 Interviews
 Focus groups. (prequalified stakeholders and SMEs to learn about their
expectations and attitudes about a proposed product, service, or result. A
trained moderator guides the
group
 Benchmarking (comparing actual or planned products, processes, and practices
to those of comparable organizations to identify best practices)
 Data Analysis
 Document Analysis (reviewing and assessing any relevant documented
information)
 S2. Collect Requirements T&T
 DECISION MAKING (Through Voting)
Unanimity. Everyone agrees on a single course of action.
Majority. More than 50% of the members of the group.
Plurality. Largest block in a group decides, even if a majority is not achieved.
Autocratic. Might is right.
Multi criteria. Decision made on multiple criteria such as depending on risk levels
and uncertainty to evaluate and rank many ideas.

• DATA REPRESENTATION
Affinity diagrams. Ideas to be classified into groups
Mind mapping. Consolidates ideas created through individual brainstorming
sessions into a single map
 S2. Collect Requirements T&T
 INTERPERSONAL AND TEAM SKILLS
Nominal Group Technique
(brainstorming with a voting process used to rank the most useful ideas)
UNBIASED
Observation/Conversation.
Direct way of viewing individuals in their environment and how they
perform their jobs or tasks and carry out processes AKA JOB SHADOWING
Facilitation
Workshops can be used to quickly define cross-functional requirements and
reconcile stakeholder differences
• Joint application design/development (JAD). (Used in Software Industry)
SME and Teams work for improvement of SW development processes
• Quality function deployment (QFD). (Used in Manufacturing Industry)
Collecting voice of the customer (VOC)then sorted and prioritized
• User Stories (Textual descriptions of required functionality)
 S2. Collect Requirements T&T
 CONTEXT DIAGRAM
The context diagram is an example of a scope model. Context diagrams
visually depict the product scope by showing a business system (process,
equipment, computer system, etc.), and how people and other systems
(actors) interact with it

 PROTOTYPING
Prototyping is a method of
obtaining early feedback on
requirements by providing a
model of the expected product
before actually building it
Examples are computer
generated 2D and 3D models,
mock-ups, or simulations
S2. Collect Requirements
Outputs
Requirement Traceability Matrix
RTM to ensure that the project’s scope, requirements, and deliverables remain
“as is” when compared to the baseline

ID Associate Requirement Business Project WBS Product Product Test

ID Description Need Objective Deliverable Design Development Cases
Opportunitie
s Goals,
Objectives
 S.3. Define Scope
• It’s the process of developing a detailed description of Project and Product
S.3. Define Scope T&T
Output: Project Scope Statement

Real life: Project Scope Statement

 Project Charter Vs Project Scope Statement
Project Charter Project Scope Statement
•Purpose or Justification •Project Scope Description
•Measureable Project Objectives and (progressively elaborated)
Success Criteria •Acceptance Criteria
•High-level requirements •Project Deliverables
•High-level project description •Project Exclusions
•High-level Risk •Project Constraints
•Summary Milestone Schedule •Project Assumptions
•Summary Budget
•Stakeholder List
•Project Approval requirements
(success factor, who decides an who
signs)
•Assigned Project Manager
•Name and authority of the sponsor
 Example: Assumptions & Constraints
• Assumptions:
• There may be external circumstances or events that must occur for project
to be successful
• E.g. Suppose you plan to go shopping at a big mall, which is far away from
your home. It will take one hour to reach there by car. You made the
assumption that you will leave your home around 6:00 PM and reach there
by 7:00 PM. After that, you can enjoy shopping.
• Constraints:
• Any limitation or restriction that stopping you to going beyond.
• E.g. At first glance, you can think of two constraints. The first constraint
is the amount of money to be spent on shopping. If you have $500 in
your hand, you cannot spend more than this amount. This is your first
constraint. The second constraint can be the mall’s closing time. If the
mall closes at 10:30 PM, you cannot continue your shopping after this
time. You have to wrap up everything before this time.
S.4. Create WBS
 S.4. Create WBS
• Till now we have created Project scope statement therefore we can now
break the project into work packages, also known as Deliverables.
• The technique we use in breaking project into work packages is called
Decomposition.
WBS : It is a deliverable-oriented hierarchical decomposition of the
work to be executed by the project team
WBS Dictionary (Code, description of work, responsible organization,
list of schedule milestones, associated schedule activities, resources
required, cost estimates, quality requirements, acceptance criteria)
Scope Baseline: A component of project management plan (PSS,
WBS, WBS Dictionary)
Project Document Update:
Scope Statement is then passed on to the Project Time Management
and Project Quality Management to plan for Time and Quality.
 Real life Example of WBS
Real life Example of WBS Dictionary
Thank You
Any Questions?

• Next Lecture:
• Project Schedule Management