Unit2
Ch. 1
1
2
3
4
5
6
7
8
9
10
11
12
13
Ch. 2
14
15
16
17
18
19
20
21

Lesson 21: Peer Review and Final Touches

Overview

Question of the Day: How can we use feedback to make our websites better?

This lesson focuses on the value of peer feedback. Students first reflect on what they are proud of, and what they would like feedback on. Teams then work with peers to get that feedback through a structured process that includes the project rubric criteria. Afterwards, students decide how they would like to respond to the feedback and put the finishing touches on their sites. After a final review of the rubric, they reflect on their process. To cap off the unit, they will share their projects and also a overview of the process they took to get to that final design.

Purpose

Peer review encourages students to leverage their peers as resources and develop effective communications skills. The final reflection and presentation allow students to practice communication about their work.

Assessment Opportunities

Use the project rubric attached to this lesson to assess student mastery of the learning goals for this unit. You may also choose to assign the post-project test through Code Studio.

Agenda

Lesson Modifications

Warm Up (5 mins)

Feedback and Iteration

Showcase

Post-Project Test

View on Code Studio

Objectives

Students will be able to:

  • Give and receive feedback
  • Prioritize and implement incremental improvements

Preparation

  • Print a copy of the peer review guide for each student.

Links

Heads Up! Please make a copy of any documents you plan to share with students.

For the Teachers

For the Students

Support

Report a Bug

Forum

Teaching Guide

Lesson Modifications

Attention, teachers! If you are teaching virtually or in a socially-distanced classroom, please see these modifications for Unit 2.

Warm Up (5 mins)

Discussion Goal

This should be a fun time for students to reflect on the great work that they have done, but also recognize that they can always use an outside perspective. This will also prepare them to fill out the creator portion of the peer review guide.

Journal 3-2-1

Prompt: What 3 parts of your website are you most proud of? What are 2 things you learned while working on this website? What 1 thing would you like an outside opinion on?

Share: Allow students to share their responses with the class.

Question of the Day: How can we use feedback to make our websites better?

Remarks

You should now have a polished product you are proud of. An important part of any major project is to get feedback from people not working on that project with you. They may bring some perspective you might have missed. We will spend today giving and getting feedback. Then you will reflect on how to put this feedback into action.

Feedback and Iteration

Reflect: Peer Review

Distribute: One copy of the peer review guide to each team.

Group: Pair teams up with each other. Alternatively, you could pair individuals from different teams together.

Peer Review Process

Teams will:

  • Open up their website projects in Web Lab.
  • Fill in the top part of the worksheet, identifying what they would like feedback on. (They should have thought about this at the end of the last lesson)
  • Trade places with the other team so each is now looking at the other's sheet and website.
  • Give feedback on the other team's work.
  • Switch back to their sheet and website to review feedback.
  • Make a plan for implementing some of the feedback.

Prepare and Try: Final Touches

Transition:Teams return to Code Studio and make any improvements that were identified in the peer review session. If they did not get any suggestions from the peer review, you may want to give them some suggestions.

Teams should also review the rubric as a final way to check their work.

Reflect: Final Reflection

Distribute: Hand out one copy of the project reflection to each student.

In the reflection, students will reflect on both the process and the product. They should identify aspects of the page itself that they are proud of, as well as how the group worked together. They also describe what they have learned in the course of the project.

Send students to Code Studio to complete their reflection on their attitudes toward computer science. Although their answers are anonymous, the aggregated data will be available to you once at least five students have completed the survey.

Showcase

Showcase Set Up

Setup: Students need:

  • A computer to display the website.
  • A way to display their website progression screenshots

Student Website Showcase

Students should stand next to their computers and talk to people attending the showcase about their work. If you can't get others to come visit your room for this activity, you can split the class in half and have one half present while the others circulate. Then they can switch.

Post-Project Test

The post-project test is found at the bottom of the Web Development unit overview page on Code Studio (studio.code.org/s/csd2-2019).

This test is locked and hidden from student view by default. In order for students to see and take this test, you'll need to unlock it by clicking the "Lock Settings" button and following the instructions that appear.

  • Lesson Overview
  • 1
  • (click tabs to see student view)
View on Code Studio

Student Instructions

  • Final Website
  • 2
  • (click tabs to see student view)
View on Code Studio

Student Instructions

Use Feedback

Now it's time to use the peer feedback to make your site even better.

Do This

  • Use the plan that your team came up with to improve your website.
  • Reflection
  • 3
  • (click tabs to see student view)
View on Code Studio

Student Instructions

This level is an assessment or survey with multiple questions. To view this level click the "View on Code Studio" link.

Standards Alignment

View full course alignment

CSTA K-12 Computer Science Standards (2017)

AP - Algorithms & Programming
  • 2-AP-15 - Seek and incorporate feedback from team members and users to refine a solution that meets user needs.
  • 2-AP-16 - Incorporate existing code, media, and libraries into original programs, and give attribution.
  • 2-AP-17 - Systematically test and refine programs using a range of test cases.
  • 2-AP-18 - Distribute tasks and maintain a project timeline when collaboratively developing computational artifacts.
  • 2-AP-19 - Document programs in order to make them easier to follow, test, and debug.