21
PROJECT SCOPE, SCHEDULE, AND RESOURCE MANAGEMENT

PROJECT SCOPE, SCHEDULE, AND RESOURCE MANAGEMENT

  • Upload
    earl

  • View
    37

  • Download
    1

Embed Size (px)

DESCRIPTION

PROJECT SCOPE, SCHEDULE, AND RESOURCE MANAGEMENT. TRIPLE CONSTRAINTS. Project Management Triple Constraints or “ Iron Triangle ” is a model of constraints of project management. PROJECT SCOPE MANAGEMET. SCOPE MANAGEMENT PROCESSES. - PowerPoint PPT Presentation

Citation preview

Page 1: PROJECT  SCOPE, SCHEDULE, AND RESOURCE MANAGEMENT

PROJECT SCOPE, SCHEDULE, AND RESOURCE MANAGEMENT

Page 2: PROJECT  SCOPE, SCHEDULE, AND RESOURCE MANAGEMENT

TRIPLE CONSTRAINTSProject Management Triple Constraints or “Iron Triangle” is a model of constraints of project management

Page 3: PROJECT  SCOPE, SCHEDULE, AND RESOURCE MANAGEMENT

PROJECT SCOPE MANAGEMET

Page 4: PROJECT  SCOPE, SCHEDULE, AND RESOURCE MANAGEMENT

SCOPE MANAGEMENT PROCESSES

Collect Requirements: Determining and documenting stakeholder needsDefine Scope: Developing detailed description of project and productCreate WBS: Subdividing project deliverables and project work into smaller, more manageable parts

Page 5: PROJECT  SCOPE, SCHEDULE, AND RESOURCE MANAGEMENT

WORK BREAKDOWN STRUCTURE

(WBS)

Page 6: PROJECT  SCOPE, SCHEDULE, AND RESOURCE MANAGEMENT

WHAT IS WBS?Project Management Inctitute (PMI) defines WBS as:

“A hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables”

Page 7: PROJECT  SCOPE, SCHEDULE, AND RESOURCE MANAGEMENT

WHAT IS WBS?Wikipedia defines WBS as:“A work breakdown structure (WBS), in project management and systems engineering, is a deliverable oriented decomposition of a project into smaller components. It defines and groups a project's discrete work elements in a way that helps organize and define the total work scope of the project.”

“A work breakdown structure element may be a product, data, service, or any combination.”

Page 8: PROJECT  SCOPE, SCHEDULE, AND RESOURCE MANAGEMENT

WBS TYPESApproaches to break activities into detail by:

Product component approachExamples: Design documents, manuals, the running system

Functional approachAnalysis, design, implementation, integration, testing, delivery, reviews

Geographical area Examples: TUM team, CMU team, off-shore team, ...

Organizational approachResearch, product development, marketing, sales

Page 9: PROJECT  SCOPE, SCHEDULE, AND RESOURCE MANAGEMENT

WBS LEVELS Each level of WBS represents an increasingly

detailed definition of project

WBS lays out the individual elements that will

construct the project

Each element must be numbered

Lowest level elements are called “Work Packages”

Page 10: PROJECT  SCOPE, SCHEDULE, AND RESOURCE MANAGEMENT

WBS LEVELS AND NUMBERINGMajor project deliverables or activities are identified

Codes assigned to each WBS componentLevel 0 - project itselfLevel 1 - major deliverablesLevel 2 - individual components of each deliverableEtc.Final level – work package

Page 11: PROJECT  SCOPE, SCHEDULE, AND RESOURCE MANAGEMENT

WBS NUMBERING SYSTEM

Work Packages are individual project activities

05-11

1.0

1.2 1.3 1.4

1.2.1

1.2.2

1.2.3

1.3.1

1.3.2

1.2.3.1

1.2.3.2

Deliverables are major project components

Sub-deliverables are supporting deliverables

The project is the overall project under development

Page 12: PROJECT  SCOPE, SCHEDULE, AND RESOURCE MANAGEMENT

PRODUCT WBS

Page 13: PROJECT  SCOPE, SCHEDULE, AND RESOURCE MANAGEMENT

PROCESS WBS

Page 14: PROJECT  SCOPE, SCHEDULE, AND RESOURCE MANAGEMENT

WBS PURPOSEProject Scope: Shows all project activities that will be necessary to doProject Chart: Project organization shows structural hierarchy of project team. WBS shows structural hierarchy of project work to be doneProject Time & Cost Estimation: Work packages are used to estimate time & cost, and they are rolled-up (aggregated) upwardsProject Measurement & Control: Each work package is assigned a cost account, and its status is tracked

Page 15: PROJECT  SCOPE, SCHEDULE, AND RESOURCE MANAGEMENT

WBS DESIGNTop-DownBottom-UpBoth Top-Down & Bottom-UpRolling Wave – greater decomposition occurs as project components becomes more defined over timeEach level should contain around +/- 7 elements

Page 16: PROJECT  SCOPE, SCHEDULE, AND RESOURCE MANAGEMENT

WORK PACKAGEWork packages should contain activities that are short in duration (1 or 2 weeks) Work package activities can be completed by an individual or a small teamAll work packages should be similar in size or effort needed unless work package is being outsourced to another company

Page 17: PROJECT  SCOPE, SCHEDULE, AND RESOURCE MANAGEMENT

WBS REPRESENTATIONOrganization Chart (Tree-Structued like in previous examples)Indented ListBubble-Chart

Page 18: PROJECT  SCOPE, SCHEDULE, AND RESOURCE MANAGEMENT

PROJECT TIME MANAGEMENT

Page 19: PROJECT  SCOPE, SCHEDULE, AND RESOURCE MANAGEMENT

TIME MANAGEMENT PROCESSESDefine Activities: Identify specific actions to be performed to produce project deliverablesSequence Activities: Identifying relationships among project activitiesEstimate Activity Resources: Estimate type of quantities of material, human resources, equipment, or supplies to perform each activityEstimate Activity Durations: Estimate number of hours to complete each activityDevelop Schedule: Analyze activity sequences, durations, resource requirements, and schedule constraints to create schedule model

Page 20: PROJECT  SCOPE, SCHEDULE, AND RESOURCE MANAGEMENT

DEFINE ACTIVITIES Break down work packages into activities that provide a basis for estimating, scheduling, executing, monitoring, and controlling Activity definitions include description, name, identifier, WBS (Work Package) ID, predessor & successor activities, leads & lags, resource requirements, imposed dates, constraints, and assumptions, person responsible, etc.

Page 21: PROJECT  SCOPE, SCHEDULE, AND RESOURCE MANAGEMENT

ACTIVITIES IN MS PROJECT