Forum Discussion
Multiple pilots under a single project
When you insert subprojects into a master, you will be able to see all the tasks in the subproject at master level. An engagement task in a subproject will not "start" anything in the master but you could create a link between a subproject task and a task in the master. For example, here is a simple subproject with a start engagement milestone. An external link is created which causes a start in the master. A similar process could be used for a finish milestone.
One easy way to make the external link is to select the desired task in the subproject and then while holding the mouse down drag to the desired task in the master. When the two tasks are widely separated, a quick filter can isolate the desired source (subproject) and destination (master) tasks.
A word of caution however, linked structures in Project (i.e. master/subprojects) are prone to corruption. Adding cross-project links (external predecessors/successors) "ups the ante" for corruption. For reference, with linked structures none of the files should ever be renamed, moved, overwritten or "saved off" to another location. Ideally, all files should reside in a single directory on a local drive and not be operated over a network. Linked structures do not work on SharePoint.
Hope this helps.
John
I have Online Desktop version 2202…
It is a compensation modelling project, piloting compensation options with 4 different vendors. So the main project is to pilot the options to arrive at a recommendation and there is a sub-project for each model that will be running simultaneously, but timeframes for activities will vary.
I want the timeframes from the sub-projects to roll-up into the main Pilot project.
Thanks for your help.
So your "pilots" are projects, each containing a set of tasks to accomplish an end result. You want to roll those into a master project which has a set of criteria or dates to be met. Does that sum it up? If so, then you can insert each subproject into your master via, Project > Insert group > Subproject. by default that will give you a dynamic master wherein changes in each subproject will be reflected in the master (i.e. dynamic linking). However a dynamic master with inserted subproject is prone to corruption so you might want to consider creating a static master which is a single file with all "pilots" included. In a static master each subproject is a separate summary group within the master (i.e. it's all one file) whereas in a dynamic master the master and each subproject are separate files.
How exactly do you want each pilot project to dovetail into the master (i.e. what is your end goal)?
John
- Hi John. Yes you have pretty much summed it up. What I want is that when 'Engagement' starts in the first pilot/subproject, I want it to generate a start in the main project. When Engagement finishes in whichever subproject finishes last, I want that to populate the 'Finish' date in the main project. I want that to occur for each of the common phases of the subprojects. I've googled, not finding what I am looking for.
When you insert subprojects into a master, you will be able to see all the tasks in the subproject at master level. An engagement task in a subproject will not "start" anything in the master but you could create a link between a subproject task and a task in the master. For example, here is a simple subproject with a start engagement milestone. An external link is created which causes a start in the master. A similar process could be used for a finish milestone.
One easy way to make the external link is to select the desired task in the subproject and then while holding the mouse down drag to the desired task in the master. When the two tasks are widely separated, a quick filter can isolate the desired source (subproject) and destination (master) tasks.
A word of caution however, linked structures in Project (i.e. master/subprojects) are prone to corruption. Adding cross-project links (external predecessors/successors) "ups the ante" for corruption. For reference, with linked structures none of the files should ever be renamed, moved, overwritten or "saved off" to another location. Ideally, all files should reside in a single directory on a local drive and not be operated over a network. Linked structures do not work on SharePoint.
Hope this helps.
John
- Thanks. That helps. I may have to reconsider how I've set things up. Thanks again for your help.
