ELC 347 project management Day 9. 3-2 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.

Slides:



Advertisements
Similar presentations
Project Management Concepts
Advertisements

Day 8 ELC 347/BUS 348/PSA 347.
Project Management 6e..
MANAGEMENT OF ENGINEERING PROJECT MANAGEMENT
NEES Project Management Workshop June 16 June 18 1 Segment 3.
Degree and Graduation Seminar Scope Management
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.
Chapter 4 Defining the Project. NEED FOR DEFINING PROJECTS One Project, small Many small projects, or large one –Yes.
Project Management Session 7
Chapter 3: The Project Management Process Groups
Chapter 5: Project Scope Management
Ch. 4 Project Definition.
Project Management Basics
Defining the Activities. Documents  Goal Statement defines why helps manage expectations  Statement of Work what gets delivered defines scope  Software.
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 Management An Overview John Mulhall MIICM; LIB International Credit & Process Management Professional.
Scope Management Chapter 5.
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.
1 Bonham, chapter 8 Knowledge Management. 2  8.1 Success Levels  8.2 Externally Focused KM  8.3 Internally Focused KM  8.4 PMO-Supported KM
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.
Scope Management Chapter 5 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall5-1.
5-1Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall Scope Management Chapter 5.
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.
© 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S.
McGraw-Hill/IrwinCopyright © 2008 by The McGraw-Hill Companies, Inc. All Rights Reserved. Defining the Project Chapter 4.
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
Strong9 Consulting Services, LLC 1 PMI - SVC I-80 Breakfast Roundtable Monthly Meeting Thursday, October 12, :00 am – 9:00 am.
SacProNet An Overview of Project Management Techniques.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
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 –
I n t e g r i t y - S e r v i c e - E x c e l l e n c e Business & Enterprise Systems The Integrated Master Plan (IMP) and the Integrated Master Schedule.
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.
Lecture 3 Title: Information Technology Project Methodology By: Mr Hashem Alaidaros MIS 434.
Develop Project Charter
~ 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.
THE MANAGERIAL PROCESS Clifford F. Gray Eric W. Larson PowerPoint Presentation by Charlie Cook The University of West Alabama Defining the Project Chapter.
Project Management 6e..
Project Management 6e..
Chapter 4 Defining the Project.
Project Management -- Defining the Project
WORK BREAKDOWN STRUCTURE
SCOPE MANAGEMENT Information Technology Project Management
Project Management.
Defining the Activities
Defining the Project Chapter 4.
MGMT 404 Enthusiastic Studysnaptutorial.com
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
MGT 605: CH 04 Defining the Project.
Project Management Process Groups
Scope Management Chapter 5
Presentation transcript:

ELC 347 project management Day 9

3-2 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 4 posted –Answer Case questions posted in blackboard –Due October 12:35 PM Quiz 1 October 7 Chapter 1-5 M/C & essay questions Integrative Project Part 1 in and I have started reading feedback will be posted soon Looking at part 2 on page 162 & 163 Part two will be due on October 18 Scope Management Using MS project

Scope Management Chapter 5

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

Conceptual Development The process that addresses project objectives by finding the best ways to meet them. Key steps in information development: 1. Problem/need statement 2. Information gathering 3. Constraints 4. Alternative analysis 5. 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 of the work required for a project. 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

Example WBS Making a PBJ –Gather materials Get 2 slices of bread Get peanut butter Get jelly Get butter knife –Assembly Using knife spread 1/8” layer of peanut butter on one side of one slice of bread Using knife spread 1/8” layer of peanut jelly on one side of the other slice of bread Place two slices of bread together with peanut butter in contact with jelly –Consumption Bite off a chunk of PBJ Chew Swallow

WBS and goals

Example WBS

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

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 See figure 5.6 on page 146 of text

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

Cost account rollup

Responsibility Assignment Matrix Notification Responsible 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

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 SumCost Plus also called “Turnkey”

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 oConfiguration oDesign oTrend monitoring oDocument oAcquisition oSpecification

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 2007 Many of the required functions/reports in Project management are part of MS project 2007 –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 –TemplateTemplate –Actual projectActual project More on MS Project as we progress through course