Draft
Review the instructions for the final product before starting work on the draft so you understand what the final paper is going to look like.
The purpose of the draft and peer review is to give you an opportunity to get early feedback on your analysis. Therefore, the draft and peer review will focus primarily on the exploratory analysis and initial drafts of the final product(s). Write the draft in the report.qmd file in your project repo.
You should have a functional product at this stage, but it is okay to have some incompleteness or partial components. If you have made more progress by this point, then you are likely to receive higher quality feedback.
Evaluation criteria
| Category | Less developed projects | Typical projects | More developed projects |
| Functional prototype | Product is non-functional or broken. | Product is reasonably functional. It need not be perfect or without errors, but is mostly working and includes most substantive parts. | Product is functional and performs without errors. All major components have been incorporated. Still lacks polish and finishing touches. |
| Progress | It is unclear whether or not the project will be completed by the deadline. | The team has made progress on the project at this point and is on track to finish by the deadline. | The team has made substantial progress on the project at this point and is on track to finish ahead of the deadline. |
| Reproducibility | Source code is unclear. Project files are missing or hard to find. Project files cannot be rendered. |
Source code is easy to read, properly formatted, and appropriately documented. Project files are generally organized in the repository and easy to find. Project files generally render with minimal errors. |
All expectations of typical projects + all required files are provided. Project files (e.g. Quarto, Shiny apps, R scripts) render without issues and reproduce the necessary outputs. |