Team collaboration

Hi there,
We have done a few team based V3D projects and have tried a number of approaches but it always seems to come down to the skill sets of the individual teams members and the project requirements.

We normally break our teams into Blender Artists, V3D dev, HTML/CSS dev, JS dev, lead creative and a producer. This seems to work out for most projects but when you have a heavy V3D project and tight timelines…then we need multiple V3D devs and multiple Blender artists…it can get complicated fast.

What we do is our 3D assets are created as linked assets to larger Blender project file. This master file, is then published at regular intervals so V3D devs can continue their work.

We have a V3d/JS developer who is responsible to merge V3D tabs, and JS into a master V3D project. This master V3D project is updated on a schedule…and the Creative Director and Producer review the project and provide feedback to the teams.

This requires lots of communication and is really a pain in the ass.

We try to segment parts of projects out so that one person is working on one object/sequence while another person is working on something unrelated. But sometimes the two shall cross.

For situations where there budget is lean and the time is still tight…we run three overlapping shifts where each team member has both Blender/V3D experience. At shift overlap time, the prior dev explains where the project is what is being worked on and the new shift person can take over from that point. NOTE: This only works if people on the team work well together and can communicate effectively otherwise this is not a great solution.

These solutions also rely on having a good backup repository that can be accessed across multiple platforms, devices and the globe.

Not an easy solution but look forward to hearing how others are doing it.