---

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)
  • Requirements Documentation (PMO-04.02.03)
• Optional / Contextual:
  • Product Vision (PMO-03.02)
  • Assumption Log (PMO-03.03)

2. Downstream Dependents

• Mandatory:
  • Work Breakdown Structure (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