Purpose
The purpose of this SOP is to provide a structured, repeatable process for developing the Work Breakdown Structure (WBS) and accompanying WBS Dictionary in Memorres projects. For lean PM teams (1–3 members), the WBS is the foundation of project planning, translating approved requirements and scope into manageable, traceable work packages. The WBS Dictionary supplements this by describing each element in detail, ensuring clarity across all stakeholders.
Without a WBS, projects risk fragmented planning, unclear responsibilities, and poor cost or effort tracking. This SOP mitigates those risks by defining how PMs should decompose project scope, structure deliverables, and validate completeness. The WBS acts as the backbone for estimation, scheduling, resource planning, and progress tracking.
The WBS Dictionary complements the structure by clarifying scope, deliverables, acceptance criteria, and ownership for each work package. This ensures traceability back to requirements, avoids duplication of effort, and provides auditable evidence for governance. Together, they prevent scope creep, facilitate accountability, and enable lean PM teams to control projects effectively.
Scope
This SOP applies to all projects managed under the Memorres Project Management Department and is mandatory during the Planning phase, following the approval of requirements and scope. It covers the decomposition of project deliverables into a hierarchical WBS, the preparation of a WBS Dictionary, and the validation of completeness and alignment.
The SOP excludes detailed engineering task breakdowns or technical solution design, which are delivery responsibilities. Instead, it focuses on governance and planning: ensuring that every requirement is captured in the WBS and that each work package is defined with clarity.
The Project Manager owns the creation and maintenance of the WBS and Dictionary. Sponsors approve the overall WBS, stakeholders validate their respective work packages, and the PMO ensures compliance with MIC standards.
Main Section
Table 1: RACI – WBS Development & Dictionary Activities
| Activity | Project Manager | Sponsor | Stakeholders | PMO | Example |
| Develop draft WBS | R | I | C | I | PM drafts WBS from scope |
| Validate coverage against requirements | R | I | A | C | SME checks deliverables covered |
| Prepare WBS Dictionary entries | R | I | C | I | PM documents work package details |
| Review and refine | R | C | A | I | Stakeholder confirms accuracy |
| Approve WBS & Dictionary | C | A | C | R | Sponsor signs baseline |
Table 2: Workflow – WBS Development & Dictionary
| Step | Inputs | PM Activities | Outputs | Gate Criteria | Example |
| 1 | Approved Scope Statement | Break scope into high-level deliverables | Draft WBS Level 1 | All scope elements represented | Portal redesign, integrations |
| 2 | Validated Requirements | Decompose deliverables into work packages | WBS Level 2–3 | No requirements unlinked | Onboarding workflow → module tasks |
| 3 | Draft WBS structure | Document work package details in Dictionary | Draft Dictionary entries | All work packages described | ID, owner, acceptance criteria included |
| 4 | Draft WBS + Dictionary | Circulate for stakeholder review | Reviewed WBS & Dictionary | Conflicts resolved | Duplicate packages removed |
| 5 | Reviewed WBS & Dictionary | Secure sponsor & PMO approval | Approved baseline | Sign-off recorded in MIC | WBS v1.0 approved 18-Sep-2025 |
Table 3: Quality Checklist
| Criterion | Test | Evidence | Example |
| Completeness | All requirements mapped to WBS | Traceability matrix | Req BR-001 mapped to WP-01 |
| Clarity | Each work package described unambiguously | WBS Dictionary entries | “User Training Material Development” |
| Uniqueness | No duplicate or overlapping work packages | Cross-check review | WP-02 and WP-03 distinct |
| Alignment | WBS aligns with Scope Statement and Charter | Document comparison | Scope v1.0 vs. WBS v1.0 |
| Approval | Sponsor sign-off documented | Signed baseline in MIC | Sponsor signed 18-Sep-2025 |
Closing Note & Cross-References
The WBS Development & Dictionary SOP ensures that Memorres projects translate scope into clear, manageable work packages with documented ownership and acceptance criteria. The WBS becomes the backbone for estimation, scheduling, and reporting, while the Dictionary ensures each element is unambiguous. Both must be approved, version-controlled, and archived in MIC before detailed planning proceeds.