Session 4 4th edition PMP

36
Project Scope Management

Transcript of Session 4 4th edition PMP

Page 1: Session   4 4th edition PMP

Project Scope Management

Page 2: Session   4 4th edition PMP
Page 3: Session   4 4th edition PMP

• After we collect requirements of project

• We need to define scope

Page 4: Session   4 4th edition PMP

Tools & Techniques

Product analysisFor projects that have a product as a deliverable, as opposed to a service or result, product

analysis can be an effective tool. Each application area has one or more generally accepted methods

for translating high-level product descriptions into tangible deliverables.

Product Analysis Template

Product name:

Company name:

Materials used :

Utility :

Client’s needs :

Safety / Hazards :)

Cost :

Aesthetics :

Green quotient:

Page 5: Session   4 4th edition PMP

Alternatives Identification

-The purpose of this technique is to generate ideas on different ways to accomplish the project- The desired work is already known, but there may be preferred ways to accomplish the work

Page 6: Session   4 4th edition PMP

Define Scope• Process of developing a detailed description of the project and product

– Project scope statement may includes product scope, deliverables, product acceptance criteria, out of scope, additional risk, constraints & assumptions

Inputs

1. Project charter2. Requirements

documentation3. Organizational

process assets

Tools & Techniques

1. Expert judgment2. Product analysis3. Alternatives

Identification4. Facilitated workshops

Outputs

1. Project scope statement

2. Project document updates

Page 7: Session   4 4th edition PMP

Project Scope Statement• Contents

– Product scope– Deliverables– Product acceptance criteria– What is not part of the project (out of scope)– Additional risks– Constraints and assumptions :

Constraints: factors that limit the team’s optionsAssumptions: Things that assumed to be true (may not be true)

Page 8: Session   4 4th edition PMP

PROJECT SCOPE STATEMENTProject Title: Date Prepared:

Product Scope Description:

Product Scope is progressively elaborated from the project description and the project requirements in the Project Charter.

Project Deliverables:

Project deliverables are progressively elaborated from the project description, the product characteristics, and the product requirements in the Project Charter.

Project Acceptance Criteria:

The acceptance criteria that will need to be met in order for a stakeholder to accept a deliverable. Acceptance criteria can be developed for the entire project or for each component of the project.

Project Exclusions:

Project exclusions clearly define what is considered out of scope for the project.

Project Constraints:

Constraints that may be imposed on the project ma include a fixed budget, hard deliverable dates, or specific technology.

Project Assumptions:Assumptions about deliverables, resources, estimates, and any other aspect of the project that the team holds to be true, real, or correct but has not validated.

Page 9: Session   4 4th edition PMP

Product Scope Description: االطباء وغرف الطبية الخدمات جميع يشمل طابق وكل طوابق اربع من المستشفى مبنى يتكون

