The Gantt chart is a useful organizational tool, if not for actually keeping track of the project timeline. When creating the Gantt chart, you are forced to think about reasonable time estimates for the project tasks. It helps to break the tasks up as small as reasonably possible to ensure that team members have a clear idea of what they are doing. For example, if the product requires an app, the “programming” task is ambiguous. But if it is broken up into “program database on server; program app in Android Studio to obtain data; establish a bluetooth communication” it becomes clear what exactly the app needs programming-wise. The Gantt chart is a great way to have the team really think about the logistics of a project before investing resources into it.