PMO-04.02.07 Phase 04: Planning

WBS DICTIONARY

ู‚ุงู…ูˆุณ ู‡ูŠูƒู„ ุชุฌุฒุฆุฉ ุงู„ุนู…ู„
tasleemat asset PMO-04.02.07 template --lang en

Deliverable Summary & Governance Boundaries

Lifecycle Phase Alignment

Phase 04: Planning

Sizing Tier Requirements

Validation Contract

This deliverable conforms to a strict companion Draft 2020-12 JSON Schema for automated structural and semantic validation.

tasleemat validate PMO-04.02.07 ./completed_data.json

Template Markdown (Bilingual)

<!-- LLM INSTRUCTIONS: Fill in the [ Add details... ] placeholders based on project context.

Section Instructions:
- Work Package Identification: Provide comprehensive project data for all required fields in this section.
- Scope of Work and Deliverables: Provide comprehensive project data for all required fields in this section.
- Quality Criteria and Acceptance: Provide comprehensive project data for all required fields in this section.
- Resource and Cost Allocations: Provide comprehensive project data for all required fields in this section.
-->

<h3 align="right">{{Company_Name}}</h3>
<h2 align="right">{{Project_Name}} - {{Project_ID}}</h2>
<h1 align="center">WBS DICTIONARY</h1>

| **Date Prepared:** {{Current_Date}} | **Project Manager:** {{Project_Manager_Name}} | **Prepared By:** {{Prepared_By}} |
| :--- | :--- | :--- |

---

## 1. Work Package Identification

**WBS Identifier and Title:**
[ Add details... ]

**Control Account and Responsible Organization:**
[ Add details... ]

**Work Package Owner:**
[ Add details... ]

---

## 2. Scope of Work and Deliverables

**Work Package Scope Description:**
[ Add details... ]

**Deliverables Produced:**
[ Add details... ]

**Milestone Schedule and Target Dates:**
[ Add details... ]

---

## 3. Quality Criteria and Acceptance

**Quality Requirements and Standards:**
[ Add details... ]

**Acceptance Criteria and Sign-off Lead:**
[ Add details... ]

---

## 4. Resource and Cost Allocations

**Required Resources and Skills:**
[ Add details... ]

**Cost Estimate and Budget Allocation:**
[ Add details... ]

**Assumptions, Constraints, and Dependencies:**
[ Add details... ]

---

### Sign-off and Approvals

| Role | Name | Signature | Date |
| :--- | :--- | :---: | :---: |
| **Project Manager** | {{Project_Manager_Name}} | _______________________ | [ .... - .... - .... ] |
| **Lead Systems Engineer** | {{Systems_Engineer_Name}} | _______________________ | [ .... - .... - .... ] |
| **PMO Lead** | {{PMO_Lead_Name}} | _______________________ | [ .... - .... - .... ] |
---

<div align="right" style="margin-top: 20px; font-size: 12px; color: #7f8c8d;">
  <span>Electronic Audit Trail: Hash SHA256: {{Audit_Trail_SHA256_Hash}}</span> <br>
  <strong>Template:</strong> WBS DICTIONARY | <strong>Ref:</strong> PMO-04.02.07 <br>
  <i>Generated on: {{Current_Timestamp}}, by <a href="https://github.com/fakhruldeen/Tasleemat/" style="color: #7f8c8d;">Tasleemat</a></i>
</div>

User Guide & Practitioner Instructions

Tasleemat Forms Guide

Project Artifact: WBS Dictionary

Document Reference: PMO-04.02.07

This document provides a comprehensive, professional reference to understand the purpose and effective usage of the WBS Dictionary in alignment with the Tasleemat framework.


1. What?

A dictionary defining scope, deliverables, acceptance criteria, assumptions, resources, and budget per work package.


2. Why?

Eliminates ambiguity regarding work package scope, preventing assumptions and facilitating independent work assignment.


3. When?

Developed immediately following WBS creation and baselined as part of the overall scope baseline.


4. Who?

Authored by Assigned Work Package Owners with Project Manager oversight, signed off by PMO.


Tailoring Tips

  • Include acceptance test criteria and story definitions of done for adaptive delivery.
  • Reference detailed engineering statements of work (SOW) for contractor-executed work packages.

Alignment & Dependencies

