Task

Each task gets a bar on the chart. Name it in terms the team uses, such as "Design," "Build," or "Taste-testing photos," so people can identify the work during a schedule discussion.

Choose the level of detail for the people reading the chart. A meeting about launch dates may only need one "Design" bar, even if design contains forty tickets. For a short project, about five to twelve tasks is a useful starting point; keep the individual tickets in the issue tracker unless the schedule needs that detail.

Give each task a duration and record its dependencies. An agreed deliverable helps the team check when it's complete. If the task is hard to describe or estimate, consider splitting it.