How to run a two-week sprint on a timeline

Sprints and Gantt charts are usually treated as rivals. Here's a routine that uses both without doing the planning twice.

Scrum teams tend to avoid Gantt charts, and for a fair reason: a detailed long-range timeline fights with the idea of re-planning every two weeks. But a sprint is itself a two-week window on a timeline. Putting it there makes three things easier: seeing what spills over, seeing who is overloaded, and seeing how the sprint connects to the release.

Before planning: size the window, not the backlog. Start with capacity. Ten working days minus meetings, time off, and support rotation gives you real hours per person. On the Gantt that's a band two weeks wide with a row per person. Anything that doesn't fit the band doesn't go in the sprint.

During planning: drop tasks into the band. Pull from the backlog and place each task on its owner's row. Estimates become bar lengths, so overload is visible as overlap rather than as a number in a spreadsheet. If two bars stack for the same person on the same days, one of them moves.

Link only what actually blocks. Add a dependency when one task can't start until another is done, and nowhere else. Most sprints need three or four links, not thirty.

During the sprint: work on the board. The board is for daily flow. Cards move across In progress, In review, and Done while the bars fill in. Standup becomes a two-minute look at the Gantt: red bars are slipping, grey bars haven't started, and the green line is today.

At the end: let spillover roll. Unfinished work moves to the next sprint band with its history intact. Compare the band with the baseline you saved on day one — the gap is your most honest retro input.

• •Keep tasks under two days. Longer bars hide problems.
• •Put reviews and QA on the timeline as their own bars.
• •Save a baseline at the end of planning, every sprint.
• •Don't re-plan mid-sprint on the Gantt. Move cards on the board instead and let the dates update.

The goal isn't to replace sprints with a Gantt chart. It's to make the sprint visible in the same place as everything around it.