[whitetiger0990]

I can only speak about expanding programming, but it's simple.

1) Keep open communication and documentation
2) Divide and conquer

This year it was kind of hard to divide up work if using LabVIEW Basic framework. Using C++ or Advanced framework, just develop the system into subsystems which communicate to eachother. We used the advanced framework and our robot main basically consisted of a series of subVIs which called the code for the Shooter, Conveyor, Drive, Lights (LEDs), etc.

Each subsystem had a cluster that was part of the Robotdata cluster. Each subsystem usually stayed within its own cluster.. so they guy working on Conveyor code developed it completely independently from the shooter code. Then it was later integrated and merged (which wasn't too hard since the only shared code was the robotdata control which just needed to have the new typedefs added, and then tho robot main vi which just needed to call the new code).

Revision control is also good. Everyone works in their own branch until it's merged with the master branch.

Keeping all this in mind, it's easy to expand the programming team.

Similar with the Electronics. Electrical wiring (specifically the PWMs) information is shared with programming, so make sure that's well documented too.

You can have someone work on parts placements and wire routing (might be good to have multiple people do that so there's less mistakes). This also requires talking to the Build team so a speed controller isn't placed on the opposite side of the bot than the motor. One person can also work on labels (labels are always good). Should be short, and useful (tells the name of what it does and where it plugs in).

The actual wiring can also take more than one person.. one to cut, one to crimp, one to place. Etc. With more people, it can go even faster than normal (but not too many..)

Yeah.

We have a Controls team which is responsible for a much more holistic understanding of the bot. While you have some people on build which may have spent their entire time on one subsystem. Because Controls works more intimately with all of the bot, they get to have a much more deeper understanding of it (if they choose to, but that's the fun part!).