IGEM 2005 "Top Tens"

The following opinions and poll results have been compiled from the 2005 intercollegiate Genetic Engineering Machines (iGEM) Jamboree teams.  After long discussion, we decided that these “Top 10’s” be presented more as a series of constructive criticisms rather than a list.  This may also have to do with the fact that we were unsure if we could reach a requisite ’10’.

==='''Ideas for Improvements:'''===
11. Organize an all-ages iGEM social event post-conference
 
10. Encourage the continuation of projects and project members.  Hopefully these members would be able to update iGEM on their progress, thus providing inspiration and ideas for current iGEM members.
 
9.  Teams try to submit project ideas (not necessarily the same one that will be used in the project) by June to a common list.  This way teams can exchange ideas and information about their projects, and teams without ideas yet can get inspiration.
 
8.  Possible iGEM “parts guardian” who could extend the standardized parts metaphor by acting as a kind of hardware store clerk.  When presented with parts requests, this person could give opinions on the construct proposition and make sure parts get delivered on time.
 
7.5  Provide opportunities for interschool competition.  For example, two or more schools would be charged with implementing a common goal.  iGEM would be charged with selecting the winning team based on the efficacy, creativity, and elegance of each design.  Competition would help produce a better product, and judgement would allow iGEM members a chance to evaluate the work of their peers.  

7. Conversely, encourage interteam collaborations.  Cooperation and self-imposed deadlines might provide motivation to finish and allocate large projects into smaller complementary portions which would be easier to complete.  
 
6. Deliver iGEM parts plasmids registry parts on time next year
 
5. Funding sources may be needed to commence and sustain our work.  Aid with public or private sponsorships would be very helpful.
 
4. Establish an online forum for teams to discuss technical methods, problems with implementation, advice, general discussion, etc. in addition to the wiki (which often acts as an intra-team device rather than an inter-team communication web).
 
3. Parts Database Improvements:
* Standardize interface using drop down boxes or format templates
* Standard nomenclature system, barcodes
* Better overall database organization

2. Acknowledge that more projects should be completed.
 
1. More initial technical training for new members.


==='''Ideas for Increasing Scalability:'''===

10. Possibly run the Jamboree as a conference with simultaneous talks categorized by topic (ie. quorum sensing, light detection).
 
9. Keep the current presentation length (30 minutes).  Shorter presentations would lack sufficient depth.
 
8. Start the Jamboree with a poster session. Groups would be required to at least provide the slides from their presentations for exhibition.
 
7. Encourage interschool cooperativity (by region, project interest).
 
6. Get financial help for teams with little funding.  Synthesize small parts from other schools or do modeling work.
 
5. Encourage synthesis as a supplement to the standard biobrick method
 
4….
 
1. There is skepticism that this competition is ready to grow significantly at this time. 


Look at [[IGEM_2006_Planning]] to see how the wiki is being used as a forum by the instructors.  Perhaps we could folllow suit with this page; that is, each item of the list could link to a new page for discussion.