4 lecture 4 - amazon web services · pdf filenotes . 17/12/1437 10 19 of 33 ... pmp pmp d vd...

17/12/1437

1

2 of 33

Project Scope Management 4 Lecture

Project Management Knowledge Areas

Section – 3 Chapter – 5

Lecture 4

Project Scope Management

17/12/1437

2

3 of 33



Planning

Planning

Planning

Planning

Monitoring & Controlling

Monitoring & Controlling

Plan Scope Management

Collect Requirement

Define Scope

Create WBS

Validate Scope

Control Scope

Quick Re-cab

4 of 33



categorized as ..

Features and functions of

the product of the project

Completion of product scope is measured against the

requirements

The work needed to

create product of the project

Completion of a project is measured against the

plan

17/12/1437

3

5 of 33



The process of defining and documenting customer needs

The customer requirements have to be elicited, analyzed and recorded

Notes

6 of 33



The requirements are categorized into:

Notes

Project Requirements

Product Requirements

Business Requirements

Technical Requirements

Project Management Requirements

Security Requirements

Delivery Requirements

Performance Requirements

17/12/1437

4

7 of 33



Definition

The process of creating a scope management plan that documents how the project scope will be defined, validated, and controlled

8 of 33



ITTO

1. Scope management plan

2. Requirements management plan

Outputs

1. Expert Judgement

2.Meetings

Tools & Techniques

1. Project management plan

2. Project Charter

3. Organizational Process Assets

4. Enterprise Environmental Factors

Inputs

17/12/1437

5

9 of 33



ITTO

1. Contract

2. Project Statement of Work

3. Business Case

4. Organizational Process Assets

5. Enterprise Environmental Factors

Inputs



Outputs

1. Expert Judgement

2. Facilitation Techniques

Tools & Techniques

1. How requirements activities will be planned, tracked and reported

2. How configuration activities will be planned, tracked and reported

3. Description of requirements prioritization

4. How product metrics are defined

5. How traceability structure is defined

Co

nte

nts

10 of 33


Collect Requirements

Definition

The process of determining, documenting, and managing stakeholder needs and requirements to meet project objectives.

17/12/1437

6

11 of 33



ITTO

1. Requirements Documentation

2. Requirements Traceability Matrix

Outputs Tools & Techniques

1. Interviews 2. Focus groups 3. Facilitated workshops 4. Group creativity

techniques 5. Group decision-

making techniques 6. Questionnaires and

surveys 7. Observations 8. Prototypes 9. Benchmarking 10.Context diagrams 11. Document analysis



3. Stakeholder management plan

4. Project charter

5. Stakeholder register

Inputs

12 of 33





4. Project charter


Inputs


ITTO


2.Requirements Traceability Matrix


1. Interviews 2. Focus groups 3. Facilitated workshops

4.Group creativity techniques

5. Group decision-making techniques

6. Questionnaires and surveys

7. Observations 8. Prototypes 9. Benchmarking 10. Context diagrams 11. Document analysis

1. Brainstorming

2. Nominal Group Techniques

3. Mind Mapping

1. Unanimity

2. Majority

3. Plurality

4. Dictatorship

17/12/1437

7

13 of 33



ITTO

Tools & Techniques

1. Interviews 2. Focus groups 3. Facilitated workshops 4. Group creativity

techniques 5. Group decision-

making techniques 6. Questionnaires and

surveys 7. Observations 8. Prototypes 9. Benchmarking 10.Context diagrams 11. Document analysis




4. Project charter


Inputs


2. Requirements Traceability Matrix

Outputs

1. Business needs

2. Functional Requirements

3. Non-Functional Requirements

4. Quality Requirements

5. Acceptance Criteria

6. Support and Training Requirements

7. Requirements Assumptions and Constraints

Co

nte

nts

14 of 33


Define Scope

Definition

The process of developing a detailed description of the project and product.

17/12/1437

8

15 of 33


Define Scope

ITTO

1. Project Scope Statement

2. Project Document Updates


1. Expert judgment

2. Product analysis

3. Alternatives generation

4. Facilitated workshops


2. Project charter

3. Requirements documentation

4. Organizational process assets

Inputs

16 of 33


Define Scope

ITTO

Tools & Techniques

1. Expert judgment

2. Product analysis

3. Alternatives generation

