Advice on Forming Teams

You are permitted, but not required, to work in teams for the project. Teams may be any manageable size (2-4 is recommended), but all members must be students enrolled in this course.  Teams must be self-organized, the teaching staff will not assign or arrange teams.

Some suggestions:

	Start forming your team and planning your project from the beginning of the semester, do not wait until just before the project proposal is due.
	Team members should be comfortable with the same programming language, on the same platform, using the same IDE, toolkits, middleware, etc.
	Team members should reside (or work) at compatible locations, e.g., all on campus, all on the upper east side, all in Queens.
	Team members who routinely do not show up for scheduled meetings should be dropped from the team (the instructor must be informed of any team composition changes that occur after the preliminary project proposal is submitted).
	One team member should be responsible for scheduling meetings.
	One team member should be responsible for editing and proofreading documentation (this does not mean that one person writes all the documentation).
	One team member should be responsible for a shared code repository (e.g., cvs, svn, sourceforge, google project hosting).
	One team member should be responsible for the testing and demo vehicle(s).

Back to Top