Here is some advice on good team work and programming, some of it
collected from previous software capstone classes.
It's common for people to become frustrated with each other. The first four times you think to yourself "Harry is lame" the problem most likely lies with you, not Harry. Whatever you're contributing is going to be most valuable if it's surrounded by things other people have contributed, and so it's to your benefit to make sure Harry is contributing. As a team, you should find something for each person to do that (a) they want to do, and (b) they can do. Everyone has skills the others don't.
Make your best attempt to help Harry contribute. When you've done that four times and you're still thinking he's lame, there's a real problem. It may be that some other person on your team needs to handle it, or it may be that the course staff have to handle it. Coming to the staff is not turning someone in, it's just letting us know that there's some kind of problem. We promise to use our own highly fallible judgement coming to any conclusion about what the problem might be.
It is critical that you are sensitive to the role of ownership in team work. There is no such thing as cheating in this class - help each other out. An individual team owns the final product. It is crucial that everyone be allowed to contribute to what that product becomes. No one is going to work hard on anything that they have no influence on (and you can't afford as a team to have anyone not working). Finally, each person on the team needs to have some identifiable role that they own, and that is their responsibility. When you're done, everyone should have made contributions they're proud of.
Try to make some progress every day. You have 9.5 weeks. That's not much time to program a robot, but it's too long a time to try to work on this project as you might on a 3-week project. Slow-and-steady will beat bursts of activity in the long run.
Additionally, pre-integration you don't have a working blimp. Post-integration, you do, even if it's not (yet) doing a great job. Once you've achieved integration, development becomes a lot easier. You'll basically be improving the behavior of the robot, piece by piece. It's much simpler to work independently, and so to get a lot more done by having everyone working at full capacity.