Scope Management Sumary

timer Asked: Feb 23rd, 2019
account_balance_wallet $10

Question Description

Watch and read the power points and write two pages summarizing

no need for sources just summarize the video

Here is the link for the video:

SCOPE MANAGEMENT Chapter 5 Copyright ©2016 Pearson Education, Inc. CHAPTER 5 LEARNING OBJECTIVES After completing this chapter, you should be able to: 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. Copyright ©2016 Pearson Education, Inc. 5-2 PMBOK CORE CONCEPTS Project Management Body of Knowledge (PMBoK) covered in this chapter includes: 1. Develop Project Charter (PMBoK 4.1) 2. Plan Scope Management (PMBoK 5.1) 3. Collect Requirements (PMBoK 5.2) 4. Define Scope (PMBoK 5.3) 5. Create WBS (PMBoK 5.4) 6. Validate Scope (PMBoK 5.5) 7. Control Scope (PMBoK 5.6) Copyright ©2016 Pearson Education, Inc. 5-3 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 2) Scope statement 3) Work authorization Copyright ©2016 Pearson Education, Inc. 4) Scope reporting 5) Control systems 6) Project closeout 5-4 CONCEPTUAL DEVELOPMENT The process that addresses project objectives by finding the best ways to meet them Key steps in information development:  Problem or need statement  Requirements gathering  Information gathering  Constraints  Alternative analysis  Project objectives  Business case Copyright ©2016 Pearson Education, Inc. 5-5 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 of the project 3. Timeline and milestones Copyright ©2016 Pearson Education, Inc. 5-6 STATEMENT OF WORK COMPONENTS  Background  Objectives  Scope  Task or Requirements  Selection Criteria  Deliverables or Delivery Schedule  Security  Place of Performance  Period of Performance Copyright ©2016 Pearson Education, Inc. 5-7 PROJECT CHARTER  Many organizations establish after the SOW  A document issued by the project initiator or sponsor formally sanctioning existence of project and authorizes project manager to begin applying organizational resources to project activities  Is created once project sponsors have done their “homework” to verify that there is:  a business case for the project  elements of project are understood  company-specific information for the project has been applied  Demonstrates formal company approval of the project Copyright ©2016 Pearson Education, Inc. 5-8 SCOPE STATEMENT 1. Establish project goal criteria to include: a) cost b) schedule c) performance d) deliverables e) review and approval “gates” 2. Develop management plan for project 3. Establish a Work Breakdown Structure 4. Create a scope baseline Copyright ©2016 Pearson Education, Inc. 5-9 WORK BREAKDOWN STRUCTURE (WBS) A deliverable-oriented grouping of project elements which organizes and defines the total scope of the project. Each descending level represents an increasingly detailed definition of a project component. Project component may be products or services. Copyright ©2016 Pearson Education, Inc. 5-10 WORK BREAKDOWN STRUCTURE PURPOSE WBS serves six main purposes: 1. Echoes project objectives 2. Organization chart for the project 3. Creates logic for tracking costs, schedule, and performance specifications 4. Communicates project status 5. Improves project communication 6. Demonstrates control structure Copyright ©2016 Pearson Education, Inc. 5-11 DEFINING A WORK PACKAGE Lowest level in WBS Deliverable result One owner Miniature projects Milestones Fits organization Trackable Copyright ©2016 Pearson Education, Inc. 5-12 PARTIAL WBS (FIGURE 5.3) Deliverables are major project components Work Packages are individual project activities (lowest level in WBS) Copyright ©2016 Pearson Education, Inc. 5-13 SAMPLE WBS IN MS PROJECT 2013 (FIGURE 5.6) Copyright ©2016 Pearson Education, Inc. 5-14 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 ©2016 Pearson Education, Inc. 5-15 INTERSECTION OF THE WBS AND OBS (FIGURE 5.7) Copyright ©2016 Pearson Education, Inc. 5-16 COST ACCOUNT ROLLUP USING OBS (FIGURE 5.9) Copyright ©2016 Pearson Education, Inc. 5-17 RESPONSIBILITY ASSIGNMENT MATRIX (FIGURE 5.10) Copyright ©2016 Pearson Education, Inc. 5-18 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. Work package may include several milestones. 6. 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. Copyright ©2016 Pearson Education, Inc. 5-19 WORK AUTHORIZATION The formal “go ahead” to begin work. Contractual documentation possesses some key identifiable features: ➢ Contractual requirements ➢ Valid consideration ➢ Contracted terms Contracts range from: Lump Sum or Turnkey Copyright ©2016 Pearson Education, Inc. Cost Plus 5-20 SCOPE REPORTING Determines what types of information reported, who receives copies, and when and how information is acquired and disseminated. Typical project reports contain: 1. Cost status 2. Schedule status 3. Technical performance status Copyright ©2016 Pearson Education, Inc. 5-21 REASONS WHY PROJECTS FAIL  Politics  Naïve promises  Naïve optimism of youth  Startup mentality of fledgling entrepreneurial companies  “Marine Corps” mentality  Intense competition caused by globalization  Intense competition caused by appearance of new technologies  Intense pressure caused by unexpected government regulations  Unexpected and/or unplanned crises Copyright ©2016 Pearson Education, Inc. 5-22 TYPES OF CONTROL SYSTEMS ➢Configuration control ➢Design control ➢Trend monitoring ➢Document control ➢Acquisition control ➢Specification control Copyright ©2016 Pearson Education, Inc. 5-23 CONFIGURATION MANAGEMENT Configuration Management is defined as: A system of procedures that monitors emerging project scope against the baseline. It requires documentation and management approval on any change to the baseline. Baseline is defined as: The project’s scope fixed at a specific point in time – for example, the project’s scheduled start date. Copyright ©2016 Pearson Education, Inc. 5-24 PROJECT CHANGES Occur for one of several reasons:  Initial planning errors, either technological or human  Additional knowledge of project or environmental conditions  Uncontrollable mandates  Client requests Copyright ©2016 Pearson Education, Inc. 5-25 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 ©2016 Pearson Education, Inc. 5-26 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. Copyright ©2016 Pearson Education, Inc. 5-27 Copyright ©2016 Pearson Education, Inc. as Prentice Hall Copyright © 2013 Pearson Education, Inc. Publishing 5-28

