Case Study: Scope Management

Only available on StudyMode
  • Topic: Project management, Work breakdown structure, Project management process
  • Pages : 18 (3477 words )
  • Download(s) : 740
  • Published : November 4, 2012
Open Document
Text Preview
INSTRUCTOR’S RESOURCE MANUAL
 
 
CHAPTER FIVE
Scope Management
 
 
 
 
 
 
 
 
 
To Accompany
 
PROJECT MANAGEMENT:
Achieving Competitive Advantage
 
 
By
Jeffrey K. Pinto
 
 
 
 
 
 
CHAPTER FIVE
 
PROJECT PROFILE — Airbus A380: Plane of the Future or Enormous White Elephant?
Introduction
5.1  CONCEPTUAL DEVELOPMENT
            The Statement of Work
5.2  THE SCOPE STATEMENT
            The Work Breakdown Structure
            Purpose of the Work Breakdown Structure
            The Organization Breakdown Structure
            The Responsibility Assignment Matrix
5.3  WORK AUTHORIZATION
5.4  SCOPE REPORTING
Project Management Research in Brief: IT Project Failure – Burying Our Heads in the Sand
5.5  CONTROL SYSTEMS
            Configuration Management
5.6  PROJECT CLOSEOUT
Summary
Key Terms
Discussion Questions
Problems
Case Study 5.1: Calcutta’s Metro
Case Study 5.2: Project Management at Dotcom.com
Cas Study 5.3: Runaway Scope – The Bradley Fighting Vehicle
Internet Exercises
MSProject Exercises
Integrated Project – Developing the Work Breakdown Structure Bibliography
 
 
 
 
 
TRANSPARENCIES
 
5.1 ELEMENTS IN PROJECT SCOPE MANAGEMENT
 
1.  Conceptual Development
     - Problem statement
     - Information gathering
     - Constraints
     - Alternative analysis
     - Project objectives
     - Statement of Work (SOW)
 
2.  Scope Statement
     - Goal criteria
     - Management plan
     - Work Breakdown Structure (WBS)
     - Scope baseline
     - Responsibility Assignment Matrix (RAM)
 
3.  Work Authorization
     - Contractual requirements
     - Valid consideration
     - Contracted terms
 

5.1 ELEMENTS IN PROJECT SCOPE MANAGEMENT (Con’d)
 
4.  Scope Reporting
     - Cost, Schedule, Technical performance status
     - S curves
     - Earned value
     - Variance or exception reports
 
5.  Control Systems
     - Configuration control
     - Design control
     - Trend monitoring
     - Document control
     - Acquisition control
     - Specification control
 
6.  Project Closeout
     - Historical records
     - Post-project analysis
     - Financial closeout
 

5.2 PURPOSES OF THE WORK BREAKDOWN STRUCTURE
 
 
1. IT ECHOES PROJECT OBJECTIVES.
 
 
2. IT IS THE ORGANIZATION CHART FOR THE PROJECT.
 
 
3. IT CREATES THE LOGIC FOR TRACKING COSTS, SCHEDULE, AND PERFORMANCE SPECIFICATIONS FOR EACH ELEMENT IN THE PROJECT.
 
 
4. IT MAY BE USED TO COMMUNICATE PROJECT STATUS. 
 
 
5. IT MAY BE USED TO IMPROVE OVERALL PROJECT COMMUNICATION. 
 
 
6. IT DEMONSTRATES HOW THE PROJECT WILL BE CONTROLLED.
 
 
 

5.3 PARTIAL WORK BREAKDOWN STRUCTURE
 
 
 
 
 
 
 
 
 
 
 
 
 

5.4 THE INTERSECTION OF THE WBS AND OBS
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

5.5...
tracking img