PMBOK Scope Management

Overview

The PMBOK Scope Management skill supports the elaboration of documents for the Scope Management knowledge area — defining and controlling what is and what is not included in the project. It covers the complete scope management lifecycle: scope management plans that establish how scope will be defined, validated, and controlled; requirements documentation capturing business, stakeholder, and solution requirements; requirements traceability matrices linking each requirement from origin through testing; project scope statements with explicit deliverables and exclusions; Work Breakdown Structures (WBS) with accompanying dictionaries; and scope validation reports for formal deliverable acceptance.

Getting Started

Upload any existing project documents (charter, stakeholder interviews, prior scope documents) to the workspace and activate the PMBOK Scope Management skill. The agent will ask whether the project follows a predictive, agile, or hybrid approach — this shapes the decomposition depth and requirements format. For WBS creation, provide the project charter or high-level deliverables list; the agent decomposes into work packages with a numbered hierarchy and matching dictionary entries.

Example Conversation

Below is an example of a typical session creating a WBS for an ERP migration project. The agent decomposes the scope into work packages and produces matching dictionary entries.

You: I need a WBS for our SAP S/4HANA migration project. We’re migrating from SAP ECC 6.0. The major deliverables are: (1) current-state assessment, (2) system design & configuration, (3) data migration, (4) integration development, (5) testing, (6) training & change management, and (7) go-live & hypercare. Predictive approach.

Agent: I’ll decompose each major deliverable into work packages. Before I start, a few questions:

1. How many modules are in scope? (e.g., FI/CO, MM, SD, PP, HCM)
2. Are there custom ABAP developments in the current system that need to be assessed for migration?
3. Is data migration limited to master data and open transactions, or does it include historical data?

You: Modules: FI/CO, MM, SD, and PP. Yes, approximately 200 custom ABAP objects. Data migration includes master data, open transactions, and 3 years of historical data.

Agent: I’ve created the WBS with 7 Level-2 deliverables decomposed into 34 work packages. Here’s the structure:

• 1.0 SAP S/4HANA Migration
  • 1.1 Current-State Assessment — 5 work packages including legacy system inventory, custom code analysis (200 ABAP objects), data quality assessment, integration mapping, and gap analysis
  • 1.2 System Design & Configuration — 6 work packages per module (FI/CO, MM, SD, PP) plus cross-module configuration and authorization design
  • 1.3 Data Migration — 5 work packages covering extraction rules, cleansing & transformation, master data load, open transaction migration, and historical data migration (3 years)
  • 1.4 Integration Development — 4 work packages for API development, middleware configuration, custom code remediation, and integration testing
  • 1.5 Testing — 5 work packages: unit, integration, regression, performance, and UAT
  • 1.6 Training & Change Management — 5 work packages: training needs assessment, materials development, end-user training, super-user certification, and change communication
  • 1.7 Go-Live & Hypercare — 4 work packages: cutover rehearsal, production cutover, hypercare support, and project closure

Each work package has a corresponding WBS dictionary entry with description, responsible party, cost estimate placeholder, and acceptance criteria. The custom code analysis (1.1.2) flags the 200 ABAP objects — I’ve noted that a custom code analyzer report should feed into the remediation work package (1.4.3).

Document Excerpt

Below is a representative excerpt from a WBS with dictionary drafted with the skill.

Work Breakdown Structure — Excerpt

Project: SAP S/4HANA Migration WBS Numbering: 1.x.x (3 levels)

WBS Hierarchy (Partial)

1.0  SAP S/4HANA Migration
├── 1.1  Current-State Assessment
│   ├── 1.1.1  Legacy System Inventory
│   ├── 1.1.2  Custom Code Analysis
│   ├── 1.1.3  Data Quality Assessment
│   ├── 1.1.4  Integration Mapping
│   └── 1.1.5  Gap Analysis Report
├── 1.2  System Design & Configuration
│   ├── 1.2.1  FI/CO Module Configuration
│   ├── 1.2.2  MM Module Configuration
│   ├── 1.2.3  SD Module Configuration
│   ├── 1.2.4  PP Module Configuration
│   ├── 1.2.5  Cross-Module Configuration
│   └── 1.2.6  Authorization & Role Design
├── 1.3  Data Migration
│   ├── 1.3.1  Extraction Rules & Mapping
│   ├── 1.3.2  Data Cleansing & Transformation
│   ├── 1.3.3  Master Data Load
│   ├── 1.3.4  Open Transaction Migration
│   └── 1.3.5  Historical Data Migration
...

WBS Dictionary (Selected Entries)

This excerpt is illustrative. Final content must reflect the specific project’s scope, organizational structure, and decomposition level.