INTRODUCTION
Managing project scope, gathering requirements, and meeting customers’ expectations are a major part of a project manager’s work. Weaknesses and deficiencies in the scope definition process – including incomplete or poorly executed stakeholder analysis, and mishandled communication – can lead to unnecessary and costly changes, rework, and even project failures.
As a key part of the triple constraints,
scope is often the most challenging constraint to manage. As a project progresses "scope creep” often occurs due to the lack of management of the constant changes. Customers’ needs, the project sponsor’s needs, and other stakeholders’ needs often are in conflict. Learn how to achieve project success by mastering requirements definition and scope control.
WHO SHOULD ATTEND?
·
For project team members, team leaders, business analysts, project managers, program managers, PMO managers, program or project directors, sponsors, and any persons functioning in a project environment
·
Participants responsible for all types of projects, from construction to new product development to information technology, will take home tools and techniques to put to immediate use
PROGRAMME OBJECTIVES
·
Determine the business needs that drive a project
·
Define the difference between product scope and project scope
·
Determine how a project integrates with the overall operations of an organization
·
Identify and apply appropriate quality requirements
·
Define the inputs, outputs, and tools and techniques of the scope management processes
·
Identify and apply the proper methodology to effectively define the scope of a project and determine macro risks
·
Understand the ways of dealing with changes to the project scope
·
Create a Work Breakdown Structure to define scope
·
Be able to properly verify the project scope
·
Determine how to control the project scope during the execution phase of the project
TRAINING METHODOLOGY
In this class the participants will participate in group exercises, integrated case studies,
training videos
and discussion of "real life” issues in their organizations that will enable them to learn the skills needed to properly manage the scope of a project.
PROGRAMME SUMMARY
This programme covers the essential skills for managing project scope, gathering requirements, and meeting customers’ expectations that are necessary for effective delivery of projects.
PROGRAMME OUTLINE
|
DAY 1 -
INTRODUCTION TO PROJECT SCOPE
·
Defining common terminology for your organization and projects
·
Organizing project definition and scope across the project lifecycle
·
Steps in the requirements management process
·
Developing a scope management process for your organization’s projects
·
Identifying environmental issues, enterprise environment factors (EEFs) and organizational process assets (OPAs)
·
Fixed and evolving requirements
·
Identifying and deploying tools and techniques to overcome organizational barriers to successful scope definition, execution, and acceptance
·
Effective listening skills needed for requirements gathering and definition
·
Listening vs. hearing
·
Causes of people "tuning-out”
·
Communication Realities
·
Listening approaches
·
The Function of Listening
|
|
DAY 2 -
DEVELOPING THE BUSINESS CASE AND PROJECT CHARTER
·
Aligning your project with organizational objectives
·
Stakeholder identification and categorisation
o
Communication plan
o
Risk factors
·
Determining how to identify and prioritize stakeholders’ needs
·
Reconciling multiple views
o
Consideration of legal and market risks
o
Relationship management process
·
Handling difficult stakeholders
·
Determining the financial benefits of a project
·
Developing a business case for a project
·
Obtaining project acceptance from key stakeholders
|
|
DAY 3 -
PROJECT SCOPE PLANNING AND DEFINITION
·
Building a complete project scope statement
·
Creating a scope management plan
·
What is a requirement?
·
Constraints and assumptions
·
Project Boundaries
·
Converting stakeholders’ objectives into project requirements
·
Functional vs. non-functional requirements
·
What makes a "good” requirement?
·
Business requirements vs. technical requirements
·
Prioritizing requirements
·
Developing a WBS
o
WBS elements
o
WBS structures
o
WBS Template
o
Decomposition
o
Code of accounts
o
WBS dictionary
·
Using "Displayed Thinking”
·
Other tools
o
Activity Diagram
o
Block/Swimlane Workflow Diagram
o
Cause & Effect Diagram
o
Decision Tree Analysis
|
|
DAY 4 -
PROJECT SCOPE VALIDATION AND VERIFICATION
·
Embedding quality directly into the project
·
Incorporating quality throughout the project
·
Creating stable verification standards
·
Conducting peer reviews
·
Identifying scope testing and evaluation techniques
·
Conducting product verification and validation
·
Managing deliverables
·
Conduction inspections and testing
·
Accepting deliverables
·
Dealing with requested changes
·
Dealing with recommended corrective actions
|
|
DAY 5 -
PROJECT SCOPE CONTROL
·
Identifying and managing changes to the project scope
·
Establishing a formal authorization process for scope changes
·
Establish business criteria for change control
·
Managing the change control system
·
Addressing political and cultural issues regarding project scope changes
·
Performance reporting
·
Implementing approved change requests
·
Gathering and disseminating work performance information
·
Measuring and managing variance
·
Configuration management
·
Obtaining final product acceptance
·
Closing a project
|
