Gantt Chart

Since 1910, when Gantt Chart was invented, it has undergone several crucial changes and still holds its position as project managers’ instrument of choice for illustrating the project schedule. Gantt Chart is one of Epicflow’s most used features. With its help you always know what tasks need to be taken care of at any point in time, who needs to work on these tasks, and what conditions need to be met to complete these tasks.

 

In Epicflow, Gantt Chart not only shows you the project schedule but lets you interact with your project, edit schedule, set dependencies, see detailed information about the user stories or milestones with one click. You can also edit stories and milestones, assign resource groups, leave comments, track progress, and see dependencies on the same screen without closing the Gantt Chart.

With phases that represent sprints and releases in a Gantt Chart, we support Jira users and enable using a Scrum approach in Epicflow.  Working with phases is intuitively easy. You can perform the following actions:

  • hide empty phases in a Gantt chart and make them visible when you add a task;
  • choose progress / in progress / completed options for phases;
  • drag the beginning and the end of any phase;
  • select multiple phases in the same way as choosing multiple milestones;
  • edit, create, delete, drag-and-drop, and filter data by phases;
  • monitor all phases-related information (sprints, releases, and backlogs) in a Gantt chart;
  • filter tasks display by selecting one of the following variants: “show all”, “selected by a date range”, and “last 14 days plus future”.

 

Gantt relationships between summary-tasks, tasks, and milestones:

  • Finish to Start (FS) – the default: The task cannot start before its predecessor ends, described above.
  • Start to Start (SS): The task cannot start until the predecessor starts, although it may start later. This can be useful if you have a task whose start date depends on the start date of another task.
  • Finish to Finish (FF): The task cannot end before the predecessor ends, although it may end later.
  • Start to Finish (SF): The task cannot end before the predecessor starts, although it may end later. This task relationship is rarely used.