This Work Breakdown Structure Software Development workbook presents the complete hierarchical decomposition of the ProjectAdm SaaS platform project scope into 12 work packages across 3 levels — the same WBS that Eduardo Montes used as the foundation for all cost estimates, schedule planning, resource assignments, and EVM calculations throughout 28 sprints and 13.5 months of development work on a $280,000 project.

What Is a Work Breakdown Structure?

A Work Breakdown Structure (WBS) is a PMBOK 8 output in the Planning Performance Domain that hierarchically decomposes the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables. The WBS is deliverable-oriented, not activity-oriented — each element represents a deliverable (a noun), not a task (a verb). The lowest-level elements are work packages: the units of scope small enough to be estimated, assigned, scheduled, monitored, and controlled. The WBS is the foundation of the scope baseline and the organizing structure for all other planning: costs roll up the WBS, resources are assigned at the work package level, and the EVM measurement system uses WBS codes to track Earned Value. A WBS that is not deliverable-oriented is not a WBS — it is an activity list in a hierarchy format.

What This Work Breakdown Structure Software Development Includes

The ProjectAdm WBS workbook contains two worksheets:

• WBS Hierarchy — Three-level outline format: Level 1 (Project: ProjectAdm SaaS Platform), Level 2 (5 major deliverable groups: Infrastructure, Application, Integration, Quality Assurance, Project Management), Level 3 (12 work packages); each element shows WBS Code, Name, Level, Parent, and Budget Allocation ($)
• Work Package Detail — For each of the 12 work packages: code, name, description, responsible team member, budget ($), percent of total budget, planned start, planned finish, milestone gate, and status at project close; CR-002 (Gantt) shown as WP 1.5.3 added in Sprint 8; CR-004 (WBS View) shown as WP 1.5.4 added in Sprint 14

The 12 work packages and their budget allocations: WP 1.1.1 Cloud Infrastructure ($18,500), WP 1.2.1 Database Schema ($14,200), WP 1.3.1 Authentication ($22,400), WP 1.3.2 Core API ($48,600), WP 1.3.3 Frontend Application ($41,300), WP 1.4.1 Integrations ($31,800), WP 1.5.1 Dashboard & Reporting ($24,700), WP 1.5.2 AI Assistant ($19,900), WP 1.5.3 Gantt Chart ($4,500, CR-002), WP 1.5.4 WBS View ($3,200, CR-004), WP 1.6.1 QA & Testing ($28,400), WP 1.7.1 Project Management ($22,500). Total: $280,000.

How Eduardo Montes Used This Work Breakdown Structure Software Development

Eduardo Montes built the WBS during Sprint 0 using a top-down decomposition approach, facilitated in a 3-hour workshop with Henry Douglas and the full team. The WBS served as the organizing framework for every other planning artifact: the Resource Requirements document assigned team members at the work package level; the Cost Baseline rolled up estimates from WBS leaf nodes; the Risk Register linked risks to the WBS packages they threatened (ISS-002 was linked to WP 1.2.1 Database Schema and WP 1.3.2 Core API); and the WBS Dictionary provided the detailed SOW for each work package. When CR-002 (Gantt chart) was approved, Eduardo added WP 1.5.3 to the WBS before any development began — maintaining the principle that nothing gets built unless it has a WBS code, a budget, and a defined deliverable.

How to Use This Work Breakdown Structure Software Development Document

When building your own Work Breakdown Structure Software Development, validate the 100% Rule at every level: the sum of the child elements must equal 100% of the parent's scope — no more, no less. Missing scope means unbudgeted work will appear later as a surprise; duplicated scope means two teams will do the same work or no team will because each assumes the other is responsible. The ProjectAdm team ran a 100% Rule check on each of the 5 Level-2 elements before finalizing the WBS — catching 2 scope gaps and 1 overlap that would have caused confusion in Sprint planning if left unresolved.

Ready to create your own WBS? Download the blank Work Breakdown Structure Template (PMBOK 8).

• Download the Work Breakdown Structure Template — PMBOK 8 (blank, ready to use)
• Read the full guide: Work Breakdown Structure 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