There is no more critical function in the management of successful projects than managing the project scope and changes to that scope, which includes identifying the requirements of the product the project will create so that changes to it can be identified, analyzed, and implemented. As a result, a scope management process consists of two important components—identifying the scope baseline and managing changes to it.
Without the establishment of a solid project scope, which is often referred to as requirements definition in information technology projects or product specification in manufacturing, it’s impossible to know the impact of proposed changes. In addition, those requirements must be prioritized and analyzed to allow effective decisions to be made about proposed changes.
As a result, project managers spend a considerable amount of time and energy fighting against what seems to be an unending onslaught of changes in the direction and scope of their projects. Without a workable understanding of the dynamics of change and a means of managing scope changes, project managers can get frustrated and project success can be threatened.
Since scope changes are inevitable, they must be managed very carefully to ensure the project is completed successfully. Project scope change management is the process of determining which requested changes to the product of the project will be made, when they will be made, and the impact they will have on the project deliverables and the project. It is used to limit and coordinate requirements and specification changes that arise during the life of a project.
This two-day workshop is compliant with the standards for business analysis and requirements definition, the Business Analysis Body of Knowledge (hereafter described as the BA BOK), which is being prepared by the International Institute of Business Analysis™ (IIBA). This workshop is also compliant with the Project Management Body of Knowledge (the PMBOK® Guide, Third Edition).
The objectives of the workshop are to:
- Introduce project managers to the challenges of project scope changes and models of project change that allow them to place changes in perspective
- Present a model for managing scope change
- Review the scope change processes embedded in the PMBOK® Guide, Third Edition.
- Review requirements identification and documentation processes that contribute to effective scope change control that are embedded in the BA BOK Guide
- Identify skills for effective scope change management
- Introduce participants to scope change management best practices and tools
- Allow participants to build skills through application of skills and techniques in a workshop setting
Day 1:
- Module 1: Introduction to the workshop
In this module, participants will be introduced to the workshop content and format and have the chance to introduce themselves and identify their expectations for the workshop.
- Module 2: Introduction to scope change
In this module, the challenges of project scope changes will be identified and a metaphor established for identifying and managing scope changes.
- Module3: Scope change management within the PMBOK® Guide and BA BOK
In this module, both the PMBOK® Guide and the BA BOK™ will be examined to determine their treatment of scope changes from the perspectives of the project manager and business analyst.
- Module 4: Scope change management planning
In Module 4, we’ll examine the elements of a solid scope management plan and the techniques for creating one.
- Module 5: Scope definition and documentation
Because scope changes can’t be identified or monitored without a good understanding and documentation of the project scope, we’ll identify the processes for scope definition and documentation.
Day #2
- Module 6: Scope change identification
In Module 6, we’ll survey the methods available for identifying scope changes to include passive and active scope change monitoring.
- Module 7: Scope change analysis and documentation
This module will examine the techniques for analyzing changes to
determine theirimpact on project objectives, schedule and cost.
- Module 8: Scope change decision, documentation, and communication
Module 8 is dedicated to the processes of making solid scope change decisions, documenting those decisions, and communicating the impact of those changes to affected parties.
- Module 9: Scope change implementation and assessment
This module describes the processes involved in implementing scope changes and assessing their impact.
- Module 10: Workshop Wrap-up
This module provides participants with the opportunity to ask remaining questions and evaluate the workshop.