Gantt e PlantUML

O gráfico de Gantt é um gráfico de barras que mostra o cronograma de um projeto: cada tarefa é uma barra no eixo do tempo, com início, duração e dependências. Foi popularizado por Henry Gantt por volta de 1910 a 1915, embora o polonês Karol Adamiecki tenha criado uma ferramenta parecida, o harmonograma, em 1896. ^[4]

O PlantUML é uma ferramenta de código aberto que desenha diagramas a partir de texto. Em vez de arrastar barras num programa, você escreve o cronograma numa linguagem quase natural, em inglês, e o PlantUML calcula as datas e gera a imagem. ^{[2] [3] [5]}

A vantagem é tratar o cronograma como código: ele cabe no controle de versão, pode ser comparado entre versões e se recalcula sozinho quando uma duração muda.

O que é preciso

• Java, para rodar o PlantUML, que é distribuído como um arquivo plantuml.jar. ^{[6] [16]}
• Um lugar para escrever e ver o resultado: a extensão PlantUML do VS Code, o servidor on-line do próprio PlantUML ou a linha de comando (java -jar plantuml.jar projeto.puml). ^[7]
• O texto original também lista o Graphviz, que o PlantUML usa para desenhar vários tipos de diagrama UML, e a sintaxe Creole, que formata textos dentro dos diagramas. ^{[8] [9]}

Todos os exemplos deste tutorial foram testados no PlantUML 1.2026.8. O texto original foi escrito para a versão 1.2020.23; as diferenças encontradas estão indicadas ao longo do texto. ^[1]

Estrutura de um arquivo

Todo gráfico de Gantt fica entre @startgantt e @endgantt. Cada linha é uma frase no formato sujeito, verbo e complemento, e os nomes de tarefas e marcos vão entre colchetes. ^[2]

@startgantt
' comentário de uma linha
/' comentário de
   várias linhas '/
project starts 2026-10-05
[Levantamento] requires 5 days
@endgantt

