Suggested Pacing Guide

joyceclp_edu

Is there a suggested pacing guide that someone can share?

How much time is expected to be spent on each notebook?

I appreciate any information you can provide.
Thanks for this incredible resource!

Joyce

dylarm

joyceclp_edu I see that you found the student handout and grading rubric, so that's definitely one suggestion. My personal pacing for this is:

Notebook 1: open 5/8, due 5/11.
Notebook 2: open 5/10, due 5/15.
Notebook 3: open 5/11, due 5/18.
Notebook 4: open 5/12, due 5/23.

I aimed to give students several in-class days to work on each notebook. Some students absolutely need that time, but I do also have students who are familiar with R (or another programming language) already, and each notebook takes them only about 30 minutes. But fortunately, they're also the students who will then help others in the class.

cschumacher

I love the idea of pacing and offering the completion quiz at the end of each notebook. Thank you to everyone who created these resources last year!

One question I have for dylarm: Is there anything to keep the more advanced coding students from working through all 4 notebooks in a few days? When you say "open 5/10", do you mean that Notebook 2 is "closed" prior to that point? I didn't see any way that I could control their access to the notebooks.

dylarm

cschumacher You're right, I don't really have the ability to keep them from starting it (too much, other than honesty I guess). But what I did was I had a separate assignment on Teams for them to submit a PDF of their notebook, and that didn't open until the day I specified. So they could have worked ahead, waited until the assignment was up and then submit their work right away, but usually they would just wait. Your mileage may vary.

cschumacher

That makes sense…thank you!