1 / 25

Scope Management

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:

Download Presentation

Scope Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Scope Management Chapter 5

  2. 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 4) Scope reporting 2) Scope statement 5) Control systems 3) Work authorization 6) Project closeout

  3. Conceptual Development The process that addresses project objectivesby finding the best ways to meet them. Key steps in information development: • Problem/need statement • Information gathering • Constraints • Alternative analysis • Project objectives

  4. 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

  5. Statement of Work (SOW) A SOW is a detailed narrative description of the work required for a project. Effective SOWs contain • Introduction and background • Technical description • Timeline and milestones • Client expectations

  6. The Scope Statement Process • Establish the project goal criteria • cost • schedule • performance • deliverables • review and approval gates • Develop the management planfor the project • Establish a work breakdown structure • Create a scope baseline

  7. Work Breakdown Structure a process that sets a project’s scope by breaking downits 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

  8. 1.0 1.2 1.3 1.4 1.3.1 1.2.1 1.3.2 1.2.2 1.2.3 1.2.3.1 1.2.3.2 Work Breakdown Structure and Codes The project is the overall project under development Work Packages are individual project activities Deliverables are major project components Subdeliverables are supporting deliverables

  9. Organizational Breakdown Structure Organizational Breakdown Structure (OBS) allows • Work definition • Owner assignment of work packages • Budget assignment to departments OBS links cost, activity & responsibility

  10. LEAD PROJECT PERSONNEL Task Ann Dave Sue Jim Bob Deliverable & Code HR R&D IS IS R&D Match IT to Problem 1.1.1 Org. Tasks Analysis 1.1 Develop 1.1.2 info Interview Identify IS user needs 1.2.1 users 1.2 Develop 1.2.2 show Gain user 1.2.3 “buy in” Prepare Find cost/ 1.3.1 proposal benefit info 1.3 Responsibility Assignment Matrix Support Notification Responsible Approval

  11. Work Authorization The formal “go ahead” to begin work Follows the scope management steps of: • scope definition • planning documents • management plans • contractual documents

  12. Contractual Documentation Most contracts contain: Requirements Valid consideration Contracted terms Contracts range from: Lump Sum Cost Plus also called “Turnkey”

  13. Scope Reporting determines what types of information reported, whoreceives copies, when, and how information is acquired and disseminated. Typical project reports contain • Cost status • Schedule status • Technical performance

  14. Types of Control Systems • Configuration • Design • Trend monitoring • Document • Acquisition • Specification

  15. 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

  16. What about IT Projects????

  17. FLOWCHART

  18. Sample WBS in MS Project

  19. LEAD PROJECT PERSONNEL Task Ann Dave Sue Jim Bob Deliverable & Code HR R&D IS IS R&D Match IT to Problem 1.1.1 Org. Tasks Analysis 1.1 Develop 1.1.2 info Interview Identify IS user needs 1.2.1 users 1.2 Develop 1.2.2 show Gain user 1.2.3 “buy in” Prepare Find cost/ 1.3.1 proposal benefit info 1.3 Responsibility Assignment Matrix Support Notification Responsible Approval

More Related