Staggered start / Rolling Schedule and Predecessors

[mark12010]

Staggered start / Rolling Schedule and Predecessors

I have a project to install software across 30 sites. The WBS is the same for each site so the plan would look something like this
Site1
Task1
Subtask 1.1
Subtask 1.2

Task2
Subtask 2.1
Subtask 2.2
Site2
Task1
Subtask 1.1
Subtask 1.2

Task2
Subtask 2.1
Subtask 2.2
ETC.

The plan is to break up the deployment into groups of 3 sites at a time
The one caveat is once any of the sites in the first block complete a certain task/subtask in the deployment, let’s say subtask 2, the first site on the second block will start. And so on.
That being said what parameters should I put in site 4 to say if either site 1, 2, or 3 reaches this point it can begin deployment.

 

[johnherman]

I don't think you're going to be able to handle this with simple constraints. You might be able to drive it by the resource requirements for each subtask. So of the cross-site identical subtasks has an assigned resource. Then, you want to make it Fixed Work effort driven, so that you're not driven by durations. You will need to keep up with work performed percentages. It may be possible by using Fixed Units as well, but I am not seeing how at this time. Another option might be to use VB scripting. It's not going to be a simple dependency and start/finish constraint.

==================================
adaptive uber info galaxies (bigger, better, faster than agile big data clouds)

 

[JulieInMaine]

I'm afraid there is no type of link in Project to handle your scenario of "whichever finishes first". It will require monitoring and updating both the plan and the resources. I don't know how long your deployments are but assuming they are a week plus, you as the PM should know which site will be finishing first. Project allows you to create models, but they still need care and feeding.