Plan projects with a Gantt chart: FS, SS, FF and SF dependencies with lag, milestones, drag-and-drop rescheduling, violation warnings and project report tabs.
More than a century after it was first used, the Gantt chart is still the most readable project planning tool there is. Horizontal bars show when each piece of work starts and ends; arrows between them show what is waiting on what. One screen gives you the timeline, the critical points and the risks.
But a Gantt chart is only as good as its setup. A plan with missing or wrong dependencies shows a hopeful guess, not reality. This article walks through dependency types, milestones, handling plan changes and the difference between sprints and projects, with practical examples.
What is a Gantt chart for?
List and kanban views answer "what is being done"; Gantt answers "when, and in what order". It is indispensable for:
- Projects lasting weeks or months with contributions from several teams
- Sequential processes where one step can't start until another finishes
- Delivery dates committed to a customer or to management
- Situations where you need to see in advance which work a delay will hit
The four dependency types
HibritİK's Gantt chart supports the four dependency types standard in project management:
| Type | Meaning | Example |
|---|---|---|
| FS (Finish-to-Start) | The successor can't start until the predecessor finishes. | Installation doesn't start before the contract is signed. |
| SS (Start-to-Start) | The successor can't start until the predecessor starts. | Validation starts once data migration starts. |
| FF (Finish-to-Finish) | The successor can't finish until the predecessor finishes. | Documentation can't be completed before development is. |
| SF (Start-to-Finish) | The successor can't finish until the predecessor starts. | The old shift can't end before the new shift begins. |
FS dominates in most projects. The other types model work that runs in parallel; SF is rarely needed.
Model waiting time with lag
Some work has a natural wait in between: concrete curing, a supplier's lead time, or the interval before an approval board meets. Adding lag to a dependency makes the successor start a set time after the predecessor. Writing that wait on the dependency, instead of inventing a dummy task, keeps the plan clean.
Milestones
A milestone has no duration but marks an important moment: design sign-off, pilot launch, customer delivery. Milestones give a clear answer to "where should we be by now" in management reports and team conversations alike. Putting one at the end of each major phase is a good starting rule.
When the plan changes
Drag and drop to reschedule
You can change a task's dates by dragging its bar on the Gantt chart. Reflecting a change agreed in a meeting right away is much faster than opening forms one by one.
Dependency violation warnings
If you move a task so that it breaks a dependency rule, HibritİK warns you and offers to reschedule the successors to fit the new dates. You don't have to work out the knock-on effect of a delay by hand, and the plan stays consistent.
To see how date changes affect individual workloads, read our workload analysis guide.
Sprint or project?
HibritİK has both projects and sprints, and they serve different needs:
- Project: a body of work with a defined goal, budget and end date, split into phases. Gantt planning and dependencies add the most value here.
- Sprint: a short, fixed-length work cycle whose scope is reset each time; kanban is the more natural way to follow it.
Many teams use both: the long-term roadmap is planned in a project with Gantt, and day-to-day delivery runs in sprints.
Tracking a project beyond the timeline
The schedule is only one dimension of a project. In HibritİK, the project detail has Overview, Risks, Lessons learned, Monitoring reports, Success criteria, Approval history and Files tabs. Logging risks while planning, writing monitoring reports regularly and recording lessons learned at the end make the next project's Gantt plan more realistic.
Using the Gantt chart in meetings
A Gantt chart is a communication tool as much as a planning tool. Running the weekly project meeting straight from the Gantt view, rather than from slides, means everyone is looking at the same live information. Start with upcoming milestones, then overdue tasks, then any dependency warnings. As decisions are made, dates are dragged into place, so the plan is already up to date when the meeting ends.
Team members may prefer to follow their own tasks in the list or calendar view; since every view uses the same data, nothing needs syncing.
Building a Gantt plan step by step
- Split the project into major phases and open a parent task for each.
- Break phases into subtasks with dates and assignees.
- Define dependencies with their type, adding lag for waiting periods.
- Place milestones at the end of each phase.
- Record risks in the project's Risks tab.
- Update the plan in the Gantt view at the weekly meeting and review any warnings.
Common mistakes
- No dependencies: placing bars by date alone hides the effect of delays.
- Making everything FS: work that could run in parallel gets queued and the project stretches.
- Set and forget: a Gantt chart stays trustworthy only if it is updated regularly.
- Milestone inflation: turning every task into a milestone makes the important moments ordinary.
Start planning with HibritİK
The Gantt chart is one of the views in HibritİK's task and project management module, sharing the same data as list, tree, kanban and calendar. Start your 14-day free trial to plan your own project, or get in touch with questions.