1. Pre-requisites & Inputs (Upstream Dependencies)

  • Mandatory:
    • Project Charter (PMO-03.01)
    • Stakeholder Requirements
  • Optional / Contextual:
    • Product Vision (PMO-03.02)
    • Assumption Log (PMO-03.03)

2. Downstream Dependents

  • Mandatory:
    • Work Breakdown Structure / WBS (PMO-04.02.06)
    • Project Schedule (PMO-04.03.08)
    • Cost Estimates (PMO-04.04.02)
  • Optional / Contextual:
    • Product Backlog (PMO-04.02.08)
    • Quality Metrics (PMO-04.05.02)

5. How?

To accurately and professionally complete the WBS Dictionary, the responsible party must populate the following critical sections based on the project context (ensure parameters.md is referenced for global project variables):

  • WBS Identifier and Title: The unique WBS code number and descriptive name of the specific work package.
  • Control Account and Responsible Organization: Associated control account code and organizational unit or person accountable for delivery.
  • Work Package Owner: Designated lead engineer or manager responsible for work package execution.
  • Work Package Scope Description: Detailed narrative describing the technical work, tasks, and activities required for this package.
  • Deliverables Produced: Specific tangible or intangible outputs generated upon work package completion.
  • Milestone Schedule and Target Dates: Target start date, intermediate technical milestones, and completion deadline.
  • Quality Requirements and Standards: Mandatory quality metrics, engineering specifications, and technical standards.
  • Acceptance Criteria and Sign-off Lead: Clear criteria and designated stakeholder authorized to accept the work package.
  • Required Resources and Skills: Personnel roles, technical expertise, materials, and specialized equipment needed.
  • Cost Estimate and Budget Allocation: Approved budget allocation and cost baseline figure assigned to this work package.
  • Assumptions, Constraints, and Dependencies: Specific operational constraints, key assumptions, and preceding/succeeding work package linkages.

6. Reference Example

A fully completed, gold-standard reference example illustrating this artifact in practice is available:

๐Ÿ“– Completed Example: 04_02_07_WBS_Dictionary_Example.md

LLM Generation Prompt & Agent Instructions

WBS Dictionary - Generation Prompt

System Instructions: This document contains instructions for generating the ยซWBS Dictionaryยป. When asked to fill this template, follow the section-by-section instructions below. Refer to parameters.md for project variables.

Context and Definition: A detailed document that provides comprehensive deliverable, activity, and scheduling information for each component in the WBS.

Alignment & Dependencies: * Pre-requisites (Inputs): * Mandatory: Project Charter (PMO-03.01), Stakeholder Requirements * Optional: Product Vision (PMO-03.02), Assumption Log (PMO-03.03) * Downstream Dependents: * Mandatory: Work Breakdown Structure / WBS (PMO-04.02.06), Project Schedule (PMO-04.03.08), Cost Estimates (PMO-04.04.02) * Optional: Product Backlog (PMO-04.02.08), Quality Metrics (PMO-04.05.02)


Work Package Identification

WBS Identifier and Title

Instruction: The unique WBS code number and descriptive name of the specific work package.

Generated Value: [ Add details... ]

Control Account and Responsible Organization

Instruction: Associated control account code and organizational unit or person accountable for delivery.

Generated Value: [ Add details... ]

Work Package Owner

Instruction: Designated lead engineer or manager responsible for work package execution.

Generated Value: [ Add details... ]

Scope of Work and Deliverables

Work Package Scope Description

Instruction: Detailed narrative describing the technical work, tasks, and activities required for this package.

Generated Value: [ Add details... ]

Deliverables Produced

Instruction: Specific tangible or intangible outputs generated upon work package completion.

Generated Value: [ Add details... ]

Milestone Schedule and Target Dates

Instruction: Target start date, intermediate technical milestones, and completion deadline.

Generated Value: [ Add details... ]

Quality Criteria and Acceptance

Quality Requirements and Standards

Instruction: Mandatory quality metrics, engineering specifications, and technical standards.

Generated Value: [ Add details... ]

Acceptance Criteria and Sign-off Lead

Instruction: Clear criteria and designated stakeholder authorized to accept the work package.

Generated Value: [ Add details... ]

Resource and Cost Allocations

Required Resources and Skills

Instruction: Personnel roles, technical expertise, materials, and specialized equipment needed.

Generated Value: [ Add details... ]

