Scope Management Chapter 5 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall5-1.

Slides:



Advertisements
Similar presentations
Project Management Concepts
Advertisements

ELC 347 project management Day Agenda Questions Assignment 3 graded –3 A’s, 5 B’s, 2 C’s, 1 D, 2 F’s and 2 answered the wrong questions Assignment.
Day 8 ELC 347/BUS 348/PSA 347.
Project Management 6e..
NEES Project Management Workshop June 16 June 18 1 Segment 3.
EGR Defining the Project Step 1:Define the project scope Step 2:Establishing project priorities Step 3:Create the work breakdown structure Step.
EGR Defining the Project Step 1:Define the project scope Step 2:Establishing project priorities Step 3:Create the work breakdown structure Step.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
Defining the Project CHAPTER FOUR Student Version Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin.
Defining the Project Chapter 4.
McGraw-Hill/Irwin© 2008 The McGraw-Hill Companies, All Rights Reserved Defining the Project (modified for 2015) Chapter 4.
ELC 347 project management Week 5. Agenda Assignment 2 re-graded –Missing case 2.3 found and graded Assignment 3 Graded –Could have used more effort –case.
Project Management Session 7
Ch. 4 Project Definition.
Project Management and Scheduling
Module 9 Session 9.2 Visual 1 Module 9 Designing Control and Reporting Systems (Time, Cost, Resources and Scope (Performance and Quality)) Session 9.2Managing.
Project Closeout and Termination Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Chapter 14 Learning Objectives After completing.
Project Management An Overview John Mulhall MIICM; LIB International Credit & Process Management Professional.
Scope Management Chapter 5.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Goal and Scope Where are we going and what path will we be taking?
Edward B. Farkas, Managing Director, Project Management Practice
Chapter 4 Defining the Project.
Defining the Project CHAPTER FOUR PowerPoint Presentation by Charlie Cook Copyright © 2014 McGraw-Hill Education. All Rights Reserved.
What’s a Project? AD642. Why the Emphasis on Project Management? Copyright 2011 John Wiley & Sons, Inc. 1-2  Many tasks do not fit neatly into business-as-usual.
Week 6: Project Management E1102 – Design Fundamental Using Advanced Computer Technologies Spring 2010.
5-1Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall Scope Management Chapter 5.
Chapter 5 Project Scope Management
What’s a Project? AD642. Copyright 2011 John Wiley & Sons, Inc. Why the Emphasis on Project Management? 2 ❑ Many tasks do not fit neatly into business-as-usual.
Scope Management Chapter 5.
Welcome to Session 4 – Project Management Process Overview (continued) Instructor:Phyllis Sweeney Instructor: Phyllis Sweeney Project Management Certificate.
McGraw-Hill/IrwinCopyright © 2008 by The McGraw-Hill Companies, Inc. All Rights Reserved. Defining the Project Chapter 4.
Project Scope Management Project management Digital Media Department Unit Credit Value : 4 Essential Learning time : 120 hours.
DEFINING THE PROJECT CHAPTER 4.
Copyright 2008 Introduction to Project Management, Second Edition 2  Many people have heard the following sayings: ◦ If you fail to plan, you plan to.
Week 2 Seminar: Project Scope Management
5-1 Copyright © 2013 McGraw-Hill Education (Australia) Pty Ltd Pearson, Larson, Gray, Project Management in Practice, 1e CHAPTER 5 Defining the Scope of.
Scope Management. 5-2Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall Project Scope Project scope is everything about a project –
Scope Management Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Chapter 5 Learning Objectives After completing this chapter,
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall o P.I.I.M.T o American University of Leadership Ahmed Hanane, MBA, Eng, CMA, Partner.
© 2014 Pearson Education, Inc., Upper Saddle River, NJ. All rights reserved. This material is protected by Copyright and written permission should be obtained.
Develop Project Charter
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Chapter 3 Managing the Information Systems Project 3.1.
Project Management.
~ pertemuan 4 ~ Oleh: Ir. Abdul Hayat, MTI 20-Mar-2009 [Abdul Hayat, [4]Project Integration Management, Semester Genap 2008/2009] 1 PROJECT INTEGRATION.
Team-Based Development ISYS321 Managing the Information Systems Project.
1 Chapter 11 Planning. 2 Project Planning “establishing a predetermined course of action within a forecasted environment” “establishing a predetermined.
Information Technology Project Management, Seventh Edition.
Project Management 6e..
Project Management 6e..
Managing the Information Systems Project
Chapter 4 Defining the Project.
Project Management -- Defining the Project
WORK BREAKDOWN STRUCTURE
SCOPE MANAGEMENT Information Technology Project Management
Project Management.
Defining the Project Chapter 4.
Where We Are Now. Where We Are Now Defining the Project (100) Step 1: Defining the Project Scope Step 2: Establishing Project Priorities Step 3: Creating.
Scope management Chapter 5 Copyright ©2016 Pearson Education, Inc.
Defining the Project Step 1: Defining the Project Scope
Scope Management Chapter 5
Chapter 3 Managing the Information Systems Project
Project Close-Out and Termination
Project Close-Out and Termination
Scope Management Chapter 5
Chapter 3 Managing the Information Systems Project
Project Close-Out and Termination
Chapter 3 Managing the Information Systems Project
Presentation transcript:

Scope Management Chapter 5 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall5-1

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 development4) Scope reporting 2) Scope statement5) Control systems 3) Work authorization6) Project closeout Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall5-2

Conceptual Development The process that addresses project objectives by finding the best ways to meet them. Key steps in information development: Problem/need statement Information gathering Constraints Alternative analysis Project objectives Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall5-3

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 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall5-4

Statement of Work (SOW) A SOW is a detailed narrative description of the work required for a project. Effective SOWs contain 1.Introduction and background 2.Technical description 3.Timeline and milestones 4.Client expectations Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall5-5

The Scope Statement Process 1.Establish the project goal criteria a)cost b)schedule c)performance d)deliverables e)review and approval gates 2.Develop the management plan for the project 3.Establish a work breakdown structure 4.Create a scope baseline Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall5-6

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  Improves communication  Demonstrates control structure Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall5-7

Work Breakdown Structure and Codes Work Packages are individual project activities Deliverables are major project components Subdeliverables are supporting deliverables The project is the overall project under development Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall5-8

Sample WBS in MS Project Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall5-9

Defining a Work Package Lowest level in WBS Deliverable result One owner Miniature projects Milestones Fits organization Trackable Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall5-10

Organizational Breakdown Structure Organizational Breakdown Structure (OBS) allows Work definition Owner assignment of work packages Budget assignment to departments OBS links cost, activity & responsibility Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall5-11

Responsibility Assignment Matrix NotificationResponsible Support Approval LEAD PROJECT PERSONNEL Bob IS DaveSue HR Ann R&D Jim R&D Task & CodeDeliverable IS Match IT to Org. Tasks proposal Prepare Identify IS user needs 1.2 Problem Analysis Develop info Interview users show Develop Gain user “buy in” Find cost/ benefit info Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall5-12

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 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall5-13

Contractual Documentation Most contracts contain: Requirements Valid consideration Contracted terms Contracts range from: Lump SumCost Plus also called “Turnkey” Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall5-14

Scope Reporting determines what types of information reported, who receives copies, when, and how information is acquired and disseminated. Typical project reports contain 1.Cost status 2.Schedule status 3.Technical performance Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall5-15

Types of Control Systems oConfiguration oDesign oTrend monitoring oDocument oAcquisition oSpecification Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall5-16

Project Closeout 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 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall5-17

Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall5-18