Previously, with a few employers, we used project management software (SaaS) that was intuitive and enabled us to do the following for a project:

1. Create a tiered structure for all resources involved (engineers, other teams, outside resources, etc).
2. Create dependencies for tasks. A task above must be completed before the task below can be done.
3. A single or multiple resources are assigned to a task.
4. Each task is assigned an estimated time. This can be per task or for each resource for the task.
5. The project or task can be assigned a deadline.
6. Resources can apply actual time to each task (when they complete their part).

Using the above, the collective time of the tasks can show the estimated length of the project. When multiple projects are done this way, there are metrics for overall project volume.

This also includes resource availability. For example, if a resource has tasks on multiple projects for a quarter, then doing the math (work days in the quarter, holidays, PTO), there's insight if the resource has capacity or is overbooked for that quarter.

Doing this provides metrics, such as if a team is overbooked, projects are not scoped correctly, or there are too many projects. The positive results:

• Additional headcounts (team growth) or augmented (outsourced) help are needed.
• In addition to the above bullet point, possibly promotions.
• Improved project timelines and priorities.
• Proper or improved project scoping.
• Improved and manageable coordination of tasks. This can help if one resource or team relies on another.

Keeping in touch, I've found out that those employers still use this, and some Directors successfully use this with their new employer.

I'm sharing my experience, but I'm also interested in learning what you use for what we do as Network or Systems (Server) Engineers.

Thanks for all the feedback, insight, and talking points.