4. Facilitated workshops


2. Project charter



Inputs

1. Project Scope Statement

2. Project Document Updates

Outputs

1. Project Scope Description

2. Product Acceptance Criteria

3. Project Deliverables

4. Project exclusions

5. Project Constraints & Assumptions Co

nte

nts

Project Scope Statement defines what work will be performed and what work is excluded.

17/12/1437

9

17 of 33


Create WBS

Definition

The process of subdividing project deliverables and project work into smaller, more manageable components.

18 of 33


Create WBS

WBS decomposes the project work into smaller, more manageable pieces of work.

WBS is a deliverable-oriented hierarchical decomposition of Project Work

Decomposition of project deliverables 1. The major deliverables of the project are identified,

including project management activities

2. Determine if adequate cost and time estimates can be applied to the lowest project work.

Notes

17/12/1437

10

19 of 33


Create WBS

WBS is very important as it is an input to FIVE core processes

Notes

WBS

Cost Estimating

Risk Mgmt. Planning

Activity Definition

Resource Planning

Cost Budgeting

20 of 33


Create WBS

ITTO

1. Scope Baseline

2. Project documents updates


1. Decomposition

2. Expert judgment


2. Project scope statement


4. Enterprise environmental factors


Inputs

17/12/1437

11

21 of 33


Create WBS

Project

PM 1.1

1.1.1 1.1.2

1.1.2.1 1.1.2.2

1.1.2.2.1 1.1.2.2.2

HW 1.2

1.2.1

1.2.2

SW 1.3 SYS Eng 1.4 Testing 1.5 Database 1.6

Leve

l 1

Leve

l 2

Leve

l 3

Leve

l4

Leve

l5

22 of 33


Create WBS

Project

1.1 Phase 1

1.1.1 Deliverable

1.1.1.1 Deliverable

1.1.1.1.1 Work Package WBS Identifier

17/12/1437

12

23 of 33


Create WBS

ITTO

Tools & Techniques

1. Decomposition

2. Expert judgment


2. Project scope statement


4. Enterprise environmental factors


Inputs

1. Scope Baseline


Outputs

WBS Dictionary

1. Code of accounts identifier

2. Description of work

3. Person / organization responsible to completing the component

4. List of schedule milestones

5. Associated schedule activities

6. Resources required & Cost estimates

7. Quality requirements & Acceptance criteria

8. Technical references

Co

nte

nts

24 of 33


Validate Scope

Definition

The process of formalizing acceptance of the completed project deliverables

17/12/1437

13

25 of 33


Validate Scope

Notes

Validate Scope is the process of the project customer accepting the project deliverables.

happens at the end of each project phase or a major deliverables are created

is ensuring that the deliverables the project creates are in alignment with the project scope

Validate of Scope differs from quality control

Quality control is preformed before validate scope

26 of 33


Validate Scope

ITTO

1. Accepted deliverables

2. Change requests

3. Work performance information



1. Inspection

2. Group decision-making techniques



3. Traceability matrix

4. Verified deliverables

5. Work performance data

Inputs

17/12/1437

14

27 of 33


Deliverables

CLOSE VS CQ

PMP

PMP D VD AD

D VD AD FPSR

PMP DMPW

Project Charter

28 of 33


Control Scope

Definition

The process of monitoring the status of the project and product scope and managing changes to the scope baseline.

17/12/1437

15

29 of 33


Control Scope

Notes

Project Scope Control concerned with influencing the factors that create project scope changes and controlling the impact of those changes

Scope control assures all requested changes and recommended corrective actions are processed through Integrated Change Control Process

Uncontrolled changes are referred to as Scope Creep

30 of 33


Control Scope

ITTO

1. Work performance information

2. Change requests

3. Project management plan updates


5. Organizational process assets updates


1. Variance analysis



3. Requirements traceability matrix

4. Work performance data


Inputs

17/12/1437

16

31 of 33


We identified Project Scope Management knowledge area processes

We know how to plan scope management

We know how to collect requirements

We know how to create Project Scope Statement

To Sum up..


32 of 33


We know how to create WBS and WBS Dictionary

We know how to validate Scope

We know how to control Scope throughout the Project

To Sum up..


4 lecture 4 - amazon web services · pdf filenotes . 17/12/1437 10 19 of 33 ... pmp pmp d vd...

Documents