Product

You will create a functioning, working end-product constructed using a reproducible workflow. The form of your product will vary depending on your objectives.

Regardless of format, the product should be accessible to a public audience. That means users should be able to access the content through a web interface (and not have to clone your Git repo to access and run files).

Your final product must be reproducible. All team members should contribute to the GitHub repository, with regular meaningful commits.

Your final product will be evaluated based on degree of difficulty and execution. You will receive feedback during the proposal stage as to the perceived level of difficulty of your project.

Evaluation criteria

Category	Less developed projects	Typical projects	More developed projects
Design + visualization	The design/visualization are inappropriate for the data and/or audience. Charts are hard to read. Design is non-intuitive or hard to access.	The design/visualizations are appropriate and easy to read.	All expectations of typical projects + consistently adheres to best practices for high-quality, accessible data visualizations. Includes but not limited to deliberate choice of color palette, appropriate font size, intuitive labeling.
Functionality	Product(s) are incomplete or broken. Code generates numerous errors or warnings which cause usability problems. Product(s) do not provide value to the audience.	Product(s) provide sufficient value to the intended audience. No errors or warnings present in final version. Product(s) are complete.	All expectations of typical projects + product(s) are intricate and exceptionally designed. Showcases significant technical skills beyond those directly taught in the course.
Code	Code is not efficient, hard to read, and/or lacks appropriate formatting or consistency. Clearly looks like multiple individuals wrote it instead of a single, cohesive approach.	Code is efficient, easy to read, and properly formatted.	All expectations of typical projects + code is thoroughly documented with comments. Adheres to consistent style guide. Clearly reusable and/or extensible for outside developers.
Impact	Broader impact is unclear or lacking. Product(s) lack a discernible usefulness.	Broader impact and usefulness of the deliverable(s) is clear.	All expectations of typical projects + product(s) deliver clear benefits to target audience. Has clear applications beyond the scope of this course.