Close
Close full mode
logoMakeCode AP CSP

Unit 5 Culminating Project

Summary

Materials

Instructional Activities and Classroom Assessments

  • Day 20

    1. Introduction of the Project (10 minutes)
    2. Brainstorm Ideas (15 minutes)
    3. Pair and Share (15 minutes)
    4. Select Your Group and Project Idea (10 minutes)
    5. Homework

  • Day 21

    1. Finish Your Pseudocode (10 minutes)
    2. Pair and Share (10 minutes)
    3. Set up GitHub Repository for Collaboration (5 minutes)
    4. Write Code (25 minutes)
    5. Homework

  • Day 22

    1. Team Meeting (5 minutes)
    2. Write Code (40 minutes)
    3. Team Meeting (5 minutes)
    4. Homework

  • Day 23

    1. Set up for Gallery Walk (5 minutes)
    2. Gallery Walk (25 minutes)
    3. Create a Revision Plan (20 minutes)
    4. Homework

  • Day 24

    1. Team Meeting (5 minutes)
    2. Write Code (40 minutes)
    3. Team Meeting (5 minutes)
    4. Homework

  • Day 25

    1. Team Meeting (5 minutes)
    2. Write Code (40 minutes)
    3. Team Meeting (5 minutes)
    4. Homework

  • Day 26

    1. Team Meeting (5 minutes)
    2. Finalize Code (20 minutes)
    3. Prepare for Presentations (25 minutes)
    4. Homework

  • Day 27

    1. Presentations (40 minutes)
    2. Finalize Submissions and Turn in Project (10 minutes)

Learning Objectives

The project is a review of the Learning Objectives covered in this unit.

Essential Knowledge

The project is a review of the essential knowledge skills covered in this unit.

Details

Day 20

1. Introduction to the project (10 minutes)

2. Brainstorm ideas (15 minutes)

  • Task students with brainstorming ideas for their project.
  • Encourage them to respond to prompts on the Planning Your Unit 5 Project page to help generate ideas.

3. Pair and share (15 minutes)

  • Encourage students to organize into small groups and have them share their ideas with their classmates:
    • You may consider assigning small groups.
  • Students should offer feedback:
    • Which one sounds most interesting from a user's perspective?
    • Any resources or ideas you have that would help?
  • Students will need to divide tasks among each other to begin the workflow for the project.

4. Select your group and project idea (10 minutes)

  • Students will select a partner:
    • Groups should be pairs of students, or if numbers allow no more than three students.
  • Teams will select their project.
  • Students should share their partner and their project idea with you before class ends.
  • Students will need to divide tasks among each other to begin the workflow for the project.

5. Homework

  • Students should begin writing the pseudocode for their program.

Day 21

Finish your pseudocode (10 minutes)

  • Give students no more than 10 minutes to finish up their pseudocode.
  • If students are finished, they can begin creating their code while they wait on classmates to finish.

2. Pair and share (10 minutes)

  • Students should meet with their partner and share the pseudocode they have written.
  • Students should offer feedback on the pseudocode:
    • Is there something that does not seem to fit the projected plan?
    • Do you have an idea of how they can make their program stronger?

3. Set up GitHub Repository for collaboration (5 minutes)

  • Task one student in each group with creating a GitHub Repository for their project.
  • Other students will accept the invitation from their partners to collaborate.

4. Write code (25 minutes)

  • Students should start writing their code.
  • Encourage students to comment on their code as they write it.
  • Remind them to create meaningful names for their variables.
  • Encourage them to save their project periodically (to protect against unexpected technical issues).
  • Remind them to test their program as they create it.

5. Homework

  • Students should evaluate how much time they will need to complete their project.
  • If they know they will need more time than allotted in class, they will need to work on the program for homework.

Day 22

1. Team meeting (5 minutes)

  • Students meet with their partner and share their code segments as it is written so far.
  • Students should offer feedback on the program:
    • Is there anything in their program that does not reflect their plan properly?
    • Do you have an idea of how to make the program stronger?
    • Are they meeting all of the requirements of the project?

2. Write code (40 minutes)

  • Students should consider their classmate's feedback:
    • Do they need to modify anything based on the feedback they received.
  • Encourage students to comment on their code as they write it.
  • Encourage them to save their project periodically (to protect against unexpected technical issues).
  • Remind them to test their program as they create it.

3. Team meeting (5 minutes)

  • Students should meet their partner and share their program as it is written so far.
  • Identify daily goals that where not completed and need to be completed for homework.

4. Homework

  • Students should evaluate how much time they will need to complete their project; they also need to evaluate how far along they are with their game development to determine if they are ready for the gallery walk.
  • If they know they will need more time than allotted in class or if they know they have not developed their game sufficiently for the gallery walk, they need to work on the program for homework.

Day 23

0. Before class

  • Print enough Gallery Walk Feedback forms for each group to use one at each game they review.

