---
# System prepended metadata

title: 'Project Logistics, Spring 2022'
tags: [resources]

---

---
tags: resources
---

# Project Logistics, Spring 2022

In CS0200, there will be three group projects. Please read this handout for more information about project logistics, because projects are a larger undertaking than the usual homework assignment.

More project-specific material, such as deadlines, content, and grading criteria will be found in each project's respective handout, released 2 weeks before their due date.

## High-Level Overview of Project Logistics

The rest of this document will expand on each of these points.

- You will be part of a project group (2 students) that collaborates on a high-level design of the project. Follow the *design check* instructions on the handout. One member of the group submits it (via Gradescope), adding **both** group members to the Gradescope submission.
- Your project group will meet with a TA to review your design  (this is the *Design Check*)

## Project Groups and Design Check TAs

Students will be working in **two person groups** for the project. You will have to choose different partners for each project.

### Note on choosing your project group

You will choose your own project group. **Once you have a group, you should fill out [this form](https://docs.google.com/forms/d/1bLerGfY3FWx5nXv9Vlhlie6DQe_OaH28qDt84SyGprg/edit).** For help with the group search, please use the Ed thread for finding group partners. **If you do not submit the group form, you will be automatically assigned a group.**
<!-- [this Ed post](https://piazza.com/class/kjqgmueegkh6j2?cid=5).  -->

Also, we encourage you to reach out to your mentor groups as well!

### Project Groups
Meet with your group and work on the design check together. When you submit to Gradescope, submit one handin for the pair. 

-   If you need access to the stencil code before your design check, please checkout the stencil from git for. When submitting code for the design check to Gradescope, however, only one person needs to submit.

### Completing the Project

Each group will submit one copy of its final code for the project, with **both** members added to the submission.

You may not look at and debug the code of people outside of your group. *This will be considered a violation of collaboration policy.* That said, you are still encouraged to talk to any students about the project at a high level to fill out any conceptual gaps!

**Both members of the same group are responsible for understanding the code that got turned in. The midterm and final may ask follow-up questions about the project.** If you split up work, take time to make sure everyone in the group understands how all of the pieces work. 

### Summary of the Collaboration Policy

The following table summarizes the collaboration policy for projects.

|  | Code Together | Conceptual questions | Debugging help |
| -------- | -------- | -------- | --------- |
| Same group | yes | yes | yes |
| Classmates beyond group | no | yes | no|
| Course Staff (TAs) | | yes | yes |
| People outside Spring 2022 CS0200 | no | no | no | 

## Deadline 1: Design Check

The design check will consist of a series of questions, usually written (though there may be coding questions, depending on the project). These questions will be detailed in each project's handout.

After reading the project handout on their own, group members are expected to come together, work on the design check questions, and submit a single design check work on Gradescope. Only one submission per group is necessary, and the person submitting should add ALL their group members to the submission on Gradescope (feel free to come to post on Ed if you're having trouble doing so).

Groups should submit this work no later than *two hours* before their design check appointment that was signed up for. This gives your design check TA enough time to read it before your discussion! 

The design check appointment itself will be a ~30 minute Zoom call with the design check TA where group members will talk about their answers to the design check questions. *Both* group members are expected to come to and participate in the discussion. The design check TA may ask any group member questions about the work that was submitted. 

#### A note on design check grading:

Your design check grade will be primarily based on whether you had viable ideas for each of the questions and were able to explain them adequately to the TA (for example, we expect you to be able to describe why you picked a particular plot or table format). Your answers do not have to be perfect, but they do need to illustrate that you've thought about the questions and what will be required to answer them. The TA will give you feedback to consider as part of your final implementation of the project.

Your design check grade will be worth roughly a third of your overall project grade. Failure to account for key design feedback in your final solution may result in deductions.


Remember that the goal of the design check is to review your project plans and to give you feedback well before the final deadline! Many students make changes to their designs following the check: doing so is common and will not cost you points.


## Deadline 2: Final Handin

Finally, all project groups will hand in their final submission on Gradescope! Only one person from each group needs to hand in the submission, but they should add the other member of their group to the handin on Gradescope (feel free to post on Ed/come to hours if you're having trouble doing so). 

After submission, groups will meet with their grader for Final Grading to go over the project.


## Peer Assessment
At the end of the project, you'll also be asked to fill out a form describing how each member of your group and group contributed to the project work. You'll also describe your groupmates' strengths and weaknesses as project partners. **Your answers will NOT be shared directly with your groupmates**.

This assessment serves two purposes:
- It helps the faculty and HTAs manage any concerns that arise over group dynamics.
- It helps us help you assess your skills at working with others on programming projects. If we see similar comments arising from multiple groupmates, we'll share an aggreated summary with the student in question.

These assessments will not impact your project grade, unless they reveal that you did not actually contribute (much) to work that was submitted in your name. If you have concerns about this, reach out to Kathi and Milda.