على ويحتوى للطوارئ االرضي الطابق متخصصة وعيادات والممرضات والممرضين والطبيباتوعدد ) مفردة )3غرفة و( استقبال وغرفة المعالجة وغرف لالطباء( 3عيادات استراحة غرفة

على ويحتوي القصيرة واالقامة االطفال للمرضى االول والطابق للمرضى 12والتمريض سريرو و 9االطفال القصيرة لالقامة وعدد )3أسرة لالطفال ترفيه الوجبات( 3غرف وتوزيع عيادات

على ويحتوى الرجال من البالغين للمرضى الثاني تسع )35والطابق غرفة كل وعدد( 4سرير مرضىالنساء( 3) من البالغين للمرضى الثالث للتحضيروالطابق وغرفة للمعالجة وغرفة مفردة غرفة

على تسع )35ويحتوى غرفة كل وعدد( )4سرير وغرفة( 3مرضى للمعالجة وغرفة مفردة غرفة:Project Deliverablesللتحضير

الطابق وبناء االول الطابق وبناء االرضي الطابق وبناء االساسات واعمال مساحة اعمالالتكييفات وتركيب التشطيبات واعمال الكهرباء واعمال الثالث الطابق وبناء الثاني

والكتالوجات كاملة بالمستشفى الخاصة الرسومات وتسليم الطبية االجهزة وتركيببالمبنى الخاصة

Project Acceptance Criteria:والشركة المالك بين العقد في جاء لما طبقا المشروع مجاالت جميع في القبول يتم

الجودة في المصرية القياسية للمواصفات وطبقا

PROJECT SCOPE STATEMENT

المشروع نطاق بيان2012/10/12التاريخ : وتجهيز : بناء المشروع اسم

خاص مستشفى

Page 10: Session   4 4th edition PMP

Project Constraints:

عن تزيد ال مدة في وتجهيزها المستشفى بناء شهور 8ضرورة

Project Assumptions:

الالزمة الحكومية التصاريح استخراج وامكانية العاملة االيدي توافر , يفترض

Project Exclusions:شبكة اقامة وال بالمستشفى الخاصة الالزمة الديكورات عمل على المشروع يشتمل ال

بالمستشفى خاصة معلومات

PROJECT SCOPE STATEMENT

المشروع نطاق بيانوتجهيز : بناء المشروع اسم

خاص 2012/10/12التاريخ :مستشفى

Page 11: Session   4 4th edition PMP

• The scope defined is difficult to manage

• So we decompose main deliverables create WBS

Page 12: Session   4 4th edition PMP

Create WBSProcess of subdividing project deliverables and project work into smaller,

more manageable components.

Inputs

1. Project scope statement2. Requirements

documentation3. Organizational process

assets

Tools & Techniques

1. Decomposition

Outputs

1. WBS2. WBS dictionary3. Scope baseline4. Project document

update

Page 13: Session   4 4th edition PMP

Create WBS

Work package: lowest level WBS component which can be scheduled, cost estimated, monitored and controlled.

100% rule: WBS includes 100% of the work defined by project scope and capture ALL deliverables (external, internal, interim) in term of work to be completed including project management.

WBS dictionary provides more detailed components, e.g. description of work, responsible organization, acceptance criteria

Agreed Scope baseline includes project scope statement, WBS, WBS dictionary

Page 14: Session   4 4th edition PMP

Work Breakdown Structure

المشروع1.0

المشروع1.0

تجهيز المستشفى

1.1

تجهيز المستشفى

1.1

كهرباء اعمال 1.2كهرباء اعمال

1.2

انشاء اعمال 1.3

انشاء اعمال 1.3

اجهزة تركيب 1.1.1

اجهزة تركيب 1.1.1

التسليح اعمال 1.3.2.1

التسليح اعمال 1.3.2.1

نجارة اعمال1.3.2.2

نجارة اعمال1.3.2.2

التكييف اعمال 1.2.1

التكييف اعمال 1.2.1

التوصيالت الكهربية

1.2.2

التوصيالت الكهربية

1.2.2

بناء اعمال 1.3.1

بناء اعمال 1.3.1

التركيب 1.1.1.3

التركيب 1.1.1.3

االختبار 1.1.1.2

االختبار 1.1.1.2

اجهزة شراء 1.1.2

اجهزة شراء 1.1.2

اعمال اساسات

1.3.2

اعمال اساسات

1.3.2

وتجهيز : بناء المشروع اسمخاص مستشفى

2012/10/12التاريخ :

Page 15: Session   4 4th edition PMP

Work Breakdown Structure

Project1.0

Project1.0

Major deliverable

1.1

Major deliverable

1.1

Major deliverable

1.2

Major deliverable

1.2

Major deliverable

1.3

Major deliverable

1.3

Deliverable 1.1.1

Deliverable 1.1.1

Work Package 1.3.2.1

Work Package 1.3.2.1

Work Package 1.3.2.2

Work Package 1.3.2.2

Work Package

1.2.1

Work Package

1.2.1

Work package

1.2.2

Work package

1.2.2

Work Package

1.3.1

Work Package

1.3.1

Work Package 1.1.1.3

Work Package 1.1.1.3

Work Package 1.1.1.2

Work Package 1.1.1.2

Work Package 1.1.1.1

Work Package 1.1.1.1

Work Package

1.1.2

Work Package

1.1.2

Deliverable 1.3.2

Deliverable 1.3.2

Project Title: ____________________ Date Prepared: ______________

Page 16: Session   4 4th edition PMP

This is the time to ensure the deliverable is acceptedVerify Scope

Page 17: Session   4 4th edition PMP

Verify Scope• Process of formalizing acceptance of the completed project deliverables.

Inputs

1. Project scope statement

2. Requirements documentation

3. Requirement traceability matrix

4. Validated deliverables

Tools & Techniques

1. Inspection

Outputs

1. Accepted deliverables2. Change requests3. Project document

updates

Page 18: Session   4 4th edition PMP

Inspection• Inspection includes activities

such as measuring, examining,

and verifying to determine

whether work and deliverables

meet requirements and product

acceptance criteria. Inspections

are sometimes called reviews,

product reviews, audits, and

walkthroughs

Page 19: Session   4 4th edition PMP

• Question :• Why we need to

Control scope?

• Answer :• To avoid Scope creep

Page 20: Session   4 4th edition PMP

Control Scope• Process of monitoring the status of the project and product scope and

managing changes to the scope baseline• Prevent from scope creep

Inputs

1. Project management plan

2. Work performance information

3. Requirements document

4. Requirement traceability matrix

5. Organizational process assets

Tools & Techniques

1. Variance analysis

Outputs

1. Work performance measurements

2. Organizational process assets updates

3. Change requests4. Project management

plan updates5. Project document

updates

Page 21: Session   4 4th edition PMP

Work performance information:

• Information about project progress, such as which deliverables have started, their progress and which deliverables have finished.

Page 22: Session   4 4th edition PMP

Variance analysis

• Project performance measurements are used to assess the magnitude of variation from the original scope baseline. Important aspects of project scope control include determining the cause and degree of variance relative to the scope baseline and deciding whether corrective or preventive action is required

Page 23: Session   4 4th edition PMP

Control Scope: Outputs

.1 Work Performance MeasurementsMeasurements can include planned vs. actual technical performance or other scope performance measurements. This information is documented and communicated to stakeholders.

.2 Organizational Process Assets UpdatesOrganizational process assets that may be updated include, but are not limited to:• Causes of variances,• Corrective action chosen and the reasons, and• Other types of lessons learned from project scope control.

Page 24: Session   4 4th edition PMP

3 Change Requests

-Analysis of scope performance can result in a change request to the scope baseline or other components of the project management plan.

- Change requests can include preventive or corrective actions or defect repairs.

Control Scope: Outputs

Page 25: Session   4 4th edition PMP

Control Scope: Outputs• .4 Project Management Plan Updates• • Scope Baseline Updates. • If the approved change requests have an effect upon the project

scope, then the scope statement, the WBS, and the WBS dictionary are revised and reissued to reflect the approved changes.

• .5 Project Document Updates• Project documents that may be updated include, but are not limited

to:• • Requirements documentation, and• • Requirements traceability matrix.

Page 26: Session   4 4th edition PMP

QUESTIONS?

Page 27: Session   4 4th edition PMP

1-You are a project manager of a large project and you are identifying some alternative techniques to generate different approaches to execute and perform the work of a project. You are doing it as a part of:

A-Collect Requirements

B-Control Scope

C-Verify Scope

D-Define Scope

Page 28: Session   4 4th edition PMP

2- one stakeholder has asked you to add to the scope of the project . The project is under budget and a little a head of schedule what should you do?

A- approve the change.

B- Determine the effects of the change on the project.

C- ask the sponsor for approval to make the change.

D- refuse the request.

Page 29: Session   4 4th edition PMP

3-Verify Scope can be BEST described as the process of

A-Verifying that the project quality requirements have been met

B-Obtaining stakeholder's formal acceptance of the project deliverables

C-Controlling changes to the scope of the project D-Verifying that all of the project's objectives have

been met

Page 30: Session   4 4th edition PMP

4-During the planning phase of your project, your project team members has discovered another way to complete a portion of the project scope. This method is safer for the project team, but may cost more for the customer. This is an example of _____ ?

1. Alternative identification.

2. Risk assessment.

3. Alternative selection.

4. Product analysis.

Page 31: Session   4 4th edition PMP

5- A Work Breakdown Structure (WBS) numbering system should allow project staff to:

A. identify the level at which individual WBS elements are found.

B. identify configuration management milestones.

C. estimate the costs of WBS elements.

D. provide project justification.

Page 32: Session   4 4th edition PMP

6- An example of scope verification is:

A. reviewing the performance of an installed software module.

B. managing changes to the project schedule.

C. decomposing the WBS to a work package level.

D. performing a benefit/cost analysis to determine if we should proceed with the project

Page 33: Session   4 4th edition PMP

7-Validated deliverables is an input to which of the following processes?

1-Collect Requirements

2-Define Scope

3-Create WBS

4-Verify Scope

Page 34: Session   4 4th edition PMP

8- the work break down Structure is created by

A- the team

B- the project manager

C- management

D- the sponsor

Page 35: Session   4 4th edition PMP

9-over the last few weeks .the team has made three changes to the activities on the project the project manager must be most careful to.

A-record all the changes

B- provide documentation on all the changes to the sponsor

C- make sure the changes are reflected in the project scope baselines

D- prevent more changes from occurring

Page 36: Session   4 4th edition PMP

Thank you