1

Lec-5

Project
Planning & Management
Presented by
Rehan Asad
BS, MS, PhD Scholar, PMP®
 2

Agenda

• Scope management
▫ Project requirements
▫ Project scope statement
▫ work breakdown structure (WBS)
 3

Project Scope Management: Planning

1. Assembling the team

2. Kickoff meeting or project startup meetings

The purpose of this meeting is to

 Bring the team together
 Review the project charter
 Ensure everyone understands why the project has been initiated and
 What it is intended to deliver.
 4

Defining the Scope of Work:

• The reason we start with the scope of work???

"Begin with the end in mind...It is your plan for success. It ... puts your
goals in focus, and moves your ideas into the real world.“
(Stephen Covey)
 5

Defining the Scope of Work:

• The project's scope defines the project in terms of:

▫ What will be produced (the deliverables)

▫ All the work required in order to produce the project deliverables
▫ Work necessary to manage the project as well as deliver the results of the
project.
 6

Developing project scope:

We will create three key deliverables that will be included in our project
plan:

▪ Requirements documentation
▪ Scope Statement
▪ Work Breakdown Structure (WBS)
 7

Collecting Requirements
• From??
• Requirements define what is needed in order to meet the project
objectives.
• They do not define how the work will be done.

• Requirements are not contradicting the project objectives. For example???

• Avoid unrealistic requirements or requirements that are not feasible.
• Requirements should be measurable and testable
 8

Collecting Requirements:
Requirement Categories:
• Product technical or functional requirements
• Project process/management requirements
• Quality or performance requirements (for the project and product)
• Business or organizational requirements (for the project and product)
• Support or operational requirements (for the product)
• Profitability or sales/marketing requirements (for the product)
 9

Documenting Requirements:
• Map requirements to deliverables and project objective

Requirements Traceability Matrix:

• document each requirement as well as which objective and deliverable
it is associated with
• Simple table that allows the requirement to be traced from the Planning
Phase all the way through Execution and Closure.
10
 11

Prioritizing Requirements
A technique to prioritize requirements is called the MoSCoW method

▪ Must Have requirements are critical and must be included in the project in order to
meet objectives.
▪ Should Have requirements are important and should be included in the project if
time and budget allow, or otherwise be delivered at a later date, perhaps in the next
release of the product, as an example.
▪ Could Have requirements are nice to have if they can be included, but the project
can still be delivered and can still meet project objectives without these
requirements included.
▪ Won't Have requirements are agreed to by the Stakeholders, from the outset, that
they will not be included in the project or product delivery at this time but can be
revisited in the future.
 12

1. Project Scope Statement

• A key document to define the scope of the project is the Project Scope
Statement.
 13

Creating the Work Breakdown Structure

The process of sub dividing the project deliverables and project work into
smaller and more manageable components .

The WBS creation involves:

• Listing all the project outputs (deliverables and other direct results)
• Identifying all the activities required to deliver the outputs
• Subdividing these activities into subactivities and tasks
• Identifying the deliverable and milestone(s) of each task
• Identifying the time usage of all the resources (personnel and material)
required to complete each task
 14

Creating the Work Breakdown Structure

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

Note: do not worry about the sequence in which the work is performed
or any dependencies between the tasks when we do a WBS
15
 16

Thank
you