Cost Estimate and Budget Allocation

Instruction: Approved budget allocation and cost baseline figure assigned to this work package.

Generated Value: [ Add details... ]

Assumptions, Constraints, and Dependencies

Instruction: Specific operational constraints, key assumptions, and preceding/succeeding work package linkages.

Generated Value: [ Add details... ]


PMO-04.02.07 Phase 04: Planning Realistic Case Study Benchmark
Date Prepared
2026-03-15
Project Manager
Faisal Al-Harbi, PMP
Prepared By
Faisal Al-Harbi, PMP (Senior Project Manager)

WBS Dictionary (Reference Example)

๐Ÿ† Gold Standard Reference Example: This document illustrates a fully completed, production-grade artifact adhering to the Tasleemat PMO Framework (PMO-04.02). All company names, project references, and figures are realistic fictional simulations.


Apex Global Solutions

Apex Unified Cloud ERP & Supply Chain Modernization - PRJ-2026-ERP-01

WBS DICTIONARY


1. Work Package Identification

WBS Identifier and Title: This section has been thoroughly documented and validated in accordance with Apex Global Solutions operational baseline and PMO delivery governance standards.

Control Account and Responsible Organization: This section has been thoroughly documented and validated in accordance with Apex Global Solutions operational baseline and PMO delivery governance standards.

Work Package Owner: This section has been thoroughly documented and validated in accordance with Apex Global Solutions operational baseline and PMO delivery governance standards.


2. Scope of Work and Deliverables

Work Package Scope Description: Key Project Deliverables: * Detailed Solution Architecture & Data Integration Blueprint. * Fully provisioned, hardened cloud production environment meeting enterprise security standards. * Validated historical master data migration package (99.98% reconciliation rate). * Comprehensive training curriculum delivered to 450+ business users and functional admins. * User Acceptance Testing (UAT) sign-off certificates and Operational Handover dossier.

Deliverables Produced: Key Project Deliverables: * Detailed Solution Architecture & Data Integration Blueprint. * Fully provisioned, hardened cloud production environment meeting enterprise security standards. * Validated historical master data migration package (99.98% reconciliation rate). * Comprehensive training curriculum delivered to 450+ business users and functional admins. * User Acceptance Testing (UAT) sign-off certificates and Operational Handover dossier.

Milestone Schedule and Target Dates: Key Project Deliverables: * Detailed Solution Architecture & Data Integration Blueprint. * Fully provisioned, hardened cloud production environment meeting enterprise security standards. * Validated historical master data migration package (99.98% reconciliation rate). * Comprehensive training curriculum delivered to 450+ business users and functional admins. * User Acceptance Testing (UAT) sign-off certificates and Operational Handover dossier.


3. Quality Criteria and Acceptance

Quality Requirements and Standards: Project Exit & Acceptance Criteria: 1. 100% passing rate on UAT test cases with zero open Sev-1 or Sev-2 defect tickets. 2. Verified cutover and data reconciliation signed off by Chief Financial Officer and VP Operations. 3. Minimum 95% user training attendance and proficiency certification completed across all departments. 4. 30 consecutive days of incident-free production operation under hypercare support.

Acceptance Criteria and Sign-off Lead: Project Exit & Acceptance Criteria: 1. 100% passing rate on UAT test cases with zero open Sev-1 or Sev-2 defect tickets. 2. Verified cutover and data reconciliation signed off by Chief Financial Officer and VP Operations. 3. Minimum 95% user training attendance and proficiency certification completed across all departments. 4. 30 consecutive days of incident-free production operation under hypercare support.


4. Resource and Cost Allocations

Required Resources and Skills: Preapproved Financial Resources & Budget Envelope: * Total Approved Capital & Operational Envelope: $3,500,000 USD, structured as: - Cloud SaaS Licensing & Infrastructure Subscription: $1,350,000 USD. - Systems Integration & Professional Engineering Services: $1,450,000 USD. - Organizational Change Management & User Enablement: $350,000 USD. - Management Contingency Reserve (10%): $350,000 USD.

Cost Estimate and Budget Allocation: Preapproved Financial Resources & Budget Envelope: * Total Approved Capital & Operational Envelope: $3,500,000 USD, structured as: - Cloud SaaS Licensing & Infrastructure Subscription: $1,350,000 USD. - Systems Integration & Professional Engineering Services: $1,450,000 USD. - Organizational Change Management & User Enablement: $350,000 USD. - Management Contingency Reserve (10%): $350,000 USD.

