Complex projects fall apart in the gaps between tasks. Odoo's native project app gives you a task list, a kanban board and — on Enterprise — a read-mostly timeline, but it does not model the dependencies, slack and downstream ripple that a real schedule lives on. When one task slips, nothing recalculates. There is no critical path telling you which delays actually threaten the deadline, no saved baseline to prove how far you've drifted from the plan you committed to, and Community editions get no Gantt at all. Project managers end up exporting to a spreadsheet or a standalone tool, and the schedule stops being connected to the tasks, timesheets and resources that Odoo already holds.

Advanced Gantt for Projects is a build-to-order module that turns project.task into a live, dependency-aware schedule inside Odoo. We add a finish-to-start (and configurable FS/SS/FF/LF) dependency model on top of the existing task graph, then compute the critical path with a stored @api.depends compute so the longest chain to your milestone is always highlighted. Drag a bar to reschedule and the module cascades the move through successors while respecting your working calendar (resource.calendar), so a two-day slip on a predecessor visibly pushes everything downstream. Every reschedule is written back to real date_start / date_deadline fields — nothing is faked in a side table — so kanban, calendar, timesheets and reporting stay in sync.

Technically, the interactive timeline is an OWL component talking to the ORM over JSON-RPC, rendering bars, dependency arrows, milestone diamonds and a resource-allocation swimlane. Baselines are captured into a companion model (project.task.baseline) on demand, so you can overlay "planned vs actual" and see variance per task. Progress roll-up is a computed field aggregating child-task completion and logged hours. Access is enforced the Odoo way — ir.model.access.csv for the new models plus record rules that keep the Gantt scoped to a user's own projects and companies, honoring multi-company. We ship a QWeb PDF of the schedule and baseline variance for stakeholders who live outside Odoo, and optional automated actions to notify assignees when a drag-reschedule moves their task.

Because this is build-to-order, you are not downloading a generic module and hoping it fits. We start from a short scoping call, confirm your Odoo edition (Community or Enterprise), version (17.0 / 18.0 / 19.0) and the exact dependency rules, calendars and reporting you need, then build against your data model — including any custom fields already on project.task. Typical delivery is 2 to 4 weeks from confirmed scope. You get the installable source, a UAT pass on a staging copy of your database with a rollback plan, documentation, a training session and a post-go-live support window. ECOSIRE writes it, installs it and stands behind it.