Structure - Resource Leveling Optimization to finish features

[jllabelle]

I have my structure grouped by feature, with multiple people working on each feature from multiple departments, and about 100 features tracked. I want to organize my planning as to only start work on a feature when everyone is available to work on it, having people focus on other work if not everyone needed is available.

e.g. Feature 25: needs person 2 and 4, but person 4 is still on feature 12, so have person 2 work on Feature 56 instead, since only person 2 is needed on that one.

I've tried both scenarios setting up Start-to-Start or Finish-to-Finish dependencies for each feature, but when running Resource Leveling, it would leave unexplainable gaps for  some people, in places where they could work on something else...

Any tips on how to achieve this? Any other way than using FF or SS dependencies?

Thanks.

[Stepan Kholodov _Tempo_ · Accepted solution]

Hello @jllabelle 

Please note: resource leveling is not designed as a scheduling tool. Its main purpose is to resolve the overallocation of tasks, delaying some of each resource's tasks to the nearest time when the resource can work on them without being overloaded. So, it can be normal that there are gaps on the timeline after resource leveling is finished (it can also depend on the configuration of both resource leveling, and the chart).

If your goal is to define when the work should happen, for which resources, and in what way, then using the manual scheduling and/or dependencies can give you the right result.

I hope this helps. If you have more questions about Structure/Gantt Charts, please reach out to us directly at our support portal.

Best regards,
Stepan
Tempo (the Structure app vendor)