few_shots: 
Example:
Problem/activity:
You’re mixing ingredients for cookies. The recipe says to combine 6 tablespoons, or ¾ stick, of butter with 1 cup of sugar. You accidentally mix in a whole stick of butter (8 tablespoons) with the cup of sugar. How can you fix this?


Concept/skill: 
Use ratio and rate reasoning to solve real-world and mathematical problems, e.g., by reasoning about tables of equivalent ratios, tape diagrams, double number line diagrams, or equations.

Answer: 
Yes. This problem solves a real-world problem involving mixing ingredients for cookies. A student doing this problem would need to reason about equivalent ratios of butter amounts to sugar amounts.

Now, does the following problem or activity enable students to learn the full intent of the following concept or skill?

shot_info: fl_problem_000972_pos_0

6
standard_description: Use a pair of perpendicular number lines, called axes, to define a coordinate system, with the intersection of the lines (the origin) arranged to coincide with the 0 on each line and a given point in the plane located by using an ordered pair of numbers, called its coordinates. Understand that the first number indicates how far to travel from the origin in the direction of one axis, and the second number indicates how far to travel in the direction of the second axis, with the convention that the names of the two axes and the coordinates correspond (e.g., x-axis and x-coordinate, y-axis and y-coordinate).
problem_activity: Warm-up
The purpose of an Estimation warm-up is to practice the skill of estimating a reasonable answer based on experience and known information, and also help students develop a deeper understanding of the meaning of standard units of measure. It gives students a low-stakes opportunity to share a mathematical claim and the thinking behind it (MP3). Asking yourself, “Does this make sense?” is a component of making sense of problems (MP1), and making an estimate or a range of reasonable answers with incomplete information is a part of modeling with mathematics (MP4).
Launch
The first few times using this routine, ask students to explain the difference between a guess and an estimate. The goal is to understand that a guess is an answer without evidence, whereas an estimate is based on reasoning using the available information.
Display the image for all to see. Ask students to silently think of a number they are sure is too low, a number they are sure is too high, and a number that is about right, and write these down. Tell students that the lamp post’s height should be in relation to the person’s height. If students ask, confirm that this is the same person in the photo from the previous lesson (whose height was revealed to be 6 feet or 72 inches). Then, write a short explanation for the reasoning behind their estimate.
Student Facing
[IMG]
How tall is the lamp post?
Record an estimate that is:
| too low | about right | too high |
|---------|-------------|----------|
|         |             |          |
Explain your reasoning.
Student Response
Teachers with a valid work email address can
click here to register or sign in
for free access to Student Response.
Activity Synthesis
Ask a few students to share their estimate and their reasoning. If a student is reluctant to commit to an estimate, ask for a range of values. Display these for all to see in an ordered list or on a number line. Add the least and greatest estimate to the display by asking, “Is anyone’s estimate less than
\(\underline{\hspace{.5in}}\)
? Is anyone’s estimate greater than
\(\underline{\hspace{.5in}}\)
?” If time allows, ask students, “Based on this discussion, does anyone want to revise their estimate?” Then, reveal the actual value and add it to the display (15 feet). Ask students how accurate their estimates were, as a class. Was the actual value inside their range of values? Was it toward the middle? How variable were their estimates? What were the sources of error? Consider developing a method to record a snapshot of the estimates and actual value so students can track their progress as estimators over time.


aligns: no