Work Breakdown Structure
Work breakdown. Useful for scoping a piece of delivery.
- Format.puml
- Length20 lines
- Diagramwbs
- Includesnone
The source
20 lines of PlantUML (wbs), and needs nothing beyond the bundled engine. Copy it, or open the template inside Gnomon and render it as it is.
@startwbs
title Work Breakdown Structure
* Project
** Phase 1: Planning
*** Define Scope
*** Identify Stakeholders
*** Create Timeline
** Phase 2: Execution
*** Task 1
**** Subtask 1.1
**** Subtask 1.2
*** Task 2
*** Task 3
** Phase 3: Closure
*** Documentation
*** Handover
@endwbsRender this offline
This template ships in Gnomon and renders on your machine, with no account and no diagram uploads. The browser editor is free and needs no install.
Others in UML and standard diagrams
- Sequence DiagramThe highest-value diagram in this list. Time runs down; participants across.
- Activity / Flow DiagramEarns its place when there are real branches and joins.
- Use Case DiagramActor-to-goal. Dated, but still the clearest way to show scope boundaries.
- Class DiagramBest used for a single bounded context, not a codebase.
- State DiagramForces the awkward questions about duplicate and out-of-order events.
- ER DiagramCardinality is the part people get wrong. Write it explicitly.
- Mind MapFor structuring thinking, not for documenting a system.
- Gantt ChartPlans, not architecture, but it renders from text, so it diffs in review.
- JSON VisualizationVisualises a JSON payload: handy in an API design review.