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 problem or activity shown below enable students to learn the full intent of the following concept or skill?

shot_info: fl_problem_000972_pos_0

6
standard_description: Understand that the probability of a chance event is a number between 0 and 1 that expresses the likelihood of the event occurring. Larger numbers indicate greater likelihood. A probability near 0 indicates an unlikely event, a probability around 1/2 indicates an event that is neither unlikely nor likely, and a probability near 1 indicates a likely event.
problem_activity: Optional activity
In this activity students compute rates to decide which job applicant is working the fastest checking online comments. They compare rates and total number of comments checked, then see that using rates is the more useful information in this situation.
Launch
Keep students in the same groups of 2.
Representation: Internalize Comprehension.
Activate or supply background knowledge. Allow students to use calculators to ensure inclusive participation in the activity.
Supports accessibility for: Memory; Conceptual processing
Student Facing
A company is hiring people to read through all the comments posted on their website to make sure they are appropriate. Four people applied for the job and were given one day to show how quickly they could check comments.
Person 1 worked for 210 minutes and checked a total of 50,000 comments.
Person 2 worked for 200 minutes and checked 1,325 comments every 5 minutes.
Person 3 worked for 120 minutes, at a rate represented by
\(c = 331t\)
,
where
\(c\)
is the number of comments checked and
\(t\)
is the time in minutes.
Person 4 worked for 150 minutes, at a rate represented by
\(t = \left( \frac{3}{800} \right) c\)
.
Order the people from greatest to least in terms of total number of comments checked.
Order the people from greatest to least in terms of how fast they checked the comments.
Student Response
Teachers with a valid work email address can
click here to register or sign in
for free access to Student Response.
Student Facing
Are you ready for more?
Write equations for each job applicant that allow you to easily decide who is working the fastest.
Make a table that allows you to easily compare how many comments the four job applicants can check.
Student Response
Teachers with a valid work email address can
click here to register or sign in
for free access to Extension Student Response.
Activity Synthesis
Ask students which job applicant should get the job and why. If time permits, consider using MLR 1 (Stronger and Clearer Each Time).
Representing, Conversing: MLR7 Compare and Connect.
Use this routine to prepare students for the whole-class discussion. At the appropriate time, invite students to create a visual display showing which job applicant should get the job and why.  Allow students time to quietly circulate and analyze the selections and justifications in at least 2 other displays in the room. Give students quiet think time to consider what is the same and what is different and whether or not they agree. Next, ask students to find a partner to discuss what they noticed. Listen for and amplify observations that highlight advantages and disadvantages to each method of determining the top job applicant. This will help students identify situation when comparing rates is more effective than the sum of quantities.
Design Principle(s): Optimize output (for justification); Cultivate conversation


aligns: no