Choice Board Examples & Strategies
Use the Choice Board to allow students to display their voice and choice within their learning. The Choice Board can be used in multiple ways by the teacher to:
- Engage students who finish early
- Assess what students have learned at different points throughout the Unit
- Extend the Unit or lesson
- Allow students to display their learning in the Share section
The Choice Board is intended to provide content that can be added to the classroom’s existing Choice Board or to any bulletin board in the classroom.
The following is the Choice Board for this Unit:
| Choice Board | ||
|---|---|---|
|
Dear NASA Write a letter to a NASA engineer to ask questions about a real Mars Rover project. What are they learning about? What do you hope they will find? |
Collection Device Design and build an extension onto your Code Base to help collect samples. Can you create something to push, pull, or hold the samples as the Code Base returns them to the base? |
How far? How far is your Code Base traveling? Add up the distances in all of your projects, to see how far it is going all together. |
|
Change Calendar Think of something that changes during a year (leaves, snow, etc.). Draw or write all of the changes that happen to that object over a year. Can you think of 6 changes? |
Recess Rover Create a recess game where you move like the Mars Rover. Draw or write the rules and the goal of the game, then share it with your teacher at recess. |
From the Future Write a journal entry from the future, as the scientist who gets the collected samples from Mars. How did they change? What did you learn? |
|
Remote Control Rover Try driving your Code Base to collect samples using the Drive Tab in VEXcode GO. Compare and contrast the movement of the robot between code and remote control. |
Watch out for the crater! Imagine that there is a crater between your Code Base and the first sample. Create a project to drive around the obstacle, to collect the sample and return it to base. |
Communication Test Work with a partner, where one of you is the "sequencer," and the other is the "driver." Reset the Field so that the driver cannot see where the objects are. The sequencer needs to communicate how to navigate the Code Base to the driver, who will build the project in VEXcode GO. Test your communication as you test your project! |