Student hub

Team workflow, submissions, presentations, and evaluation.

Use this page as the working guide for ET617 project teams across course runs.

Maintain a sprint board, assign responsibilities, document decisions, and keep weekly progress visible to mentors and instructors.

Use short iterations, backlog prioritization, issue labels, weekly demos, retrospective notes, and feedback-driven planning.

Use the EAD-Labs GitHub organization for source code, issues, pull requests, releases, README files, and deployment documentation.

Submit requirements, design rationale, implementation notes, testing evidence, limitations, and reflection in the prescribed report format.

Prepare mid-semester and final presentations with problem context, design evolution, demo, evaluation evidence, and next steps.

Do not commit secrets, collect unnecessary personal data, expose private user information, or deploy unreviewed authentication flows.

Evaluation Rubric

Exact weights may be announced by the instructor; this structure helps teams plan their effort.

Criterion	Evidence
Problem understanding	Client requirements, learner context, scope clarity, and educational rationale.
Design quality	User flows, accessibility, inclusion, interface clarity, and learning alignment.
Implementation	Working app, code quality, GitHub hygiene, testing, deployment readiness, and maintainability.
Process	Agile board, sprint notes, meeting minutes, mentor engagement, and response to feedback.
Communication	Reports, presentations, demos, repository documentation, and final handover.
Responsible practice	Security, ethics, responsible AI, anti-plagiarism, IPR, DPDP awareness, and accessibility.