WHAT IS SCOPE OF WORK SCOPE MANAGEMENT Scope management

WHAT IS SCOPE OF WORK SCOPE MANAGEMENT Scope management WHAT IS SCOPE OF WORK SCOPE MANAGEMENT Scope management WHAT IS SCOPE OF WORK SCOPE MANAGEMENT Scope management WHAT IS SCOPE OF WORK SCOPE MANAGEMENT Scope management WHAT IS SCOPE OF WORK SCOPE MANAGEMENT Scope management

SCOPE MANAGEMENT

DEMARCATION OF WORK

WHAT IS SCOPE OF WORK

& SCOPE MANAGEMENT

• Scope defines the who, what, when, where and how

• Product scope: feature and function that characterize

a product, service or result

• Project scope: is the work that project team will do to deliver the product

• The Project Scope Management is the process to ensure that a project includes all the work

relevant/appropriate to achieve the project's

objectives

CUSTOMER EXPECT SALE ADVERTISE COMPLETE PRODUCT

WHY IT’S

IMPORTANT?

 Define project needs

 Understand project objective

 Define the project scope

WHY IT’S IMPORTANT?

• A scope creep is adding

features and

functionality to project

scope without

addressing the effects

on time, costs, and

resources, or without

customer approval”

WHY IT’S

IMPORTANT?

PT

• Predictive life cycle (or classic or

planning focus life cycle): scope fixed

• Adaptive or agile life cycle or change-driven, scope identify in high level

?

1 Plan

scope

managemen

t

2.Collect requirement

3 Define scope

4.Create WBS

5 Validate scope

6 Control scope

• How the project defined, validated

and controlled

• SCOPE MANAGEMENT PLAN -

Describe how the scope will be

defined, develop, monitor, control and validate

• REQUIREMENT MANAGEMENT PLAN:

to answer question like: Once I have all the requirements, what will I do to analyze, prioritize, manage and track changes to them?

• Understand what is needed to satisfy

stakeholders, then documenting that

understanding

• process of determining, documenting,

and managing stakeholder needs and

requirements to meet objectives

• REQUIREMENT DOCUMENTATION

describes what needs to be performed

and why each requirement is

important on the project 1 thing must

include in acceptance criteria

Business requirements Stakeholder requirements Transition and readiness requirements Project requirements

Quality requirements

• Developing details description of

project and product

• Project scope statement = HERE

WHAT WE WILL DO ON THIS

PROJECT

• On plan-driven project, can take a lot

of time and involve many expert

judgment, stakeholder and expert outside of organization

• On change-driven project, it will less detail, but it will have sufficient

detail to define what include/

exclude.

CREATE W ORK B REAKDOWN

S TRUCTURE

• Dividing project deliverables and project

work into smaller, easy to manage

component

• Decomposition - breaking down the project

deliverable into smaller components

• SCOPE BASELINE - approved version of

scope statement, WBS, and WBS dictionary

Only change through formal change control

procedure

4.Create

WBS

• Formal acceptance of the completed

project deliverables

• Accepted deliverables: formally

signed off and approved by the

customer or sponsor

• Work performance information: Tell

how deliverable was created, on

time, within budgets, how the

resources used compared with

estimate

• Change requests

Quality control

building the product correctly

inspect the deliverable for completeness and correctness

Validate scope

building the right product

Make sure that the products meet the customer’s requirements

DEMARCATION OF WORK

• creating a boundary around a

place or thing

• Form of Demarcation

• Drawing, mapping

• Matrix, chart

• BOQ