Purpose
The combined WBS & Dictionary Template provides a single, authoritative format for defining and describing the scope of Memorres projects. It ensures lean project teams (1–3 members) can both decompose the project into a hierarchical WBS and document the details of each work package in one place.
The WBS shows how project scope is structured into deliverables and work packages, while the Dictionary provides detailed descriptions, deliverables, acceptance criteria, dependencies, assumptions, ownership, and status. By merging these two into one template, lean PM teams reduce duplication, improve clarity, and maintain a single source of truth for planning, estimation, and resource allocation.
This template prevents scope gaps, overlaps, or misinterpretations. It creates traceability from requirements to deliverables, supports accountability through ownership assignments, and provides auditable evidence of scope baseline approval. Once approved, the WBS & Dictionary must be archived in MIC and serve as the foundation for estimation, scheduling, and monitoring.
Scope
This template applies to all projects managed by the Memorres Project Management Department and is mandatory during the Planning phase after scope approval. It must be completed before estimates, resource plans, and baseline schedules are created.
The scope of this template includes:
- Structuring project scope into hierarchical levels (WBS).
- Documenting detailed dictionary entries for each work package.
- Recording ownership, acceptance criteria, dependencies, and assumptions.
- Capturing approvals for the scope baseline.
It excludes detailed engineering task lists or technical design specifications, which belong to delivery teams. The Project Manager owns this template, stakeholders provide validation of specific work packages, and the Sponsor/PMO approve the final baseline.
Main Section
Table 1: Header Fields
| Field | Description | Example |
| Project Title | Name of the project | “Client Portal Modernization” |
| WBS Version | Version number | v1.0 |
| Prepared By | Project Manager | [PM Name] |
| Date | Date of preparation | 18-Sep-2025 |
| Approved By | Sponsor/PMO | [Sponsor Name] |
| Approval Date | Date of approval | 20-Sep-2025 |
Table 2: WBS & Dictionary Register
| WBS ID | Level | Parent ID | Title | Description | Deliverables | Acceptance Criteria | Dependencies | Assumptions | Owner | Status | Example |
| 1.0 | 1 | – | Client Portal Modernization | Entire project scope | Approved portal | Sponsor acceptance | None | Scope approved | Project Manager | Approved | Overall program |
| 1.1 | 2 | 1.0 | Requirements Baseline | Capture and validate requirements | Requirements Spec v1.0 | Signed-off by stakeholders | Depends on SME availability | Assumes SME time provided | PM | Approved | Req Spec signed 12-Sep-2025 |
| 1.2 | 2 | 1.0 | Portal Redesign | Redesign user interface | Approved UI mockups | Sponsor sign-off | Depends on requirements baseline | Assumes design tools available | Design Lead | In Progress | Wireframes in review |
| 1.2.1 | 3 | 1.2 | UI Wireframes | Develop module-level wireframes | Draft wireframes | Stakeholder approval | Requires validated requirements | Assumes timely SME review | Design Lead | In Progress | Wireframes submitted 17-Sep-2025 |
| 1.2.2 | 3 | 1.2 | Final UI Design | Deliver high-fidelity mockups | Final mockups | Sponsor sign-off | Depends on wireframes | Assumes no major scope change | Design Lead | Not Started | Planned for Oct 2025 |
| 1.3 | 2 | 1.0 | User Training | Develop training materials | Training docs & guides | SME validation | Depends on portal completion | Assumes SME feedback | Training Coordinator | Not Started | Planned for Q4 2025 |
Table 3: Approval Record
| Approver | Role | Signature/Date | Example |
| [Sponsor Name] | Project Sponsor | [Signed 20-Sep-2025] | CIO sign-off |
| [PM Name] | Project Manager | [Signed 18-Sep-2025] | PM signature |
Closing Note & Cross-References
The WBS & Dictionary Template ensures that project scope is both structured and described in a single document, reducing complexity for lean teams. By combining hierarchical breakdown with detailed descriptions, it provides the baseline for estimation, scheduling, resource allocation, and monitoring. Once signed-off, this register must be stored in MIC as the official scope baseline.