<p>The project is poorly defined: we are to write educational software for CS 111 Computer Programming I students focusing on functions. We have 6 student developers with various backgrounds working in Flex. The project has a duration of about 7 weeks. We have very limited face time (30 min per week) and very limited work time (&lt;8 hours per developer per week). We have limited access to the customers (professor of our course, professor of CS 111, students in CS 111).</p>

<p>Our toolset includes Flex Builder, Subversion, and TRAC.</p>

<p>What methodology is best for this project and why? Alternately, what features should be gathered from various methodologies to better suit this situation?</p>

What makes you think any methodology would be successful under these circumstances -- little communication, more requirements than time, and lack of access to customers?
That being said, I would focus on incremental delivery (each iteration should have some few working features), unit testing (all tests pass before check in), tagging of incremental releases (the ability to go back to a working release), and pairing of strong team members with weaker team members to boost the overall productivity of the team.  Consider devoting one strong member of the team to integration testing.
Incremental delivery is most important.  Showing a working demo of less than what was asked for is always better than showing a non-working prototype.