Template for Project Descriptions
Not for human consumption at this time.
Project Summary
Outline each project with deliverables, due dates, and evaluation criteria. Adjust the table to match your calendar.
| Project | Focus | Deliverables | Due |
|---|---|---|---|
| P1: Title | Skills or pipeline focus | Shots / write-up / assets | Week X |
| P2: Title | Team or solo | Checklist of files + reflection | Week X |
| P3: Title | Capstone or sprint | Delivery package + presentation | Finals week |
Submission Standards
- File naming convention:
course_project_lastname_v01.ext. - Delivery location (LMS/Drive/repo) and required folder structure.
- Include a brief reflection: what worked, what you would change next time.
Feedback
- How critiques are run (in-class reviews, async notes, rubrics).
- When grades and notes will be returned.
Rubrics (example)
- Craft/technical execution — 40%
- Concept and intent — 30%
- Process and iteration — 20%
- Professionalism (naming, documentation, punctuality) — 10%
Academic Integrity and Assets
- Note what third-party assets are acceptable and how to attribute them.
- Clarify expectations for original work vs. kitbashing or purchased packs.