1. Set up for Gallery Walk (5 minutes)

  • Task students with setting up for the Gallery Walk.
  • Each group should use two computers:
    • One will display the game in Edit mode (so students can see both the game and the code).
    • One will display a PowerPoint slide with the following information:
      • Name of the game
      • Objective of the game
      • Purpose of the program
      • Program's functionality

2. Gallery Walk (25 minutes)

  • Encourage groups to display their game/program for classmates to test and provide feedback based on the project rubric and user experience.
  • Teams will have five minutes at each station to play the game and provide feedback based on the project rubric.
  • Each team will be able to review five games in the time allotted.
  • Teams should complete a Gallery Walk Feedback form for each game they play.
  • Set a timer for 5 minutes to keep track of time.
  • When the timer ends, ask students to rotate to another station:
    • If students end early, they can swap with another group that is finished.
  • Repeat the process until the end of the 25 minutes.

3. Create a revision plan (20 minutes)

  • Encourage students to review the feedback provided by other groups.
  • Based on feedback, encourage students to create a revision plan for their game.
  • Students should assign the modifications to team members so the work is evenly distributed.

4. Homework

  • Students should evaluate how much time they will need to complete their project.
  • If they know they will need more time than allotted in class, they will need to work on the program for homework.

Day 24

1. Team meeting (5 minutes)

  • Students should gather in their groups and share their program as it is written so far.
  • Students should offer feedback on the program:
    • Is there anything in their program that does not reflect their plan properly?
    • Do you have an idea of how to make the program stronger?
    • Are they meeting all of the requirements of the project?

2. Write code (40 minutes)

  • Students should consider their classmate's feedback:
    • Do they need to modify anything based on the feedback they received.
  • Encourage students to comment on their code as they write it.
  • Encourage them to save their project periodically (to protect against unexpected technical issues).
  • Remind them to test their program as they create it.

3.Team meeting (5 minutes)

  • Students should gather in their small groups and share their program as it is written so far.
  • Identify daily goals that where not completed and need to be completed for homework.

4. Homework

  • Students should evaluate how much time they will need to complete their project.
  • If they know they will need more time than allotted in class, they will need to work on the program for homework.
  • Encourage students to review the prompts to prepare for drafting their responses (or better yet begin their responses).

Day 25

1. Team meeting (5 minutes)

  • Students should meet with their partners and share their program as it is written so far.
  • Students should offer feedback on the program:
    • Is there anything in their program that does not reflect their plan properly?
    • Do you have an idea of how to make the program stronger?
    • Are they meeting all of the requirements of the project?

2. Write code (40 minutes)

  • Students should consider their classmate's feedback:
    • Do they need to modify anything based on the feedback they received.
  • Encourage students to comment on their code as they write it.
  • Encourage them to save their project periodically (to protect against unexpected technical issues).
  • Remind them to test their program as they create it.

3. Team meeting (5 minutes)

  • Students should gather in their small groups and share their program as it is written so far.
  • Identify daily goals that where not completed and need to be completed for homework.

4. Homework

  • Students should evaluate how much time they will need to complete their project.
  • If they know they will need more time than allotted in class, they will need to work on the program for homework.
  • Students should also write complete drafts to the prompts regarding the project.

Day 26

1. Team meeting (5 minutes)

  • Students should gather in their small groups and share their program as it is written so far.
  • Students should offer feedback on the program:
    • Is there anything in their program that does not reflect their plan properly?
    • Do you have an idea of how to make the program stronger?
    • Are they meeting all of the requirements of the project?

2. Finalize code(20 minutes)

  • Students should consider their classmate's feedback:
    • Do they need to modify anything based on the feedback they received.
  • Encourage students to comment on their code as they write it.
  • Encourage them to save their project periodically (to protect against unexpected technical issues).
  • Remind them to test their program as they create it.

3. Prepare presentations (25 minutes)

  • Students will prepare for their presentation.
  • Students should decide who will present which section:
    • Each member of the team must present.
  • The presentation will include the following:
    • Name of the game
    • An explanation of the purpose of the game
    • An explanation of the function of the game
    • Detailed steps of how the algorithms in the game work
    • Identify the input and output of the game
    • Describe one test case
    • Describe another test case
  • Students can create a PowerPoint for a visual aide, or open the game and show it during the presentation.
  • Groups should practice their presentation.

4. Homework

  • Students should practice their presentation.

Day 27

1. Presentations (40 minutes)

  • Groups will take turns presenting their programs.
  • Each group will have five minutes to present their game to the class.

2. Finalize submissions and turn in project (10 minutes)

  • Task students with:
    • Publishing their game and copying the link to the Project Requirements & Responses page.
    • Creating a screencast of their game being played.
    • Creating a screenshot of their program and label each type of algorithm implementation.
    • Each partner needs to add the link and the screenshot to their project responses page.
  • Students should turn in their document digitally so the link and video can be viewed.
📘 Unit 5 - AAP Part 2 — Previous
Day 20-27
Next — 📘 Unit 5 - AAP Part 2
Planning Your Unit 5 Project