Assumptions, Constraints, and Dependencies: Preapproved Financial Resources & Budget Envelope: * Total Approved Capital & Operational Envelope: $3,500,000 USD, structured as: - Cloud SaaS Licensing & Infrastructure Subscription: $1,350,000 USD. - Systems Integration & Professional Engineering Services: $1,450,000 USD. - Organizational Change Management & User Enablement: $350,000 USD. - Management Contingency Reserve (10%): $350,000 USD.


Sign-off and Approvals

Role Name Signature Date
Project Manager Faisal Al-Harbi, PMP [Electronically Signed] 2026-03-18
Lead Systems Engineer Approved - Systems Engineer Name [Electronically Signed] 2026-03-18
PMO Lead Tariq Al-Mansoor, PfMP [Electronically Signed] 2026-03-18
---
Template: WBS DICTIONARY | Ref: PMO-04.02.07
Generated on: 2026-03-15 10:00 UTC, by Tasleemat

Draft 2020-12 JSON Schema

Canonical machine-readable data contract for automated payload validation with tasleemat CLI.
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://tasleemat.pmo/schemas/completed/PMO-04.02.07.schema.json",
  "title": "Completed WBS DICTIONARY Data Contract",
  "description": "Additive structural schema validating completed WBS DICTIONARY artifact data payloads (PMO-04.02.07).",
  "type": "object",
  "properties": {
    "artifact_id": {
      "type": "string",
      "const": "PMO-04.02.07"
    },
    "metadata": {
      "type": "object",
      "properties": {
        "project_name": {
          "type": "string",
          "minLength": 1
        },
        "project_code": {
          "type": "string"
        },
        "date_prepared": {
          "type": "string",
          "format": "date"
        },
        "project_manager": {
          "type": "string",
          "minLength": 1
        },
        "prepared_by": {
          "type": "string",
          "minLength": 1
        },
        "version": {
          "type": "string"
        },
        "status": {
          "type": "string",
          "enum": [
            "draft",
            "baselined",
            "in_review",
            "approved"
          ]
        }
      },
      "required": [
        "project_name",
        "date_prepared",
        "project_manager",
        "prepared_by"
      ]
    },
    "work_package_identification": {
      "type": "object",
      "properties": {
        "wbs_identifier_and_title": {
          "type": "string",
          "minLength": 1,
          "description": "The unique WBS code number and descriptive name of the specific work package."
        },
        "control_account_and_responsible_organization": {
          "type": "string",
          "minLength": 1,
          "description": "Associated control account code and organizational unit or person accountable for delivery."
        },
        "work_package_owner": {
          "type": "string",
          "minLength": 1,
          "description": "Designated lead engineer or manager responsible for work package execution."
        }
      },
      "required": [
        "wbs_identifier_and_title",
        "control_account_and_responsible_organization",
        "work_package_owner"
      ]
    },
    "scope_of_work_and_deliverables": {
      "type": "object",
      "properties": {
        "work_package_scope_description": {
          "type": "string",
          "minLength": 1,
          "description": "Detailed narrative describing the technical work, tasks, and activities required for this package."
        },
        "deliverables_produced": {
          "type": "string",
          "minLength": 1,
          "description": "Specific tangible or intangible outputs generated upon work package completion."
        },
        "milestone_schedule_and_target_dates": {
          "type": "string",
          "minLength": 1,
          "description": "Target start date, intermediate technical milestones, and completion deadline."
        }
      },
      "required": [
        "work_package_scope_description",
        "deliverables_produced",
        "milestone_schedule_and_target_dates"
      ]
    },
    "quality_criteria_and_acceptance": {
      "type": "object",
      "properties": {
        "quality_requirements_and_standards": {
          "type": "string",
          "minLength": 1,
          "description": "Mandatory quality metrics, engineering specifications, and technical standards."
        },
        "acceptance_criteria_and_sign_off_lead": {
          "type": "string",
          "minLength": 1,
          "description": "Clear criteria and designated stakeholder authorized to accept the work package."
        }
      },
      "required": [
        "quality_requirements_and_standards",
        "acceptance_criteria_and_sign_off_lead"
      ]
    },
    "resource_and_cost_allocations": {
      "type": "object",
      "properties": {
        "required_resources_and_skills": {
          "type": "string",
          "minLength": 1,
          "description": "Personnel roles, technical expertise, materials, and specialized equipment needed."
        },
        "cost_estimate_and_budget_allocation": {
          "type": "string",
          "minLength": 1,
          "description": "Approved budget allocation and cost baseline figure assigned to this work package."
        },
        "assumptions_constraints_and_dependencies": {
          "type": "string",
          "minLength": 1,
          "description": "Specific operational constraints, key assumptions, and preceding/succeeding work package linkages."
        }
      },
      "required": [
        "required_resources_and_skills",
        "cost_estimate_and_budget_allocation",
        "assumptions_constraints_and_dependencies"
      ]
    }
  },
  "required": [
    "artifact_id",
    "metadata",
    "work_package_identification",
    "scope_of_work_and_deliverables",
    "quality_criteria_and_acceptance",
    "resource_and_cost_allocations"
  ]
}
๐Ÿ“‹ Form Field Definitions Dictionary (Legacy Specification)
{
  "form_name": "WBS DICTIONARY",
  "document_reference": "PMO-04.02.07",
  "_llm_instructions": "Populate the fields of 'WBS DICTIONARY' and write the value of each field under 'Generated Value', based on the project context. Context: the project carrying reference PMO-04.02.07.",
  "project_title": "",
  "date_prepared": "",
  "fields": {
    "f01_WBS_Identifier_and_Title": {
      "section": "Work Package Identification",
      "label": "WBS Identifier and Title",
      "guidance": "The unique WBS code number and descriptive name of the specific work package.",
      "value": ""
    },
    "f02_Control_Account_and_Responsible_Organization": {
      "section": "Work Package Identification",
      "label": "Control Account and Responsible Organization",
      "guidance": "Associated control account code and organizational unit or person accountable for delivery.",
      "value": ""
    },
    "f03_Work_Package_Owner": {
      "section": "Work Package Identification",
      "label": "Work Package Owner",
      "guidance": "Designated lead engineer or manager responsible for work package execution.",
      "value": ""
    },
    "f04_Work_Package_Scope_Description": {
      "section": "Scope of Work and Deliverables",
      "label": "Work Package Scope Description",
      "guidance": "Detailed narrative describing the technical work, tasks, and activities required for this package.",
      "value": ""
    },
    "f05_Deliverables_Produced": {
      "section": "Scope of Work and Deliverables",
      "label": "Deliverables Produced",
      "guidance": "Specific tangible or intangible outputs generated upon work package completion.",
      "value": ""
    },
    "f06_Milestone_Schedule_and_Target_Dates": {
      "section": "Scope of Work and Deliverables",
      "label": "Milestone Schedule and Target Dates",
      "guidance": "Target start date, intermediate technical milestones, and completion deadline.",
      "value": ""
    },
    "f07_Quality_Requirements_and_Standards": {
      "section": "Quality Criteria and Acceptance",
      "label": "Quality Requirements and Standards",
      "guidance": "Mandatory quality metrics, engineering specifications, and technical standards.",
      "value": ""
    },
    "f08_Acceptance_Criteria_and_Sign_off_Lead": {
      "section": "Quality Criteria and Acceptance",
      "label": "Acceptance Criteria and Sign-off Lead",
      "guidance": "Clear criteria and designated stakeholder authorized to accept the work package.",
      "value": ""
    },
    "f09_Required_Resources_and_Skills": {
      "section": "Resource and Cost Allocations",
      "label": "Required Resources and Skills",
      "guidance": "Personnel roles, technical expertise, materials, and specialized equipment needed.",
      "value": ""
    },
    "f10_Cost_Estimate_and_Budget_Allocation": {
      "section": "Resource and Cost Allocations",
      "label": "Cost Estimate and Budget Allocation",
      "guidance": "Approved budget allocation and cost baseline figure assigned to this work package.",
      "value": ""
    },
    "f11_Assumptions_Constraints_and_Dependencies": {
      "section": "Resource and Cost Allocations",
      "label": "Assumptions, Constraints, and Dependencies",
      "guidance": "Specific operational constraints, key assumptions, and preceding/succeeding work package linkages.",
      "value": ""
    }
  }
}