Test/Experiment Phase

As the school year ended, I was able to use the prototype in my two computer science classes as we turned to text based coding. This testing phase allowed me to see what worked and what didn't about this idea going into the summer. A major part of the testing phase was making sure I was staying up to date on the grading as students complete each phase to give immediate feedback. This feedback is intended to let students know if they are on the right track going forward through the levels of the rubric.

Positives

As I worked through this trial run using the new Google Slides Digital Notebook and Tracking Chart, I found that I was more prompt in my feedback. Students, whether in-person or remote learning had the opportunity to interact with the feedback in close to real time. This variation eliminated the problem of the students turning in their notebooks and either not having them when they were working on completing the code or me not seeing them until after the student was complete with the assignment.

Negatives

While going through the Python unit using the new educational technology tools I noticed that there are some small flaws in this design. One flaw was the students did not all use the tracker to accurately tell me when they completed the different phases or had questions. This problem was minimal but it did cost some students from getting the full benefits of this new model structure. Another small problem was me not clarifying that resolving the comment did not allow me to see what was changed easily. After a clarifying moment, this seemed to be eliminated.

Summary

In summary, I think the new format was beneficial to all those who participated. I believe that this still has some work to do and is not a perfect system but there is definite potential. I was not able to post an entire survey about the