Comentários começam com aspa simples (') ou ficam entre /' e '/; não aparecem no desenho. A figura abaixo mostra de onde vem cada parte de um gráfico.

Configurando o projeto

Estes comandos definem o gráfico como um todo. Vários deles, como title, footer, caption, legend e scale, são comuns a todos os diagramas do PlantUML. ^[10]

Duas observações de versão:

• O texto original cita printscale diary; o valor correto é daily. As escalas quarterly e yearly, e o comando zoom, vieram depois. ^[2]
• As versões recentes acrescentam à esquerda uma tabela com início, fim e duração de cada tarefa. Para escondê-la, use hide column start, hide column end e hide column duration, como nos exemplos deste tutorial.

O comando language muda o idioma do calendário, com o código ISO 639. Nos testes, funcionou em alemão (de), mas o português e o italiano ainda saem em inglês; por isso as figuras reais deste tutorial mostram meses e dias em inglês.

Calendário

O calendário diz quais dias contam como dias de trabalho e quais merecem destaque.

saturday are closed
sunday are closed
2026-10-12 is closed                      ' feriado
2026-10-12 is colored in Salmon
2026-10-19 to 2026-10-23 are colored in LightYellow
today is 2026-10-14 and is colored in #FFB703
[Desenvolvimento] requires 10 days
[Desenvolvimento] pauses on 2026-10-15
[Documentação] starts 2026-10-07
[Documentação] ends 2026-10-16

• Dias fechados (are closed, is closed) não contam para ninguém: uma tarefa de 10 dias se estende por cima deles. Com is opened, um dia fechado volta a ser útil, como um sábado de trabalho.
• Pausa (pauses on) vale só para uma tarefa. A diferença é semântica: o dia fechado indica que o projeto não trabalha naquela data; a pausa indica que aquela tarefa foi suspensa. O texto original escreve pause on na sintaxe, mas a forma aceita é pauses on, como no próprio exemplo dele.
• Dias coloridos (is colored in, are colored in) só destacam visualmente, sem mudar a contagem. Com are named, um intervalo recebe um nome, como [Férias].

As cores aceitam os nomes de cores do CSS, como LightYellow e Salmon, ou códigos hexadecimais, como #FFB703. ^[15]

Tarefas

Uma tarefa é criada ao ser citada pela primeira vez. Há dois jeitos de definir quando ela acontece:

• Dinâmica: só com a duração ([Protótipo] requires 8 days). O PlantUML a posiciona a partir do início do projeto e das dependências.
• Fixa: com datas de início e fim ([Treinamento] starts 2026-10-19 e [Treinamento] ends 2026-11-13).

O texto original usa o verbo lasts, que continua funcionando; a documentação atual prefere requires, que expressa o esforço necessário. ^[2]

project starts 2026-10-05
saturday are closed
sunday are closed
[Levantamento] requires 5 days
then [Protótipo] requires 8 days
then [Testes] requires 4 days
[Entrega] happens at [Testes]'s end

Outras propriedades da tarefa

Dependências e marcos

O ponto forte do PlantUML é posicionar tarefas pelas relações entre elas. Mudou uma duração, o cronograma inteiro se recalcula.

• [B] starts at [A]'s end: B começa quando A termina. Com with red bold link, a seta ganha cor e estilo (bold, dashed ou dotted).
• then [B] requires 3 days: atalho para “logo depois da tarefa anterior”.
• [A] -> [B]: outra forma curta de ligar duas tarefas.
• [B] starts 2 days after [A]'s end: com folga entre as duas.
• [M] happens at [A]'s end: um marco, um ponto no tempo, sem duração. Também pode ter data fixa: [M] happens 2026-10-30.
• [B] displays on same row as [A]: desenha B na mesma linha de A, para economizar espaço.

Recursos e separadores

Para dizer quem faz cada tarefa, use chaves com o nome e, se quiser, a porcentagem de dedicação. Abaixo do gráfico, o PlantUML mostra a carga de cada pessoa por dia.

-- Fase 1 --
[Análise] on {Ana} requires 5 days
[Análise] is 100% completed
-- Fase 2 --
[Código] on {Bruno} requires 8 days
[Código] starts at [Análise]'s end
[Código] is 40% completed
[Testes] on {Ana:50%} {Bruno:50%} requires 4 days
note bottom
  Ana e Bruno dividem
  o tempo dos testes
end note
[Testes] starts at [Código]'s end with red bold link
[Pronto] happens at [Testes]'s end

• Separadores (-- Nome --) dividem o gráfico em fases, setores ou grupos.
• Recursos (on {Ana:50%}) mostram a alocação; com hide resources names, os nomes somem das barras, e com {Ana} is off on 2026-10-20 a pessoa fica indisponível num dia.
• A nota fica abaixo da tarefa declarada logo antes dela.

Estilo e sprites

A aparência é definida num bloco <style>, parecido com CSS, ou com comandos skinparam. O bloco de estilo é a forma mais nova e recomendada. ^{[11] [12]}

<style>
ganttDiagram {
  task      { FontName Arial; FontSize 12; BackGroundColor #EFE3FA; LineColor #5B2A86 }
  milestone { FontSize 12; BackGroundColor #FFB703; LineColor #2B1B3D }
  note      { FontSize 11; BackGroundColor #FFF1C9; LineColor #B35300 }
}
footer { HorizontalAlignment right }
title  { FontSize 20; HorizontalAlignment center }
</style>
skinparam footerFontColor blue

FontStyle aceita bold, italic, monospaced, stroked e underlined.

Sprites e ícones

Um sprite é uma pequena imagem codificada em texto, declarada com sprite $nome [15x15/8z] … e usada com <$nome>. Os ícones do conjunto Open Iconic vêm prontos, com a forma <&check>. ^{[13] [14]}

Exemplo completo

O texto original termina com um exemplo que junta quase tudo. Abaixo, o resultado gerado pelo PlantUML atual a partir do código do autor, com as três linhas hide column acrescentadas.

@startgantt
hide column start
hide column end
hide column duration
<style>

  ganttDiagram {

  	task {
  		FontName Courrier
  		FontColor black
  		FontSize 12
  		FontStyle bold
  		BackGroundColor Blue
  		LineColor blue
  	}

  	milestone {
  		FontColor blue
  		FontSize 12
  		FontStyle italic
  		BackGroundColor gold
  		LineColor red
  	}

  	note {
  		FontColor DarkGreen
  		FontSize 10
  		LineColor lightgreen
        BackGroundColor orange\yellow
  	}

  }

  footer {
    HorizontalAlignment right
  }

  title {
    FontColor black
    FontSize 40
    FontStyle italic
    HorizontalAlignment center
  }

</style>

skinparam footerFontColor blue
skinparam footerFontSize 10
skinparam footerFontStyle italic
'skinparam titleBackgroundColor Aqua-CadetBlue
'skinparam titleBorderColor blue
'skinparam titleBorderRoundCorner 15
'skinparam titleBorderThickness 2

' sprites
sprite $printer [15x15/8z] NOtH3W0W208HxFz_kMAhj7lHWpa1XC716sz0Pq4MVPEWfBHIuxP3L6kbTcizR8tAhzaqFvXwvFfPEqm0

' Initialization
caption figure 1
title Projeto<$printer>\nEntrega SDS 001 <&check>
footer Giovani Perotto Mesquita\n18/01/2011 - 13:01
scale 1.5
hide footbox
'printscale weekly
project starts the 2021/01/01

' Day watching
'today is 2021/01/20 and is colored in Yellow
today is 14 days after start and is colored in Yellow

' Close Days
saturday are closed
sunday are closed
2021/01/01 is closed
2021/01/01 is colored in lightblue
2021/01/04 to 2021/01/08 are colored in coral

' Tasks and separators
-- Phase One --
[Prototype design] on {Alice} lasts 13 days
  [Prototype design] links to [[http://plantuml.com]]
'note bottom
'  memo1 ...
'  memo2 ...
'  explanations1 ...
'  explanations2 ...
'  <img:http://plantuml.com/logo3.png>
'end note
[Config prototype] on {Giovani} lasts 7 days
'note bottom
'  WiFi <&wifi>
'  |= |= table |= header |
'  | a | table | row |
'  |<#FF8080> red |<#80FF80> green |<#8080FF> blue |
'  <#yellow>| b | table | row |
'end note
-- Phase Two --
[QA prototype] on {Davi} lasts 9 days
[Test prototype] on {Camila:50}{Giovani:50} lasts 6 days
-- Phase Three --
[Deploy] lasts 1 day
'note bottom
'  Example of Tree
'  |_ First line
'  |_ **Bom(Model)**
'    |_ prop1
'    |_ prop2
'    |_ prop3
'  |_ Last line
'end note
[PD audict] lasts 10 days
[Trainning] on {Camila:50}{Maria:50} starts 2021/01/18
  [Trainning] ends 2021/02/12
  legend right
    This is a legend
  endlegend
-- Milestones --

' Tasks flow
[Config prototype] starts at [Prototype design]'s end with red bold link
[QA prototype] starts at [Prototype design]'s end with red bold link
[Test prototype] starts at [Config prototype]'s end with red bold link
  [Test prototype] starts at [QA prototype]'s end with red bold link
  [Test prototype] pauses on monday
[Deploy] starts at [Test prototype]'s end with red bold link
[PD audict] starts at [Deploy]'s end with red bold link

' Tasks progress
[Prototype design] is 70% completed
[Config prototype] is 0% completed
[QA prototype] is 23% completed
[Test prototype] is 0% completed
[Deploy] is 0% completed
[PD audict] is 0% completed
[Trainning] is 20% completed

' Milestones
[DevEnd] happens at [Prototype design]'s end
  [DevEnd] happens at [QA prototype]'s end
[ReadyDeploy] happens at [Test prototype]'s end
  [ReadyDeploy] displays on same row as [DevEnd]
[PDEnd] happens at [PD audict]'s end
[PDEnd] displays on same row as [ReadyDeploy]

' Colors
[Prototype design] is colored in Red/Red
[Config prototype] is colored in Red/Red
[QA prototype] is colored in Red/Red
[Test prototype] is colored in Red/Red
[Deploy] is colored in Red/Red
[PD audict] is colored in Red/Red
[DevEnd] is colored in White/Black
[ReadyDeploy] is colored in Gray/Black
@endgantt

No código, o bloco de estilo define fontes e cores; sprite e <&check> colocam ícones no título; o calendário fecha os fins de semana e o dia 1º de janeiro; as tarefas usam recursos, dependências com setas vermelhas, pausa às segundas e progresso; e os marcos ficam na mesma linha com displays on same row as.

Referência rápida

Revisão rápida

Tente responder antes de abrir cada pergunta.

Referências

1. Giovani Perotto Mesquita, “Building Gant diagrams with PlantUML”, GitHub, texto original deste tutorial, github.com/GiovaniPM/MyCourses/blob/master/PlantUML/Course Gant.md.
2. PlantUML, “Gantt Diagram”, acesso em 25/09/2026, plantuml.com/gantt-diagram.
3. PlantUML, site oficial, acesso em 25/09/2026, plantuml.com.
4. Wikipedia (em inglês), “Gantt chart”, acesso em 25/09/2026, en.wikipedia.org/wiki/Gantt_chart.
5. Wikipedia (em inglês), “PlantUML”, acesso em 25/09/2026, en.wikipedia.org/wiki/PlantUML.
6. PlantUML, “Download”, acesso em 25/09/2026, plantuml.com/download.
7. Visual Studio Marketplace, “PlantUML” (jebbs), acesso em 25/09/2026, marketplace.visualstudio.com/items?itemName=jebbs.plantuml.
8. Graphviz, site oficial, acesso em 25/09/2026, graphviz.org.
9. PlantUML, “Creole”, acesso em 25/09/2026, plantuml.com/creole.
10. PlantUML, “Common commands”, acesso em 25/09/2026, plantuml.com/commons.
11. PlantUML, “Skinparam”, acesso em 25/09/2026, plantuml.com/skinparam.
12. PlantUML, “Style (evolution)”, acesso em 25/09/2026, plantuml.com/style-evolution.
13. PlantUML, “Sprite”, acesso em 25/09/2026, plantuml.com/sprite.
14. PlantUML, “Open Iconic”, acesso em 25/09/2026, plantuml.com/openiconic.
15. W3C, CSS Color Module Level 4, “Named colors”, acesso em 25/09/2026, w3.org/TR/css-color-4/#named-colors.
16. PlantUML, repositório no GitHub, acesso em 25/09/2026, github.com/plantuml/plantuml.

Gantt and PlantUML

A Gantt chart is a bar chart that shows a project schedule: each task is a bar on the time axis, with start, duration and dependencies. It was popularized by Henry Gantt around 1910–1915, although the Pole Karol Adamiecki created a similar tool, the harmonogram, in 1896. ^[4]

PlantUML is an open-source tool that draws diagrams from text. Instead of dragging bars around in a program, you write the schedule in an almost natural English language, and PlantUML calculates the dates and generates the image. ^{[2] [3] [5]}

The advantage is treating the schedule as code: it fits in version control, can be compared between versions and recalculates itself when a duration changes.

What you need

• Java, to run PlantUML, which is distributed as a plantuml.jar file. ^{[6] [16]}
• A place to write and see the result: the PlantUML extension for VS Code, PlantUML’s own online server or the command line (java -jar plantuml.jar project.puml). ^[7]
• The original text also lists Graphviz, which PlantUML uses to draw several kinds of UML diagram, and the Creole syntax, which formats text inside diagrams. ^{[8] [9]}

Every example in this tutorial was tested on PlantUML 1.2026.8. The original text was written for version 1.2020.23; the differences found are pointed out along the way. ^[1]

Structure of a file

Every Gantt chart goes between @startgantt and @endgantt. Each line is a sentence in subject, verb and complement form, and task and milestone names go in square brackets. ^[2]

@startgantt
' single-line comment
/' multi-line
   comment '/
project starts 2026-10-05
[Requirements] requires 5 days
@endgantt

Comments start with a single quote (') or go between /' and '/; they do not appear in the drawing. The figure below shows where each part of a chart comes from.

Setting up the project

These commands define the chart as a whole. Several of them, such as title, footer, caption, legend and scale, are common to all PlantUML diagrams. ^[10]

Two version notes:

• The original text mentions printscale diary; the correct value is daily. The quarterly and yearly scales, and the zoom command, came later. ^[2]
• Recent versions add a table on the left with each task’s start, end and duration. To hide it, use hide column start, hide column end and hide column duration, as in this tutorial’s examples.

The language command changes the calendar language, using the ISO 639 code. In the tests it worked in German (de), but Portuguese and Italian still come out in English; that is why this tutorial’s real figures show months and days in English.

Calendar

The calendar says which days count as working days and which deserve highlighting.

saturday are closed
sunday are closed
2026-10-12 is closed                      ' holiday
2026-10-12 is colored in Salmon
2026-10-19 to 2026-10-23 are colored in LightYellow
today is 2026-10-14 and is colored in #FFB703
[Development] requires 10 days
[Development] pauses on 2026-10-15
[Documentation] starts 2026-10-07
[Documentation] ends 2026-10-16

• Closed days (are closed, is closed) do not count for anyone: a 10-day task stretches over them. With is opened, a closed day becomes a working day again, such as a working Saturday.
• Pause (pauses on) applies to one task only. The difference is semantic: a closed day means the project does not work that day; a pause means that task was suspended. The original text writes pause on in the syntax, but the accepted form is pauses on, as in its own example.
• Colored days (is colored in, are colored in) only highlight visually, without changing the count. With are named, a range gets a name, such as [Vacation].

Colors accept CSS color names, such as LightYellow and Salmon, or hexadecimal codes, such as #FFB703. ^[15]

Tasks

A task is created the first time it is mentioned. There are two ways to set when it happens:

• Dynamic: duration only ([Prototype] requires 8 days). PlantUML places it from the project start and the dependencies.
• Fixed: with start and end dates ([Training] starts 2026-10-19 and [Training] ends 2026-11-13).

The original text uses the verb lasts, which still works; the current documentation prefers requires, which expresses the effort needed. ^[2]

project starts 2026-10-05
saturday are closed
sunday are closed
[Requirements] requires 5 days
then [Prototype] requires 8 days
then [Testing] requires 4 days
[Delivery] happens at [Testing]'s end

Other task properties

Dependencies and milestones

PlantUML’s strength is placing tasks through their relations. Change one duration and the whole schedule recalculates.

• [B] starts at [A]'s end: B starts when A ends. With with red bold link, the arrow gets a color and a style (bold, dashed or dotted).
• then [B] requires 3 days: shortcut for “right after the previous task”.
• [A] -> [B]: another short way to link two tasks.
• [B] starts 2 days after [A]'s end: with a gap between the two.
• [M] happens at [A]'s end: a milestone, a point in time with no duration. It can also have a fixed date: [M] happens 2026-10-30.
• [B] displays on same row as [A]: draws B on the same row as A, to save space.

Resources and separators

To say who does each task, use curly braces with the name and, optionally, the allocation percentage. Below the chart, PlantUML shows each person’s load per day.

-- Phase 1 --
[Analysis] on {Ana} requires 5 days
[Analysis] is 100% completed
-- Phase 2 --
[Coding] on {Bruno} requires 8 days
[Coding] starts at [Analysis]'s end
[Coding] is 40% completed
[Testing] on {Ana:50%} {Bruno:50%} requires 4 days
note bottom
  Ana and Bruno split
  the testing time
end note
[Testing] starts at [Coding]'s end with red bold link
[Done] happens at [Testing]'s end

• Separators (-- Name --) split the chart into phases, departments or groups.
• Resources (on {Ana:50%}) show allocation; with hide resources names, names disappear from the bars, and with {Ana} is off on 2026-10-20 the person is unavailable on a given day.
• A note goes below the task declared right before it.

Style and sprites

Appearance is defined in a <style> block, similar to CSS, or with skinparam commands. The style block is the newer, recommended way. ^{[11] [12]}

<style>
ganttDiagram {
  task      { FontName Arial; FontSize 12; BackGroundColor #EFE3FA; LineColor #5B2A86 }
  milestone { FontSize 12; BackGroundColor #FFB703; LineColor #2B1B3D }
  note      { FontSize 11; BackGroundColor #FFF1C9; LineColor #B35300 }
}
footer { HorizontalAlignment right }
title  { FontSize 20; HorizontalAlignment center }
</style>
skinparam footerFontColor blue

FontStyle accepts bold, italic, monospaced, stroked and underlined.

Sprites and icons

A sprite is a small image encoded as text, declared with sprite $name [15x15/8z] … and used with <$name>. Icons from the Open Iconic set come ready to use, in the form <&check>. ^{[13] [14]}

Complete example

The original text ends with an example that brings almost everything together. Below is the output generated by the current PlantUML from the author’s code, with the three hide column lines added.

@startgantt
hide column start
hide column end
hide column duration
<style>

  ganttDiagram {

  	task {
  		FontName Courrier
  		FontColor black
  		FontSize 12
  		FontStyle bold
  		BackGroundColor Blue
  		LineColor blue
  	}

  	milestone {
  		FontColor blue
  		FontSize 12
  		FontStyle italic
  		BackGroundColor gold
  		LineColor red
  	}

  	note {
  		FontColor DarkGreen
  		FontSize 10
  		LineColor lightgreen
        BackGroundColor orange\yellow
  	}

  }

  footer {
    HorizontalAlignment right
  }

  title {
    FontColor black
    FontSize 40
    FontStyle italic
    HorizontalAlignment center
  }

</style>

skinparam footerFontColor blue
skinparam footerFontSize 10
skinparam footerFontStyle italic
'skinparam titleBackgroundColor Aqua-CadetBlue
'skinparam titleBorderColor blue
'skinparam titleBorderRoundCorner 15
'skinparam titleBorderThickness 2

' sprites
sprite $printer [15x15/8z] NOtH3W0W208HxFz_kMAhj7lHWpa1XC716sz0Pq4MVPEWfBHIuxP3L6kbTcizR8tAhzaqFvXwvFfPEqm0

' Initialization
caption figure 1
title Projeto<$printer>\nEntrega SDS 001 <&check>
footer Giovani Perotto Mesquita\n18/01/2011 - 13:01
scale 1.5
hide footbox
'printscale weekly
project starts the 2021/01/01

' Day watching
'today is 2021/01/20 and is colored in Yellow
today is 14 days after start and is colored in Yellow

' Close Days
saturday are closed
sunday are closed
2021/01/01 is closed
2021/01/01 is colored in lightblue
2021/01/04 to 2021/01/08 are colored in coral

' Tasks and separators
-- Phase One --
[Prototype design] on {Alice} lasts 13 days
  [Prototype design] links to [[http://plantuml.com]]
'note bottom
'  memo1 ...
'  memo2 ...
'  explanations1 ...
'  explanations2 ...
'  <img:http://plantuml.com/logo3.png>
'end note
[Config prototype] on {Giovani} lasts 7 days
'note bottom
'  WiFi <&wifi>
'  |= |= table |= header |
'  | a | table | row |
'  |<#FF8080> red |<#80FF80> green |<#8080FF> blue |
'  <#yellow>| b | table | row |
'end note
-- Phase Two --
[QA prototype] on {Davi} lasts 9 days
[Test prototype] on {Camila:50}{Giovani:50} lasts 6 days
-- Phase Three --
[Deploy] lasts 1 day
'note bottom
'  Example of Tree
'  |_ First line
'  |_ **Bom(Model)**
'    |_ prop1
'    |_ prop2
'    |_ prop3
'  |_ Last line
'end note
[PD audict] lasts 10 days
[Trainning] on {Camila:50}{Maria:50} starts 2021/01/18
  [Trainning] ends 2021/02/12
  legend right
    This is a legend
  endlegend
-- Milestones --

' Tasks flow
[Config prototype] starts at [Prototype design]'s end with red bold link
[QA prototype] starts at [Prototype design]'s end with red bold link
[Test prototype] starts at [Config prototype]'s end with red bold link
  [Test prototype] starts at [QA prototype]'s end with red bold link
  [Test prototype] pauses on monday
[Deploy] starts at [Test prototype]'s end with red bold link
[PD audict] starts at [Deploy]'s end with red bold link

' Tasks progress
[Prototype design] is 70% completed
[Config prototype] is 0% completed
[QA prototype] is 23% completed
[Test prototype] is 0% completed
[Deploy] is 0% completed
[PD audict] is 0% completed
[Trainning] is 20% completed

' Milestones
[DevEnd] happens at [Prototype design]'s end
  [DevEnd] happens at [QA prototype]'s end
[ReadyDeploy] happens at [Test prototype]'s end
  [ReadyDeploy] displays on same row as [DevEnd]
[PDEnd] happens at [PD audict]'s end
[PDEnd] displays on same row as [ReadyDeploy]

' Colors
[Prototype design] is colored in Red/Red
[Config prototype] is colored in Red/Red
[QA prototype] is colored in Red/Red
[Test prototype] is colored in Red/Red
[Deploy] is colored in Red/Red
[PD audict] is colored in Red/Red
[DevEnd] is colored in White/Black
[ReadyDeploy] is colored in Gray/Black
@endgantt

In the code, the style block sets fonts and colors; sprite and <&check> put icons in the title; the calendar closes weekends and January 1; the tasks use resources, dependencies with red arrows, a pause on Mondays and progress; and the milestones share a row with displays on same row as.

Quick reference

Quick review

Try to answer before opening each question.

References

1. Giovani Perotto Mesquita, “Building Gant diagrams with PlantUML”, GitHub, original text of this tutorial, github.com/GiovaniPM/MyCourses/blob/master/PlantUML/Course Gant.md.
2. PlantUML, “Gantt Diagram”, accessed 25 September 2026, plantuml.com/gantt-diagram.
3. PlantUML, official website, accessed 25 September 2026, plantuml.com.
4. Wikipedia, “Gantt chart”, accessed 25 September 2026, en.wikipedia.org/wiki/Gantt_chart.
5. Wikipedia, “PlantUML”, accessed 25 September 2026, en.wikipedia.org/wiki/PlantUML.
6. PlantUML, “Download”, accessed 25 September 2026, plantuml.com/download.
7. Visual Studio Marketplace, “PlantUML” (jebbs), accessed 25 September 2026, marketplace.visualstudio.com/items?itemName=jebbs.plantuml.
8. Graphviz, official website, accessed 25 September 2026, graphviz.org.
9. PlantUML, “Creole”, accessed 25 September 2026, plantuml.com/creole.
10. PlantUML, “Common commands”, accessed 25 September 2026, plantuml.com/commons.
11. PlantUML, “Skinparam”, accessed 25 September 2026, plantuml.com/skinparam.
12. PlantUML, “Style (evolution)”, accessed 25 September 2026, plantuml.com/style-evolution.
13. PlantUML, “Sprite”, accessed 25 September 2026, plantuml.com/sprite.
14. PlantUML, “Open Iconic”, accessed 25 September 2026, plantuml.com/openiconic.
15. W3C, CSS Color Module Level 4, “Named colors”, accessed 25 September 2026, w3.org/TR/css-color-4/#named-colors.
16. PlantUML, GitHub repository, accessed 25 September 2026, github.com/plantuml/plantuml.

Gantt e PlantUML

Il diagramma di Gantt è un grafico a barre che mostra il calendario di un progetto: ogni attività è una barra sull’asse del tempo, con inizio, durata e dipendenze. È stato reso popolare da Henry Gantt intorno al 1910–1915, anche se il polacco Karol Adamiecki aveva creato uno strumento simile, l’armonogramma, nel 1896. ^[4]

PlantUML è uno strumento open source che disegna diagrammi a partire da testo. Invece di trascinare barre in un programma, scrivi il calendario in un linguaggio quasi naturale, in inglese, e PlantUML calcola le date e genera l’immagine. ^{[2] [3] [5]}

Il vantaggio è trattare il calendario come codice: sta nel controllo di versione, si può confrontare tra versioni e si ricalcola da solo quando cambia una durata.

Cosa serve

• Java, per eseguire PlantUML, distribuito come file plantuml.jar. ^{[6] [16]}
• Un posto dove scrivere e vedere il risultato: l’estensione PlantUML di VS Code, il server online di PlantUML o la riga di comando (java -jar plantuml.jar progetto.puml). ^[7]
• Il testo originale elenca anche Graphviz, che PlantUML usa per disegnare diversi tipi di diagramma UML, e la sintassi Creole, che formatta il testo dentro i diagrammi. ^{[8] [9]}

Tutti gli esempi di questo tutorial sono stati verificati con PlantUML 1.2026.8. Il testo originale era stato scritto per la versione 1.2020.23; le differenze trovate sono indicate lungo il testo. ^[1]

Struttura di un file

Ogni diagramma di Gantt sta tra @startgantt e @endgantt. Ogni riga è una frase nella forma soggetto, verbo e complemento, e i nomi di attività e milestone vanno tra parentesi quadre. ^[2]

@startgantt
' commento su una riga
/' commento su
   più righe '/
project starts 2026-10-05
[Raccolta requisiti] requires 5 days
@endgantt

I commenti iniziano con un apice (') o stanno tra /' e '/; non compaiono nel disegno. La figura qui sotto mostra da dove viene ogni parte di un diagramma.

Configurare il progetto

Questi comandi definiscono il diagramma nel suo insieme. Diversi, come title, footer, caption, legend e scale, sono comuni a tutti i diagrammi di PlantUML. ^[10]

Due note di versione:

• Il testo originale cita printscale diary; il valore corretto è daily. Le scale quarterly e yearly, e il comando zoom, sono arrivati dopo. ^[2]
• Le versioni recenti aggiungono a sinistra una tabella con inizio, fine e durata di ogni attività. Per nasconderla usa hide column start, hide column end e hide column duration, come negli esempi di questo tutorial.

Il comando language cambia la lingua del calendario, con il codice ISO 639. Nelle prove ha funzionato in tedesco (de), ma portoghese e italiano escono ancora in inglese; per questo le figure reali di questo tutorial mostrano mesi e giorni in inglese.

Calendario

Il calendario dice quali giorni contano come lavorativi e quali meritano di essere evidenziati.

saturday are closed
sunday are closed
2026-10-12 is closed                      ' festivo
2026-10-12 is colored in Salmon
2026-10-19 to 2026-10-23 are colored in LightYellow
today is 2026-10-14 and is colored in #FFB703
[Sviluppo] requires 10 days
[Sviluppo] pauses on 2026-10-15
[Documentazione] starts 2026-10-07
[Documentazione] ends 2026-10-16

• I giorni chiusi (are closed, is closed) non contano per nessuno: un’attività di 10 giorni si allunga sopra di essi. Con is opened un giorno chiuso torna lavorativo, come un sabato di lavoro.
• La pausa (pauses on) vale per una sola attività. La differenza è semantica: il giorno chiuso indica che il progetto non lavora in quella data; la pausa indica che quell’attività è sospesa. Il testo originale scrive pause on nella sintassi, ma la forma accettata è pauses on, come nel suo stesso esempio.
• I giorni colorati (is colored in, are colored in) evidenziano solo visivamente, senza cambiare il conteggio. Con are named un intervallo riceve un nome, come [Ferie].

I colori accettano i nomi dei colori CSS, come LightYellow e Salmon, o codici esadecimali, come #FFB703. ^[15]

Attività

Un’attività viene creata la prima volta che la si nomina. Ci sono due modi di stabilire quando avviene:

• Dinamica: solo con la durata ([Prototipo] requires 8 days). PlantUML la posiziona a partire dall’inizio del progetto e dalle dipendenze.
• Fissa: con date di inizio e fine ([Formazione] starts 2026-10-19 e [Formazione] ends 2026-11-13).

Il testo originale usa il verbo lasts, che funziona ancora; la documentazione attuale preferisce requires, che esprime l’impegno necessario. ^[2]

project starts 2026-10-05
saturday are closed
sunday are closed
[Raccolta requisiti] requires 5 days
then [Prototipo] requires 8 days
then [Test] requires 4 days
[Consegna] happens at [Test]'s end

Altre proprietà dell’attività

Dipendenze e milestone

Il punto di forza di PlantUML è posizionare le attività in base alle loro relazioni. Cambia una durata e l’intero calendario si ricalcola.

• [B] starts at [A]'s end: B inizia quando finisce A. Con with red bold link la freccia prende un colore e uno stile (bold, dashed o dotted).
• then [B] requires 3 days: scorciatoia per “subito dopo l’attività precedente”.
• [A] -> [B]: un altro modo breve per collegare due attività.
• [B] starts 2 days after [A]'s end: con un margine tra le due.
• [M] happens at [A]'s end: una milestone, un punto nel tempo senza durata. Può anche avere una data fissa: [M] happens 2026-10-30.
• [B] displays on same row as [A]: disegna B sulla stessa riga di A, per risparmiare spazio.

Risorse e separatori

Per indicare chi svolge ogni attività usa le parentesi graffe con il nome e, se vuoi, la percentuale di impegno. Sotto il diagramma, PlantUML mostra il carico di ogni persona per giorno.

-- Fase 1 --
[Analisi] on {Ana} requires 5 days
[Analisi] is 100% completed
-- Fase 2 --
[Codice] on {Bruno} requires 8 days
[Codice] starts at [Analisi]'s end
[Codice] is 40% completed
[Test] on {Ana:50%} {Bruno:50%} requires 4 days
note bottom
  Ana e Bruno si dividono
  il tempo dei test
end note
[Test] starts at [Codice]'s end with red bold link
[Pronto] happens at [Test]'s end

• I separatori (-- Nome --) dividono il diagramma in fasi, reparti o gruppi.
• Le risorse (on {Ana:50%}) mostrano l’allocazione; con hide resources names i nomi spariscono dalle barre, e con {Ana} is off on 2026-10-20 la persona non è disponibile in un giorno.
• La nota va sotto l’attività dichiarata subito prima.

Stile e sprite

L’aspetto si definisce in un blocco <style>, simile al CSS, o con i comandi skinparam. Il blocco di stile è il modo più recente e consigliato. ^{[11] [12]}

<style>
ganttDiagram {
  task      { FontName Arial; FontSize 12; BackGroundColor #EFE3FA; LineColor #5B2A86 }
  milestone { FontSize 12; BackGroundColor #FFB703; LineColor #2B1B3D }
  note      { FontSize 11; BackGroundColor #FFF1C9; LineColor #B35300 }
}
footer { HorizontalAlignment right }
title  { FontSize 20; HorizontalAlignment center }
</style>
skinparam footerFontColor blue

FontStyle accetta bold, italic, monospaced, stroked e underlined.

Sprite e icone

Uno sprite è una piccola immagine codificata in testo, dichiarata con sprite $nome [15x15/8z] … e usata con <$nome>. Le icone del set Open Iconic sono già pronte, nella forma <&check>. ^{[13] [14]}

Esempio completo

Il testo originale si chiude con un esempio che riunisce quasi tutto. Qui sotto, il risultato generato dal PlantUML attuale a partire dal codice dell’autore, con le tre righe hide column aggiunte.

@startgantt
hide column start
hide column end
hide column duration
<style>

  ganttDiagram {

  	task {
  		FontName Courrier
  		FontColor black
  		FontSize 12
  		FontStyle bold
  		BackGroundColor Blue
  		LineColor blue
  	}

  	milestone {
  		FontColor blue
  		FontSize 12
  		FontStyle italic
  		BackGroundColor gold
  		LineColor red
  	}

  	note {
  		FontColor DarkGreen
  		FontSize 10
  		LineColor lightgreen
        BackGroundColor orange\yellow
  	}

  }

  footer {
    HorizontalAlignment right
  }

  title {
    FontColor black
    FontSize 40
    FontStyle italic
    HorizontalAlignment center
  }

</style>

skinparam footerFontColor blue
skinparam footerFontSize 10
skinparam footerFontStyle italic
'skinparam titleBackgroundColor Aqua-CadetBlue
'skinparam titleBorderColor blue
'skinparam titleBorderRoundCorner 15
'skinparam titleBorderThickness 2

' sprites
sprite $printer [15x15/8z] NOtH3W0W208HxFz_kMAhj7lHWpa1XC716sz0Pq4MVPEWfBHIuxP3L6kbTcizR8tAhzaqFvXwvFfPEqm0

' Initialization
caption figure 1
title Projeto<$printer>\nEntrega SDS 001 <&check>
footer Giovani Perotto Mesquita\n18/01/2011 - 13:01
scale 1.5
hide footbox
'printscale weekly
project starts the 2021/01/01

' Day watching
'today is 2021/01/20 and is colored in Yellow
today is 14 days after start and is colored in Yellow

' Close Days
saturday are closed
sunday are closed
2021/01/01 is closed
2021/01/01 is colored in lightblue
2021/01/04 to 2021/01/08 are colored in coral

' Tasks and separators
-- Phase One --
[Prototype design] on {Alice} lasts 13 days
  [Prototype design] links to [[http://plantuml.com]]
'note bottom
'  memo1 ...
'  memo2 ...
'  explanations1 ...
'  explanations2 ...
'  <img:http://plantuml.com/logo3.png>
'end note
[Config prototype] on {Giovani} lasts 7 days
'note bottom
'  WiFi <&wifi>
'  |= |= table |= header |
'  | a | table | row |
'  |<#FF8080> red |<#80FF80> green |<#8080FF> blue |
'  <#yellow>| b | table | row |
'end note
-- Phase Two --
[QA prototype] on {Davi} lasts 9 days
[Test prototype] on {Camila:50}{Giovani:50} lasts 6 days
-- Phase Three --
[Deploy] lasts 1 day
'note bottom
'  Example of Tree
'  |_ First line
'  |_ **Bom(Model)**
'    |_ prop1
'    |_ prop2
'    |_ prop3
'  |_ Last line
'end note
[PD audict] lasts 10 days
[Trainning] on {Camila:50}{Maria:50} starts 2021/01/18
  [Trainning] ends 2021/02/12
  legend right
    This is a legend
  endlegend
-- Milestones --

' Tasks flow
[Config prototype] starts at [Prototype design]'s end with red bold link
[QA prototype] starts at [Prototype design]'s end with red bold link
[Test prototype] starts at [Config prototype]'s end with red bold link
  [Test prototype] starts at [QA prototype]'s end with red bold link
  [Test prototype] pauses on monday
[Deploy] starts at [Test prototype]'s end with red bold link
[PD audict] starts at [Deploy]'s end with red bold link

' Tasks progress
[Prototype design] is 70% completed
[Config prototype] is 0% completed
[QA prototype] is 23% completed
[Test prototype] is 0% completed
[Deploy] is 0% completed
[PD audict] is 0% completed
[Trainning] is 20% completed

' Milestones
[DevEnd] happens at [Prototype design]'s end
  [DevEnd] happens at [QA prototype]'s end
[ReadyDeploy] happens at [Test prototype]'s end
  [ReadyDeploy] displays on same row as [DevEnd]
[PDEnd] happens at [PD audict]'s end
[PDEnd] displays on same row as [ReadyDeploy]

' Colors
[Prototype design] is colored in Red/Red
[Config prototype] is colored in Red/Red
[QA prototype] is colored in Red/Red
[Test prototype] is colored in Red/Red
[Deploy] is colored in Red/Red
[PD audict] is colored in Red/Red
[DevEnd] is colored in White/Black
[ReadyDeploy] is colored in Gray/Black
@endgantt

Nel codice, il blocco di stile definisce font e colori; sprite e <&check> mettono icone nel titolo; il calendario chiude i fine settimana e il 1º gennaio; le attività usano risorse, dipendenze con frecce rosse, una pausa il lunedì e l’avanzamento; e le milestone condividono una riga con displays on same row as.

Riferimento rapido

Ripasso veloce

Prova a rispondere prima di aprire ogni domanda.

Riferimenti

1. Giovani Perotto Mesquita, “Building Gant diagrams with PlantUML”, GitHub, testo originale di questo tutorial, github.com/GiovaniPM/MyCourses/blob/master/PlantUML/Course Gant.md.
2. PlantUML, “Gantt Diagram”, consultato il 25/09/2026, plantuml.com/gantt-diagram.
3. PlantUML, sito ufficiale, consultato il 25/09/2026, plantuml.com.
4. Wikipedia (in inglese), “Gantt chart”, consultato il 25/09/2026, en.wikipedia.org/wiki/Gantt_chart.
5. Wikipedia (in inglese), “PlantUML”, consultato il 25/09/2026, en.wikipedia.org/wiki/PlantUML.
6. PlantUML, “Download”, consultato il 25/09/2026, plantuml.com/download.
7. Visual Studio Marketplace, “PlantUML” (jebbs), consultato il 25/09/2026, marketplace.visualstudio.com/items?itemName=jebbs.plantuml.
8. Graphviz, sito ufficiale, consultato il 25/09/2026, graphviz.org.
9. PlantUML, “Creole”, consultato il 25/09/2026, plantuml.com/creole.
10. PlantUML, “Common commands”, consultato il 25/09/2026, plantuml.com/commons.
11. PlantUML, “Skinparam”, consultato il 25/09/2026, plantuml.com/skinparam.
12. PlantUML, “Style (evolution)”, consultato il 25/09/2026, plantuml.com/style-evolution.
13. PlantUML, “Sprite”, consultato il 25/09/2026, plantuml.com/sprite.
14. PlantUML, “Open Iconic”, consultato il 25/09/2026, plantuml.com/openiconic.
15. W3C, CSS Color Module Level 4, “Named colors”, consultato il 25/09/2026, w3.org/TR/css-color-4/#named-colors.
16. PlantUML, repository su GitHub, consultato il 25/09/2026, github.com/plantuml/plantuml.