Semester plan

Weekly timeline, milestones, and deliverables.

A reusable phase-based course plan, from partner onboarding to final showcase. The first implementation was the 2025-2 Spring Semester run.

Semester Phases

The course moves from discovery to working prototype, then into iterative development, stabilization, and final showcase.

0Preparation

Client briefs, course setup, GitHub organization.

1Discovery

Team formation, client meetings, requirements.

2Prototype

Early build, review, feedback, revised backlog.

3Delivery

Implementation, testing, documentation, showcase.

Gantt View

A compact planning map of major activities across the semester. Scroll horizontally on small screens.

Activity
Pre
W1
W2
W3
W4
W5
W6
W7
Mid
W8
W9
W10
W11
W12
End
Setup and orientation
Briefs, setup, foundations
Team and discovery
Teams, clients, requirements
Prototype sprint
Prototype build
Formal review
Review
Development sprints
Core implementation
Stabilization
Testing, docs, handover
Final showcase
Demo

Milestones and Deliverables

Detailed checkpoints for students, mentors, clients, and evaluators.

Pre-semester

Client and project onboarding

Identify partner organizations, define project briefs, clarify IPR/open-source expectations, and prepare the EAD-Labs GitHub organization.

Output: project briefs
Week 1

Course orientation

Introduce course goals, evaluation structure, team workflow, WhatsApp community, GitHub practices, and examples of past educational apps.

Output: course setup
Week 2

Foundations workshop

Discuss agile methods, educational technology design, security expectations, accessibility, ethics, responsible AI, and stakeholder communication.

Output: shared working norms
Week 3

Team formation and project selection

Students form teams, review project briefs, meet mentors, choose collaboration tools, and create repository structures.

Output: team and repo setup
Weeks 4-5

Requirements and design direction

Teams conduct client meetings, document user needs, write meeting minutes, define acceptance criteria, and submit a requirements report.

Output: requirements report
Weeks 6-7

Prototype sprint

Build low-fidelity and early working prototypes, log issues, gather feedback, and prepare a short design rationale.

Output: prototype demo
Mid-semester

Formal review

Demonstrate the prototype, present risks, receive evaluator feedback, update the backlog, and revise the development plan.

Output: review presentation
Weeks 8-10

Iterative development

Run weekly sprints, implement core features, test with users where feasible, and review security, data, and accessibility concerns.

Output: sprint builds
Weeks 11-12

Stabilization and documentation

Improve usability, fix defects, prepare deployment notes, write technical documentation, and complete the final report draft.

Output: final report draft
End semester

Final showcase

Submit final report, repository, presentation, reflection, client handover package, and demonstrate the educational app.

Output: final demo and handover