Skip to content

ProjectSpecChecklist.md

Latest commit

 

History

History
37 lines (29 loc) · 3.7 KB

ProjectSpecChecklist.md

File metadata and controls

37 lines (29 loc) · 3.7 KB
Raw

Team 26 Digital Equity Learning - Capstone Project Specifications Checklist

  • A GitHub repository containing:

    • A README file that documents how to run your code.
    • A requirements.txt file listing the libraries needed to run your code.
    • Code that generates results and figures in your report.
    • Cleaned code: unused code blocks and files removed, absolute file paths converted to relative paths, and personal keys (e.g. API) removed.
    • A data access statement indicating how to access the data or explaining who owns the data. Licenses for data use and redistribution are respected.
    • In-line code attributions for any code segments your team did not write or received external assistance to create. If code is reused from an open source project, licenses are respected.

  • A 3-5 minute video summary or poster about the highlights of your project.

  • A written report about your work. We strongly suggest keeping the report under 3000 words (excluding bibliography and appendix). Your report should meet the following specifications:

    • Project statement: your report explains the problem you attempted to solve at a level appropriate for a broad audience.
    • Methodology: your report explains how you attempted to solve the problem and justifies your methodological approach.
    • Evaluation strategy: your report defines what a successful outcome would be and includes a critical evaluation of your work following an appropriate strategy.
    • Technical depth: your report demonstrates mastery of learning objectives from multiple MADS courses.
    • Translation: your report interprets the outcome of your work. Numerical results are translated to insight on your problem.
    • Broader impacts: your report identifies who stands to be impacted by your work. You identify at least one ethical question or concern that could arise from your work or its potential applications.
    • Appropriate technical writing: your writing is clear, professional, and accurately reflects your work. Writing avoids overstatement.
    • Visuals: your report includes at least 3 original, legible, data visualizations. Visuals are explained and integrated in the body of the report.
    • Context: your report cites at least 3 studies, blogs, academic articles, or other sources that are relevant to your project. All references in your report are correctly formatted with a consistent citation style (such as MLA or APA).
    • Statement of work: your report contains a statement identifying the contributions of each team member.
    • Incorporating feedback: Your report builds on feedback from your project mentor. Major issues identified during check-ins are addressed.
    • (Optional) An appendix: Show us what you left out. Create an appendix to describe any other efforts you made that did not get included in the main report.

  • A post in the #capstone-gallery channel to share your video, poster, and/or blog.

Additional Reminders from the instructional team:

Capstone projects are highly individualized, and there is no single definition of success. To promote curiosity and risk-taking, we will be using specifications grading to assess your final projects. In this framework, all projects that meet the minimum requirements, specified in the checklist below, receive full credit. Of course, we expect you will go beyond the minimum! Projects that meet all specifications will receive full credit. As a grace, one specification can be missed without penalty.

Projects missing 3 specifications will receive 80% of full credit. Projects missing 4 specifications will receive 70% of full credit… etc.

Projects containing plagiarized material cannot receive credit. Please refer to the MADS Academic Integrity statements if you are unsure what constitutes plagiarism.