I’m part of a fair size team where the ideal is a division of workloads based on individual skills to be able to preform isolated tasks so from a management standpoint scene management would be no different than say a large VFX project being done in a 3d app like 3ds Max.
The small details are best left to micro management by agreement and solve problems when they occur rather than trying to anticipate the problems at the start and inject obstacles that adds unnecessary time and additional work loads to service unnecessary requirements. In other words just get started and fix as you go along and over time the work flow will smooth out.
After that where and how the pipeline functions determines how the structure needs to be laid out from the start based on the type of network being used. Demands from a local network set up compounds if the project is Internet based project for example and the simple things like storage capacity, the lack of, would stop a project in it’s tracks considering the need to maintain source chains as part of the iteration process.
Could write a book but the best suggestion I could give at the moment is to sit down and plan things out, using white boarding, based on the type of network pipeline and current available resources thinking in terms of how it all needs to work five years from now and not on a foundation of what is required today just to get it to work.
So the answer to the OP is sure you can have as many individuals you wish working on a single project, we have already proven it, and all that is need is someone acting as the project manager to make sure things goes where they need to go and bodies of course to work on the project.