On this page
Short answer: many tools draw bars on a timeline. A real Gantt chart is a schedule: it knows how tasks depend on each other, which days are working days, and what moves when something slips. Test that, not the look.
What a Gantt chart must do beyond drawing bars
- Dependencies with lag. Finish-to-start is the common case, but you need start-to-start, finish-to-finish and start-to-finish too, plus lead and lag.
- Automatic rescheduling. Change one task and everything that depends on it moves.
- A working calendar. Weekends and holidays are respected, so a task that spans a weekend takes the right number of working days.
- Constraints. "Must finish on", "start no earlier than" and similar rules that the schedule honours.
- Baseline and critical path. You can save the original plan, compare it with the forecast, and see the chain of tasks that decides the finish date.
Three tests for any demo
Use your own plan, or a ten-task example, and do these live:
- Slip one task by a week. Do the dependent tasks move on their own? Does the project finish date change?
- Add a holiday. Does a task that spans it get longer?
- Ask for the critical path. Is it shown, with its length, and does it change when you slip a task?
If the vendor cannot do these in a minute each, it is a drawing tool.
A worked example
Take a small plan: Design (5 days) leads to Build (10 days) and Test (5 days), then Release.
- The chain is Design, Build, Test, Release, so those are on the critical path. A parallel task, "Write the user guide" (4 days, starting after Design), has float, because it finishes before Test does.
- Slip Design by three days. Build, Test and Release move by three days, the user guide moves too, and the finish date moves by three. The critical path is unchanged.
- Slip the user guide by two days. Nothing else moves, because it was off the critical path. That is the float at work.
- Add a holiday on a Wednesday of the Build week. Build gets one working day longer in calendar terms.
If a tool behaves this way without you touching the dependent tasks, it is scheduling.
Gantt with cost: a quick note on earned value
Dates alone do not tell you whether the project is healthy. Earned value compares what you planned to have done, what you actually did and what it cost: planned value, earned value, actual cost, and the indices CPI and SPI. A CPI below 1 means you are over budget for the work done, and an SPI below 1 means you are behind schedule. Look for a tool that computes these from the plan rather than asking you to enter them by hand.
How NUSK handles it
- Timeline. A Gantt view of every work item with a start and a due date, on a shared axis, with milestones plotted on it.
- Critical path. The longest chain of dependent items is highlighted, with its total length, calculated from the dependency register.
- Dependencies. Finish-to-start, start-to-start, finish-to-finish and start-to-finish links with lag.
- Calendar and constraints. A project working calendar with holidays, and scheduling constraints on items.
- Rescheduling. Dates that depend on a changed task are recalculated.
- Baseline. Snapshot every item's start and finish from the Gantt view, then track variance and critical-path length over time.
- Cost and earned value. Budgeted and actual cost per item, per-person cost rates and a live panel with PV, EV, AC, CPI, SPI, EAC, ETC, VAC and TCPI.
- Work breakdown structure. Any item can parent any other, with automatic WBS codes and a WBS dictionary of scope, acceptance criteria and owner for each work package.
- Round trip. Import a plan from MS Project XML, and export back to it.
- Beyond the chart. The same project can hold deliverables, milestones, a RAID register and agile work, and it feeds one health score.
When to stay on MS Project
If you need resource levelling, effort-driven scheduling and per-resource calendars at a large scale, a dedicated scheduling engine may serve you better. See our guide to Microsoft Project alternatives for how to decide.
Watch the demo · Import your plan
See it with your own project
Import a plan or a Jira project into a free NUSK workspace and judge it on your own data.