**Background**  

I'm building a project Gantt, involving multiple teams. In the past I've had a good experience with a Gantt as a means of planning a project but not so much as a means of tracking a project's progress.

I'm trying to figure out what would be the best way to reflect the integration points and dependencies between teams and then track it as easily as possible.

**Current approach**  

Right now, what I have in mind is creating tasks for teams' activities and after each task that indicates a delivery to another team I creating a milestone, with the task as its predecessor. The receiving team's task depends on the milestone.

Example:  

```
==== [Team A develops]
   +-> * [Team A development complete]
       +-> ==== [Team B develops]

```

The downside of this approach is that the Gantt gets cluttered with a lot of milestones. The upside is that I get more control down the road around team delivery tracking and an easier way to filter the deliveries of each of the teams. Also, a side benefit is to avoid messing with weird task updates, splits, etc. I would ask for updates to estimated delivery dates.

I'd be happy to hear your thoughts and ideas around this issue. How would you approach this?
['https://pm.stackexchange.com/questions/2109', 'https://pm.stackexchange.com', 'https://pm.stackexchange.com/users/44/']
You do not need to use milestones to show the task relationships. In your schedule, once you have determined the sequence of work, based on BOTH hard and soft logic, link them. Link them using FS, SS, FF, with the appropriate leads and lags as appropriate. Baseline it and go. 

This should provide you with the control you need.
How about tracking deliveries between teams and as a separate list? This list would be managed by the program office. Each party would need to mutually agree upon what each delivery will contain and when it will be made. Once they sign up these agreements would be as binding as schedule milestones. This list would be used in addition to a master schedule - it does not replace a schedule.

The number and status of these hand-offs also makes a useful metric. The practice provides teams a way to ask for and get attention for things they need from one another.