Gantt Chart

Plans, not architecture, but it renders from text, so it diffs in review.

• Format.puml
• Length20 lines
• Diagramgantt
• Includesnone

The source

20 lines of PlantUML (gantt), and needs nothing beyond the bundled engine. Copy it, or open the template inside Gnomon and render it as it is.

@startgantt

title Project Timeline

Project starts 2024-01-01

[Planning] lasts 10 days
[Design] lasts 15 days
[Design] starts at [Planning]'s end

[Development] lasts 30 days
[Development] starts at [Design]'s end

[Testing] lasts 15 days
[Testing] starts at [Development]'s end

[Deployment] lasts 5 days
[Deployment] starts at [Testing]'s end

@endgantt

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.
• JSON VisualizationVisualises a JSON payload: handy in an API design review.
• Work Breakdown StructureWork breakdown. Useful for scoping a piece of delivery.