Introduction to Project Management

Download Report

Transcript Introduction to Project Management

o o P.I.I.M.T

American University of Leadership

Ahmed Hanane, MBA, Eng, CMA, Partner email: [email protected]

Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall

Scope Management

05-02

     After completing this chapter, students will be able to: Understand the importance of scope management for project success.

Understand the significance of developing a scope statement.

Construct a Work Breakdown Structure for a project.

Develop a Responsibility Assignment Matrix for a project.

Describe the roles of changes and configuration management in assessing project scope.

05-03

05-05 FIGURE 5.1 The Expeditionary Fighting Vehicle Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall

Project scope

is

everything about a project

work content as well as expected outcomes.

Scope management

is the function of

controlling a project

in terms of its goals and objectives and consists of:

1) Conceptual development 2) Scope statement 3) Work authorization 4) Scope reporting 5) Control systems 6) Project closeout 05-06

The

process

that addresses

project objectives

meet them.

by finding the best ways to

05-07 Key steps in information development: o Problem/need statement o Information gathering o Constraints o Alternative analysis o Project objectives

Successful conceptual development requires: o Reduction of overall project complexity o Goals and objects are clearly stated o Reference points are provided 05-08 o Complete understanding of the problem

A SOW is a

detailed narrative description

of the work required for a project.

05-09 Effective SOWs contain 1.

Introduction and background 2.

3.

4.

Technical description Timeline and milestones Client expectations

o o o o o o o o o Background Objectives Scope Task or Requirements Selection Criteria Deliverables or Delivery Schedule Security Place of Performance Period of Performance 05-010

1.

2.

3.

4.

a) b) Establish the project

goal criteria

cost schedule c) d) e) performance deliverables review and approval gates Develop the

management plan

project for the Establish a

work breakdown structure

Create a

scope baseline

05-011

05-12 Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Figure 5.2

A process that sets a project’s scope by

breaking down

its overall

mission into

a cohesive set of synchronous, increasingly

specific tasks

.

What does WBS accomplish?

 Echoes project objectives      Offers a logical structure Establishes a method of control Communicates project status Improves communication Demonstrates control structure 05-13

1.0

1.2

1.2.1

1.2.2

1.2.3

1.2.3.1

1.2.3.2

05-14 1.3

1.3.1

1.3.2

1.4

The project is the overall project under development Deliverables are major project components Sub-deliverables are supporting deliverables Work Packages are individual project activities

05-15 Figure 5.7

05-16

In a team of two, prepare the WBS for:

1.

Launch of a new product 2.

Create a non lucrative association to help children on the street

05-17 o o o Organizational Breakdown Structure (OBS) allows Work definition Owner assignment of work packages Budget assignment to departments

OBS links cost, activity & responsibility

05-18 Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Figure 5.8

05-19 Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Figure 5.10

05-20 Figure 5.11

1.

2.

3.

4.

5.

6.

7.

Work package forms lowest level in WBS.

Work package has a deliverable result.

Work package has one owner.

Work package may be considered by its owner as a project in itself.

A work package may include several milestones.

A work package should fit organizational procedures and culture.

The optimal size of a work package may be expressed in terms on labor hours, calendar time, cost, reporting period, and risks.

05-21

05-22 The formal

“go ahead”

to begin work Follows the scope management steps of: 1.

scope definition 2.

3.

4.

planning documents management plans contractual documents

Most contracts contain:

Requirements Valid consideration Contracted terms

Contracts range from: Lump Sum also called “Turnkey” 05-23 Cost Plus

determines

what

reported,

who

types of information receives copies,

when

, and

how

information is acquired and disseminated.

Typical project reports contain 1.

Cost status 2.

3.

Schedule status Technical performance 05-24

05-25 o Configuration o Design o Trend monitoring o Document o Acquisition o Specification

The job is not over until the paperwork is done…

Closeout documentation is

used to

: Resolve disputes Train project managers Facilitate auditing Closeout documentation

includes

: Historical records Post project analysis Financial closeout 05-26

1.

2.

3.

4.

5.

Understand the importance of scope management for project success.

Understand the significance of developing a scope statement.

Construct a Work Breakdown Structure for a project.

Develop a Responsibility Assignment Matrix for a project.

Describe the roles of changes and configuration management in assessing project scope.

05-27