Tutor Answer

School: Rice University


Surname 1

Name of student
Professor’s name
Course title
Scope Management
By definition, scope management refers to the process of controlling and overseeing a
project in line with the set goals and objectives. Good scope management must outline the
criteria to be used to determine the achievement of each goal. Some of the activities involved
in scope management include conceptual development, stating the scope of the work,
authorization of work, scope reporting, control systems, and finally project closeout.
Conceptual development is the first activity, and it involves identifying the objectives of the
project and establishing the best way to meet them.
After the development of the conceptual framework, the project requires a statement
of Work. This step involves giving a detailed description of the activities that are required to
complete the proj...

flag Report DMCA

Thank you! Reasonably priced given the quality not just of the tutors but the moderators too. They were helpful and accommodating given my needs.

Similar Questions
Hot Questions
Related Tags
Study Guides

Brown University

1271 Tutors

California Institute of Technology

2131 Tutors

Carnegie Mellon University

982 Tutors

Columbia University

1256 Tutors

Dartmouth University

2113 Tutors

Emory University

2279 Tutors

Harvard University

599 Tutors

Massachusetts Institute of Technology

2319 Tutors

New York University

1645 Tutors

Notre Dam University

1911 Tutors

Oklahoma University

2122 Tutors

Pennsylvania State University

932 Tutors

Princeton University

1211 Tutors

Stanford University

983 Tutors

University of California

1282 Tutors

Oxford University

123 Tutors

Yale University

2325 Tutors