Build for Ukraine

Class Deliverables

Build for Ukraine requires several deliverables throughout the course to ensure teams make consistent progress and communicate their work effectively. These deliverables provide opportunities for feedback, accountability, and documentation of your contributions to addressing real-world challenges.

Team Deliverables

Preliminary Design Review (PDR)

See the Design Reviews page for full requirements.

  • Format: 12-15 minute presentation (timing may be adjusted depending on number of teams)
  • Team Contribution Log: Submit a brief document listing each team member and their specific contributions to the project so far
  • Presentation Requirement: Different team members should present different sections of the PDR

Critical Design Review (CDR)

See the Design Reviews page for full requirements.

  • Format: 12-15 minute presentation (timing may be adjusted depending on number of teams)
  • Team Contribution Log: Submit an updated document listing each team member and their specific contributions since PDR
  • Presentation Requirement: Different team members should present different sections of the CDR

Final Presentation

See the Design Reviews page for full requirements.

  • Format: 10-12 minute presentation
  • Audience: Remember that part of the audience will be hearing about your project for the first time, and may include potential collaborators for spring continuation

Final Paper

In addition to your final presentation, each team will submit a written final paper that documents your project’s development, findings, and potential for future impact. This paper serves as both a technical record of your work and a guide for others who may continue or build upon your efforts.

Paper Requirements:

  • Length: 8-12 pages (excluding references and appendices)
  • Format: IEEE or ACM conference paper format (templates will be provided)
  • Authorship: All team members should be listed as authors
  • Due Date: January 30th 23:59:59 Anywhere on Earth

Required Components:

  1. Executive Summary (1 page maximum): One-sentence jargon-free project objective, brief overview of approach and key outcomes, summary of recommendations for future work
  2. Background and Problem Context (suggested 1-2 pages): Description of the challenge problem and its significance, analysis of current practices and limitations, identification of key stakeholders and end-users
  3. Project Objectives and Approach (suggested 2-3 pages): Clear articulation of project goals and success metrics, description of methodology and design process, explanation of what makes your approach novel or effective, discussion of scope decisions and trade-offs
  4. Implementation and Results (suggested 2-4 pages): Detailed description of what you built, developed, or analyzed; presentation of key findings, data, or outcomes; visual representations; discussion of validation with stakeholders or end-users
  5. Challenges and Risk Assessment (suggested 1-2 pages): Analysis of technical, logistical, or contextual challenges encountered; description of how challenges were addressed; identification of remaining risks and limitations
  6. Impact and Continuation Plan (suggested 1-2 pages): Assessment of potential real-world impact, concrete plan for project continuation beyond IAP, recommendations for teams or organizations that might advance this work, resource requirements and timeline estimates
  7. Conclusions and Lessons Learned (suggested 1 page): Reflection on what worked well and what could be improved, key insights gained, advice for future teams
  8. References: All sources consulted, including conversations with stakeholders

Evaluation Criteria:

Papers will be evaluated on clarity and organization of writing, depth of technical or analytical content, evidence of stakeholder engagement and user-centered design, realistic assessment of challenges and limitations, quality and feasibility of continuation plan, and professional presentation and documentation.

Submission:

  • Submit as a PDF via TBD submission platform
  • Include any supplementary materials (code repositories, design files, datasets, etc.) as appendices or linked resources. Please ensure that any linked resources are accessible without any kind of log-in. If staff cannot access a linked resource, it will not count towards your deliverable.
  • One submission per team

Individual Deliverables

Individual Contribution Statement

Each student will submit an individual reflection document with the final paper. This statement provides an opportunity to articulate your personal contributions, growth, and learning throughout the course.

Requirements:

  • Length: 1-2 pages
  • Due Date: Submitted with the final paper

Required Content:

  • Your Specific Contributions: Describe the concrete tasks, deliverables, or responsibilities you owned throughout the project. Be specific about what you did, not just what the team accomplished.
  • Learning and Growth: Reflect on what you learned—both technical skills and broader lessons about teamwork, project management, working with stakeholders, or understanding the problem domain.
  • Challenges and How You Addressed Them: Discuss any obstacles you encountered (technical difficulties, team dynamics, time management, etc.) and how you worked to overcome them.
  • Team Collaboration: Briefly reflect on how you worked with your teammates and what made the collaboration effective or challenging.

This statement will be kept confidential and is an opportunity to ensure you receive appropriate credit for your work.

Peer Evaluation

Each student will complete a confidential peer evaluation assessing the contributions of their teammates.

Requirements:

  • Format: Online submission (link TBD)
  • Due Date: January 30th 23:59:59 Anywhere on Earth
  • Confidentiality: Your responses will be kept confidential and used only by instructors for grading and to identify teams that may need support

Evaluation Criteria:

You will assess each teammate on:

  • Effort and Engagement: Did they consistently contribute time and energy to the project?
  • Quality of Contributions: Were their contributions valuable and well-executed?
  • Collaboration: Did they communicate effectively, respect others’ ideas, and work constructively with the team?
  • Reliability: Did they meet deadlines and follow through on commitments?

Please provide honest and constructive feedback. This process helps ensure fair recognition of everyone’s contributions and allows instructors to provide support where needed.