Presentation is loading. Please wait.

Presentation is loading. Please wait.

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

Similar presentations


Presentation on theme: "Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 8."— Presentation transcript:

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

2 Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Ch 1 -2 Agenda Questions? IP part 1 Late IP Part 2 Due Oct 10 (or maybe Oct 14) Group work days  Oct 3 Assignment 3 Due Due September 30 prior to class Assignment 4 Posted Read Case Study 4.3, Problems with John (page 130) and 5.4, Classic Case: The Ford Edsel. (page 167). Complete and upload the answers to the Questions at the end of each case study. In addition, complete the MS Project Exercise Project Outline-Remodeling an Appliance on page 171 of the text. Upload a MS project file (*.mpp) Due Oct 7 Exam 1 on Oct 7 Chaps 1-5 Open Book Open Notes 80 min. Scope Management

3 Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Scope Management 05-03

4 Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Chapter 5 Learning Objectives 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

5 Copyright © 2013 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 development4) Scope reporting 2) Scope statement5) Control systems 3) Work authorization6) Project closeout 05-05

6 Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall 1) Conceptual Development The process that addresses project objectives by finding the best ways to meet them. Key steps in information development: a. Problem/need statement b. Information gathering c. Constraints d. Alternative analysis e. Project objectives 05-06

7 Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall 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 05-07

8 Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall 2) 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 05-08

9 Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Statement of Work Components Background Objectives Scope Task or Requirements Selection Criteria Deliverables or Delivery Schedule Security Place of Performance Period of Performance Statement of work.docx 05-09

10 Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall 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

11 Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Goal Setting With and Without Work Breakdown Structures (WBS) Figure 5.2 Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall

12 Work Breakdown Structure (WBS) 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-12

13 Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Example WBS 1. Making a PBJ 1. Gather materials 1. Get 2 slices of bread 2. Get peanut butter 3. Get jelly 4. Get butter knife 2. Assembly 1. Using knife spread 1/8” layer of peanut butter on one side of one slice of bread 2. Using knife spread 1/8” layer of jelly on one side of the other slice of bread 3. Place two slices of bread together with peanut butter in contact with jelly 3. Consumption 1. Bite off a chunk of PBJ 2. Chew 3. Swallow

14 Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Defining a Project Work Package 1. Work package forms lowest level in WBS. 2. Work package has a deliverable result. 3. Work package has one owner. 4. Work package may be considered by its owner as a project in itself. 5. A work package may include several milestones. 6. A work package should fit organizational procedures and culture. 7. The optimal size of a work package may be expressed in terms on labor hours, calendar time, cost, reporting period, and risks

15 Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Work Breakdown Structure and Codes Work Packages are individual project activities Deliverables are major project components Sub-deliverables are supporting deliverables The project is the overall project under development 05-15

16 Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Sample WBS in MS Project Figure 5.7 PBJ.mpp

17 Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Sample WBS in ProjectLibre 17

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

19 Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Intersection of the WBS and OBS Figure 5.8 Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall

20 Cost Account Rollup Using OBS Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Figure 5.10

21 Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Responsibility Assignment Matrix Figure 5.11

22 Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall 3) 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 05-22

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

24 Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall 4) 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 05-24

25 25

26 Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall 5) Types of Control Systems o Configuration o Design o Trend monitoring o Document o Acquisition o Specification templates\Project Exception report.doc templates\Technology Project Assessment xls

27 Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall 6) 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 05-27

28 Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Reasons Why (IT) Projects Fail Politics Naïve promises Naïve optimism of youth Startup mentality of fledging entrepreneurial companies “Marine Corps” mentality Intensive competition caused by globalization Intense competition caused by appearance of new technologies Intense pressure caused by unexpected government regulations Unexpected and/or unplanned crises 05-28

29 Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Using MS project 2010 (and ProjectLibre) Many of the required functions/reports in Project management are part of MS project 2010 Industry wide acceptance Do not use Wizard till you are comfortable with MS project File  New  Blank Project Enter Project and all Deliverables Sub deliverables Work packages Indent using arrows to show decomposition Template Actual project More on MS Project as we progress through course

30 Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Summary 1. Understand the importance of scope management for project success. 2. Understand the significance of developing a scope statement. 3. Construct a Work Breakdown Structure for a project. 4. Develop a Responsibility Assignment Matrix for a project. 5. Describe the roles of changes and configuration management in assessing project scope

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


Download ppt "Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 8."

Similar presentations


Ads by Google