Project Scope Management in IT Project Management
Project Scope Management
Information Technology Project Management, Chapter 5
Review
Components of Project Management
Stakeholders
Scope Management
10 Knowledge Areas:
Schedule Management
Cost Management
Quality Management
Project Integration Management
Resource Management
Communication Management
Risk Management
Procurement Management
Stakeholder Management
Project Success Factors
Needs and expectations from Projects, often influencing scope definitions and stakeholder satisfaction.
Project Management Framework
Illustrated in FIGURE 1-2, encompasses various aspects leading to project success, including processes, tools, and techniques applied across the project life cycle.
What is Project Scope Management?
Scope Definition:
Refers to all the work involved in creating the products of the project and the processes used to create them. This includes specific features, functions, and characteristics of the product, service, or result, as well as the activities necessary to deliver these components to meet project objectives.
Deliverable:
A unique and verifiable product, result, or capability produced as part of a project. Deliverables can be tangible items (e.g., hardware components, software modules, written reports, planning documents) or intangible outcomes (e.g., improved processes, meeting minutes, training completion).
Project Scope Management:
Involves the processes for defining and controlling what is included in a project and what is not. Its primary goal is to ensure that the project team performs all the work required, and only the work required, to complete the project successfully. This establishes a mutual understanding between stakeholders and the project team regarding deliverables and processes, preventing misunderstandings and ensuring alignment with project goals.
Project Scope Management Processes
Main Processes:
Planning Scope Management
Collecting Requirements
Defining Scope
Creating the Work Breakdown Structure (WBS)
Validating Scope
Controlling Scope
Plan Scope Management
Outputs of the Plan Scope Management Process:
Scope Management Plan:
A component of the project management plan that describes how the project scope will be defined, developed, monitored, controlled, and verified. It includes:
A detailed statement of project scope, often serving as a baseline.
The Work Breakdown Structure (WBS) approach, specifying how the WBS will be structured (e.g., top-down, bottom-up) and decomposed.
Maintenance and approval of the WBS, outlining who is responsible for updates and how changes are approved to ensure its integrity.
Formal acceptance of completed project deliverables, detailing the process and criteria by which stakeholders or the customer will acknowledge that project outputs meet their requirements.
Control requests for changes to scope, describing the procedures for submitting, reviewing, approving, and managing changes to the project scope through an integrated change control system.
Requirements Management Plan:
A component of the project management plan that describes how project requirements will be analyzed, documented, and managed. It outlines:
How to plan, track, and report requirement activities, using specific tools or metrics.
Details configuration management activities related to requirements, such as how changes to requirements will be approved and communicated.
Describes how to prioritize requirements (e.g., using MoSCoW method, business value, urgency) to ensure focus on the most critical elements.
Includes methods for utilizing product metrics to measure and evaluate the quality and completeness of requirements.
Provides a framework to trace and capture requirements' attributes (e.g., source, status, stability, justification, priority, acceptance criteria) for clearer understanding and impact analysis.
Collect Requirements
Challenges in Requirements Collection:
Complexity often arises, particularly in software development projects, due to factors such as conflicting stakeholder expectations, unclear business needs, hidden requirements, or rapidly changing environments.
Techniques for Collecting Requirements:
Interviewing stakeholders: Direct conversations with individuals to elicit detailed information and uncover specific needs.
Holding focus groups and facilitated workshops: Bringing together cross-functional stakeholders to define requirements, resolve conflicts, and reach consensus in a collaborative setting.
Utilizing group creativity and decision-making techniques: Methods like brainstorming, nominal group technique, or Delphi technique to generate and evaluate ideas for requirements.
Employing questionnaires and surveys: Efficiently gathering input from a large number of stakeholders, often when face-to-face interaction is impractical.
Conducting observational studies: Watching individuals perform their work to identify implicit requirements or process inefficiencies.
Generating ideas through benchmarking: Comparing project practices or product characteristics to those of other organizations or projects to identify best practices and potential improvements.
Defining Scope
Key Elements of a Project Scope Statement:
Provides a detailed description of the project and product, including:
Description of product scope: Features, functions, and characteristics of the product, service, or result.
User acceptance criteria for the product: Measurable and verifiable conditions that must be met for the deliverable to be formally accepted.
Detailed information on all project deliverables: A comprehensive list of all outputs, along with their associated attributes and quality standards.
Additional Documentation:
Project boundaries, constraints (e.g., budget, schedule, resources), and assumptions (e.g., availability of personnel, technology readiness) should be noted.
Supporting documentation references (e.g., product specifications, organizational process assets) are often included to provide additional context.
Scope Clarity Over Time:
Generally, as the project progresses, its scope increasingly clarifies and becomes more specific through a process known as progressive elaboration, iterating from high-level understanding to detailed specifications.
Creating the Work Breakdown Structure (WBS)
Definition:
A deliverable-oriented hierarchical decomposition of the work involved in a project, breaking it down into smaller, more manageable components.
Purpose and Importance:
Serves as the foundational document for planning and managing project schedules, costs, resources, and changes. It helps to organize and define the total scope of the project, making complex projects more digestible.
Process of Decomposition:
Involves subdividing project deliverables into smaller, more elementary components, adhering to principles like the 100% rule (the WBS includes all work for the project) and ensuring elements are mutually exclusive.
Work Package:
The smallest unit of work in the WBS, representing a task at the lowest level that can be realistically and confidently estimated, assigned to a specific individual or team, and monitored for progress.
Work Breakdown Structure Example
Illustration in FIGURE 5-3:
Displays a sample intranet WBS organized by multiple product levels, with detailed tasks at each level illustrating its hierarchical structure and components. This example typically shows how a project is broken down into major phases, then into deliverables, and finally into work packages.
WBS in Project Management Workflow
Inclusion in Gantt Chart:
The WBS is integrated into Gantt charts, where each work package corresponds to a specific task or set of tasks, visually depicting project timelines, dependencies, and progress.
Task Management:
Breaks down tasks according to project phases:
Initiating phase activities (e.g., project charter development, stakeholder identification)
Planning phase activities (e.g., developing the scope statement, creating the WBS, activity definition, resource planning)
Executing, Monitoring and Controlling, and Closing phases are also structured with specific WBS elements to manage and oversee all project work.
Validating Scope
Definition:
Scope validation is the process for formal acceptance of completed project deliverables by the customer or stakeholders. This involves reviewing the deliverables with the customer to ensure they meet requirements and obtaining formal sign-off. It is distinct from quality control, which focuses on the correctness of deliverables.
Scope Creep:
Many IT projects struggle with scope creep, which refers to unauthorized, uncontrolled changes or continuous expansion in project scope without proper adjustment to time, cost, and resources. This can lead to budget overruns, schedule delays, resource strain, and reduced project quality or abandonment.
Controlling Scope
Purpose of Scope Control:
Involves managing changes to project scope, ensuring alignment with project goals and business strategy, and preventing scope creep. Its main purpose is to ensure that all changes are processed through the integrated change control system and that actual scope remains consistent with the baselined scope.
Goals of Scope Control:
Influence factors leading to scope changes (e.g., proactive identification of potential causes, clear communication).
Process changes according to established integrated change control procedures, ensuring all proposed changes are documented, assessed, approved, or rejected.
Actively manage changes when they occur, implementing approved changes and updating project plans accordingly.
Variance:
Defined as the difference between planned and actual performance (e.g., planned scope versus actual delivered scope). Monitoring variance is critical for early detection of deviations from the scope baseline, allowing project managers to take corrective actions and maintain project success.