I have a number of tasks which have 3 subtasks each that MUST start and be completed exactly 2 weeks from each other. (each subtask is half day) i.e. task1: (subtask1 @ day1, subtask2 @ day14, subtask3 @ day28)

The problem is that if I use lag, when I have many tasks (more than 200) and I level the resources, the subtasks2 of each task is pushed by the subtasks1 so they are scheduled more than 2 weeks from the linked subtask1)

I could use constraint but I need the tasks to float so if I change the starting day or the priority of the main tasks everything will be rescheduled maintaining a fixed 2 weeks delay of each subtask.

Any idea on how to do it?

Keep your lag values and then:

  • Option 1: If it is resource levelling that is causing the subtasks to be moved around, then set up a "special" resource that is only used on those subtasks. This means there will never be resource overloading and so the subtasks are never moved by Levelling. Of course, this does lead to a potential overloading of the actual resource because MS-Project will see them as different resources and will assign them on the same day as it will see no overloading

  • Option 2: Use Priorities. Set a higher priority on the subtasks than any other task where there could be a resource clash. Given they must occur on your strict timing, set them to the highest possible priority (999) and ensure that the 'Levelling Order' is 'Priority, Standard'. This means MS-Project will attempt to preserve their timing above all others and so the other clashing tasks, at a lower priority, will be moved first. This option would be my personal preference as there are no real downsides

  • Hi Marv, thank you fro your answer. I need to use leveling as the main tasks need to be scheduled by priority. It works of I use "level by ID", but if I do that, then I can level by priority. I use only one resource. Also if I level by priority or ID it will simply schedule the highest priority first but if there is a gap between high priority tasks it will put in there the first of the lower priority tasks and the second and third will be pushed at more than 2 weeks delay. – user2822225 Feb 7 '16 at 1:24
  • Ok I have tested, and I cannot find a way to push ST2 because of levelling effects from other tasks, though I am using a very simple project with few tasks. As far as I can tell ST2 would only be pushed if there was a higher priority task, which is why I suggested making all the subtasks the HIGHEST priority. I don't understand your comment- if you Level by ID then you cannot level by priority. I have linked a task and two subtasks using S-S relationship with lag of 10 days, Level by 'Priority, Standard' and 'Levelling can create splits...' and I cannot get them to move through levelling! – Marv Mills Feb 8 '16 at 9:09
  • ok, let me explain better... look at the picture attached. postimg.org/image/tp7cffsjv Let's say my team has a capability of completing 3 subtasks per week. Each task has it's own priority, some tasks will have the same priority. There will be new tasks that will be added to the plan at any time and their priority might be higher than the one already scheduled. Priorities could also change and if they do schedule should be recalculated for the non started tasks. – user2822225 Feb 9 '16 at 4:40
  • Either your subtasks MUST start on time, and therefore they must have the highest priority, or incoming tasks have an even higher priority- you cannot have it both ways. Saying a task may not be pushed by a higher priority task means it is not a higher priority task! If you cannot work with it you have only two options- use a different resource in the MSP for the unmovable tasks so Levelling does not try to resolve a clash, or don't use Levelling... – Marv Mills Feb 9 '16 at 9:12
  • Looking again, and thinking more about your needs, I am not sure Project is really the right tool for you. Project tries to actively manage and balance its list of tasks according to availability and priority. You might be able to force it to approximate what you need, by making ST1 a higher priority that ST2, and 2 higher than 3, all within a framework where Task1 (and its subtasks) are all higher priority than T2 and all its subtasks. But what's the point? By the time you have done that and tied it in knots you might as well do manual scheduling since you have removed all automation! – Marv Mills Feb 9 '16 at 10:22

Don't use the schedule leveling function. You don't need it.

Your Answer

 

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.