This WBS Dictionary Software Development workbook provides the detailed definition for each of the 12 work packages in the ProjectAdm SaaS platform Work Breakdown Structure — the scope statements, deliverable descriptions, acceptance criteria, responsible teams, estimated effort, and schedule window for every WBS element from the MariaDB schema design to the production deployment, built by Eduardo Montes to eliminate scope ambiguity before Sprint 1 began.

What Is a WBS Dictionary?

A WBS Dictionary is a PMBOK 8 output in the Planning Performance Domain providing detailed information about each component in the WBS, including the work package's statement of work (SOW), deliverable description, acceptance criteria, assigned organizational unit, schedule milestones, required resources, cost estimates, quality requirements, contract information (if applicable), and technical references. The WBS Dictionary transforms the WBS from a visual decomposition diagram into a binding scope contract — each work package becomes an unambiguous commitment with defined boundaries, measurable outputs, and clear accountability. Without the WBS Dictionary, a WBS is just a hierarchy of labels; with it, every team member knows exactly what "in scope" and "out of scope" means for their assigned package.

What This WBS Dictionary Software Development Includes

The ProjectAdm WBS Dictionary workbook contains one master worksheet with a row for each of the 12 work packages:

• WBS Code and Name — Hierarchical code (e.g., 1.3.2 Core API) and descriptive name aligned with the WBS diagram
• Statement of Work — Narrative description of the work to be performed; boundaries (what is in scope and explicitly what is out of scope); deliverable format and medium
• Deliverables List — Specific tangible outputs (e.g., WP 1.3.2: REST API endpoints for 51 MariaDB tables, OpenAPI 3.0 specification, PHPUnit test suite with ≥ 80% coverage)
• Acceptance Criteria — Measurable conditions that must be met for the work package to be accepted by Henry Douglas; linked to the corresponding User Stories in the backlog
• Responsible Party — Primary (e.g., Marcus Webb for backend packages) and supporting team members; escalation path for scope questions
• Effort Estimate — Three-point estimate (optimistic/most likely/pessimistic) in story points and hours; PERT estimate; basis of estimate reference
• Schedule Window — Earliest start, latest finish, and target milestone gate (M1–M5) for each work package
• Change History — CR-001 through CR-004 impact on work package scope; ISS-002 impact on WP 1.3.2 effort estimate (increased by 320 hours)

How Eduardo Montes Used This WBS Dictionary Software Development

Eduardo Montes used the WBS Dictionary as the escalation reference whenever scope disputes arose. In Sprint 11, a disagreement emerged between Henry Douglas and Marcus Webb over whether OAuth 2.0 multi-provider support was in scope for WP 1.3.2 (Core API) or WP 1.4.1 (Authentication). Eduardo opened the WBS Dictionary: WP 1.3.2's SOW explicitly listed "OAuth 2.0 endpoints for Google and GitHub providers" while WP 1.4.1's SOW listed "login UI, session management, and password reset flow." The dispute was resolved in 10 minutes — the WBS Dictionary made the boundary unambiguous. CR-002 (Gantt chart, $4,500) required creating a new work package (WP 1.5.3 Gantt Visualization) with a full WBS Dictionary entry before the change was approved — ensuring the new scope was as rigorously defined as the original scope.

How to Use This WBS Dictionary Software Development Document

When building your own WBS Dictionary Software Development, write the "out of scope" section for each work package before you write the "in scope" section. Counterintuitive as it seems, defining what you are NOT doing eliminates the most common source of scope creep: unstated assumptions. The ProjectAdm WBS Dictionary's explicit "out of scope" entries prevented three potential scope creep incidents in the first 10 sprints — in each case, a stakeholder request was quickly resolved by pointing to the relevant "out of scope" clause and following the change control process.

Ready to create your own WBS dictionary? Download the blank WBS Dictionary Template (PMBOK 8).

• Download the WBS Dictionary Template — PMBOK 8 (blank, ready to use)
• Read the full guide: WBS Dictionary in PMBOK 8

Want to go deeper? The PMBOK Guide 8th Edition is the definitive reference for modern project management. Get your copy and use it alongside these examples to build a solid, practical understanding of every performance domain.

Format: Microsoft Excel (.xlsx) | Project: Software Development (SaaS Platform) | PMBOK Edition: 8th (2025) | Domain: Planning