Project Scope Management

Course Number: PROJMGT 7080
Course Name: Project Scope Management (Online)
Course Description:    Project scope management includes the processes required to ensure that the project includes all the work required, and only the work required, to complete the project successfully.  Defining scope ensures the successful management of other key project management areas, including time, cost, and quality, since it is the foundation upon which the schedule, the budget, the resource plan, and the overall project management plan, are prepared. Topics include scope management planning, collecting requirements, defining product and project scope, creating work breakdown structures, validating product and project scope, and controlling changes to product or project scope.
Prerequisites:    PROJMGT 7010 and PROJMGT 7020
Level: Graduate
Credits: 3
Format: Online
Program: Master of Science in Project Management

Registration Instructions

NOTE: The information below is representative of the course and is subject to change.  The specific details of the course will be available in the Desire2Learn course instance for the course in which a student registers.

Additional Information

Learning Outcomes
Upon completion of this course, you should be able to

  • Synthesize the content of a case study and prepare a project charter, stakeholder register, and complete a stakeholder analysis for a simple and complex project as an individual and as a member of a virtual team, respectively.
  • Collaborate with team members and establish business rules for virtual teams.
  • Synthesize case study materials and work in a virtual team to create a scope statement, work breakdown structure (WBS) and WBS dictionary for a complex project.
  • Synthesize case study materials and create a work breakdown structure (WBS) and WBS dictionary for a simple project.
  • Explain the relationships between project scope baseline and several project artifact documents.
  • Discuss the value added by project scope management
  • Appreciate and understand the context of the project environment as it relates to the project owner, sponsor, manager, and project environment.
  • Compare the advantages and disadvantages of requirements management tools
  • Explain the importance of a Work Breakdown Structure (WBS) and WBS dictionary in project management, and construct and critique a WBS and a WBS dictionary.
  • Devise scope validation for formal acceptance procedures.
  • Devise a configuration management system.
  • Devise a project change control process.
  • Research and discuss scope control and other aspects of project scope management.

Unit Descriptions
Course Organization and Assignment Descriptions

Unit 1: Portfolio Management Key Concepts

Scope management planning takes place at the beginning of a project when the project charter and the stakeholder register are completed during the initiation phase. This unit focuses on taking the high-level project requirements (and its deliverable product requirements) found in the project charter and further defining them in more detail to satisfy stakeholders. Requirements collection results in linking the business/operational need of the customer/organizational element with the requirements of the product/project, stakeholders, and the priority. After assembling the requirements for a project, the scope statement is developed to define the work that will be done to meet those requirements. A project scope statement has specific elements included, which are discussed in detail in the course readings. Important documents to develop a project scope statement include the project charter and the requirements management plan/requirements traceability matrix. The project scope statement can be used as a feeder document to planning risk management, developing a project schedule, and estimating and sequencing activities as part of project integration. The project scope statement is also a key resource document for the development the Work Breakdown Structure (WBS).

Upon completion of this unit, you should be able to

  • Prepare a project charter.
  • Prepare a stakeholder register.
  • Differentiate between project scope and product scope.
  • Determine appropriate requirements analysis techniques to use in different projects.
  • Understand the requirements definition process.
  • Prepare a requirements traceability matrix.
  • Define the key elements of a requirements management plan.
  • Prepare a requirements management plan.
  • Prepare a project scope statement.

Unit 2: Transitioning to Portfolio Management

The Work Breakdown Structure (WBS) is an important tool in project scope management. The WBS is one of the most frequently neglected tools in project management. These two statements illustrate a gap in the understanding of the WBS and its role in project management. This unit focuses on the WBS and why it's an important tool for the project manager and key stakeholders, as well as how to properly construct the WBS. The WBS, WBS dictionary, and project scope statement combine to form the project's scope baseline. The scope baseline is essential for the planning project procurements, human resources, risk management, and quality. We will focus on the WBS dictionary as a transitional tool to properly develop the project budget, activity network, and project schedule.

Upon completion of this unit, you should be able to

  • Discuss concepts of work decomposition.
  • Prepare a WBS using various formats.
  • Prepare a WBS dictionary.
  • Identify problems in a WBS.
  • Discuss project problems related to defects in the WBS.
  • Apply quality principles to development of a WBS.
  • Explain the relationship between the scope baseline and other knowledge areas of project management.

Unit 3: Porfolio Managment Model

Once a project is underway, the project team must be aware of internal and external factors and stakeholders that can cause loss of control in the scope. This loss of control can often be the result of "feature creep," where the product features change because of stakeholder changes to the scope baseline. It is common, and often expected, to have changes occur over the course of a project. Configuration management aids in the control of scope and is its own "system" of procedures that can be used to identify and document the characteristics of a product (or other outcome of the project). A configuration management system is related to the project quality control plan that is used to verify that each deliverable meets the required characteristics of a product. Planning for the verification of each deliverable and ensuring that a system is in place to control the scope of the product/project will help a project manager maintain the schedule and budget and will ensure that key stakeholders approve delays and budget overruns if they are necessary.

Upon completion of this unit, you should be able to

  • Define the scope verification process.
  • Describe various tools and techniques for scope verification.
  • Describe how scope verification relates to quality control.
  • Determine what must be done to obtain formal acceptance.
  • Describe needed supporting documentation.
  • Explain the next steps if formal acceptance is not obtained.
  • Define project scope control.
  • Describe its interface to the Integrated Change Control Process.
  • Recognize the inevitability of change on projects.
  • Explain scope creep.
  • Discuss the importance of a change control system.
  • Recognize how it fits into the project management information system.
  • Describe why project configuration management is required.
  • Explain configuration management planning.
  • Manage change in the context of project configuration management.
  • Perform configuration status accounting.
  • Discuss different methods of configuration verification and audits.

Grading Criteria for Activities
The following table presents a breakout of points allocated to each unit:

Unit Individual Points Group Points Percentage
1 - Plan/Collect 100 points 150 points 25%
2 - Define/Create 200 points 125 points 32.5%
Term Paper 100 points   10%
3 - Control/Validating 200 points 125 points 32.5%
Total: 600 points 400 points 100%

The following presents a breakout of points by assignment type:

Assignments Possible Points Percentage
Individual Assignments 600 points 60%
Group Rules of Engagement 25 points 2.5%
Group Assignments 300 points 30%
Peers/Self Evaluation 75 points 7.5%
Total: 1,000 points 100%

Grading Scale

A 94% - 100%
A- 91% - 93%
B+ 88% - 90%
B 84% - 87%
B- 81% - 83%
C+ 78% - 80%
C 74% - 77%
C- 71% - 73%*
D+ 68% - 70%
D 64% - 67%
D- 61% - 63%
F 0% - 60%

*You must earn a grade of C or better in order for your credits to count toward a Master of Science in Project Management; however, a lower grade will be reflected in your overall grade point average.

Footer Anchor