Judging
From 2012e.igem.org
(Difference between revisions)
Line 1: | Line 1: | ||
The judging criteria are still being determined. | The judging criteria are still being determined. | ||
- | < | + | <b>Project Documentation: </b> |
<p>However, every team submission must be documented on the iGEM Wiki, including but not limited to a public executive summary, elevator pitch (max 3 min) video, and public presentation (Slides). | <p>However, every team submission must be documented on the iGEM Wiki, including but not limited to a public executive summary, elevator pitch (max 3 min) video, and public presentation (Slides). | ||
<ul> | <ul> |
Revision as of 21:54, 31 January 2012
The judging criteria are still being determined.
Project Documentation:
However, every team submission must be documented on the iGEM Wiki, including but not limited to a public executive summary, elevator pitch (max 3 min) video, and public presentation (Slides).
- Wiki: You have the freedom to be creative, but a few specific rules apply, and generally follow the collegiate iGEM Wiki requirements. See the <a href="https://2012.igem.org/Requirements/Wiki">wiki requirements</a>.
- Business Plan Wiki: Successful business plan submissions probably include sections that show:
- * The problem or opportunity being addressed.
- * Details of the solution being proposed.
- * The competitive landscape.
- * Skillsets of the founding team and early employees and collaborators required.
- * Information about the team.
- * The team's competitive advantage.
- * Proposed milestones.
- * Business model.
- * Funding requirements tied to milestones.
- * Potential Risks.
- * Actions suggested to mitigate risks.
- * Attribution of work to team members, advisors, and others.
- * If seeking investment, exit scenarios and appropropriately discounted yield calculations.
- Other Track Wikis: The Wiki for the submissions must at least include sections that show:
- The problem or opportunity being addressed.
- Details of the solution being proposed.
- Comparison of alternative solutions.
- Stakeholder maps and actions required to reach them.
- Proposed milestones.
- Potential Risks.
- Actions suggested to mitigate risks.
- Attribution of work to team members, advisors, and others.