ELC 347 project management

Day 8

Agenda

• Quiz 1 • October 2 (next Class) • Chapter 1-4 • M/C & essay questions • Entire Class period • Assignment 3 Graded • 3 A’s, 2 B’s, 2 C’s, 1 D & 1 F • • Some students could have used more effort case 3.1.xls

• Assignment 4 Posted • Due October 9 • Integrative Project • 1 st part due Oct 2, Post in File Exchange in Group Section of Blackboard • Outline of deliverables (posted in WebCT) • Scope Management • Using MS project

5-3

Scope Management

Chapter 5 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall

Project Scope

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

Conceptual Development

The process that addresses project objectives by finding the best ways to meet them.

Key steps in information development: 1.

2.

3.

4.

5.

Problem/need statement Information gathering Constraints Alternative analysis Project objectives

Problem Statements

Successful conceptual development requires: •

Reduction

of overall project

complexity

• Goals and objects are –

clearly stated

Reference points are provided • • Complete

understanding

of the problem You cannot solve a problem till you

UNDERSTAND

the problem

Statement of Work (SOW)

A SOW is a

detailed narrative description

required for a project.

of the work

Effective SOWs contain 1. Introduction and background 2. Technical description 1.

The more specific the better 3. Timeline and milestones 1.

Anticipated (hoped-for) 4. Client expectations 1.

What constitutes a project well done

The Scope Statement Process

1. Establish the project

goal criteria

(deliverables) a) cost b) schedule c) performance d) deliverables e) review gates 2. Develop the

management plan

for the project 3. Establish a

work breakdown structure

4. Create a

scope baseline

Work Breakdown Structure

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 Improved communication  Demonstrates control structure

WBS and goals

Example WBS

Work Breakdown Structure and Codes 1.0

The project is the overall project under development 1.2

1.3

1.4

1.2.1

1.3.1

Deliverables are major project components 1.2.2

1.3.2

1.2.3

Subdeliverables are supporting deliverables 1.2.3.1

Work Packages are individual project activities 1.2.3.2

Examples

Sample WBS in MS Project

Work Packages

Lowest level in WBS X.X.X.X Deliverable result One owner Miniature projects Milestones Fits organization Trackable

Organizational Breakdown Structure Organizational Breakdown Structure (OBS) allows • Work definition • Owner assignment of work packages • Budget assignment to departments

OBS links cost, activity & responsibility

Intersection of WBS and OBS

Responsibility Assignment Matrix

Deliverable Task & Code Match IT to Org. Tasks 1.1

Problem Analysis Develop info 1.1.1

1.1.2

Identify IS user needs 1.2

Interview users Develop show 1.2.1

1.2.2

Gain user “buy in” 1.2.3

LEAD PROJECT PERSONNEL Dave Sue IS HR Ann R&D Jim R&D Bob IS Prepare proposal 1.3 Find cost/ benefit info 1.3.1

Support Notification Responsible Approval

Work Authorization

The formal

“go ahead”

to begin work Follows the scope management steps of: 1. scope definition 2. planning documents 3. management plans 4. contractual documents

Contractual Documentation

Most contracts contain:

Requirements Valid consideration Contracted terms

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

Scope Reporting

determines what types of information reported, who receives copies, when, and how information is acquired and disseminated.

Typical project reports may contain 1. Cost status 2. Schedule status 3. Technical performance

Types of Control Systems

o Configuration o Design o Trend monitoring o Document o Acquisition o Specification

Project Closeout

The job is not over until the paperwork is done…

Closeout documentation is

used to

: Resolve contractual disputes Train project managers Facilitate auditing Closeout documentation

includes

: Historical records Post project analysis Financial closeout

Using MS project 2003

• Many of the required functions/reports in Project management are part of MS project 2003 – Industry wide acceptance • Do not use Wizard till you are comfortable with MS project • File ->New • Enter Project and all – Deliverables – Sub deliverables – Work packages • Indent using arrows to show decomposition – Template – Actual project • More on MS Project on Oct 6