SWBAT graph functions represented symbolically, and interpret key features of those graphs in terms of a context.

Now that students have some practice with function notation, it's time to create some tables and graphs, and see what we can see!

8 minutes

One purpose of this week's sequence of lessons is to encourage students to move fluently between the representations of functions. So while yesterday's opener asked students to evaluate a few rules for two different inputs, today they get two tables of values, and must write the rules. By moving between the different representations each day, I want to give students their own space to see which tasks are easiest for them, and which are more challenging; I want them to be aware of which representation works best for them. I pay attention to this. For example, when a student is quiet during one opener, but eager to contribute to our work on another, that's important. I try to show students how to pay attention to their own thinking as well

Today's opener is pretty straightforward, and as a group, my students should be able to handle this task pretty quickly, so I don't expect to spend too much time on it. There are couple of blanks in each table that need to be filled in, and then the task is to write algebraic rules for each. The first table is generated by a linear function, and the second one is exponential. I want to make sure that students notice that the input column is counting by 2's in the first table, and I check to make sure that they can accurately determine the slope of this line.

Kids may slip back into the language of arithmetic and geometric sequences. When this happens, I make sure to provide the equivalent terminology of linear and exponential functions.

30 minutes

**It's a Work Period**

Today is the third day that students will work on the Spending & Saving Project, and first and foremost, it's a work day. So if kids need time to work on Part 1 of the project, they'll get it (you can read about Part 1 of the project here and here). When a student is ready to move on, they let me know, and I introduce them to Part 2. Wherever they stand, I try to check in with each student to answer questions and to continue to encourage them to interpret the mathematics in the context of each problem situation.

I use today's agenda to guide students through what they've done so far and should do next. Students must complete each part of the project before receiving the next. I've posted each part of the project at the bottom of the agenda, which gives kids a picture of how the project works.

**Part 2 of the Project**

When they're ready, students start on Part 2 of the Spending & Saving Project. The task is to create a table and a graph for each of the function situations that was introduced in Part 1. Here is my video description of this part of the project. When students get to work, there's this beautiful array of cross-referenced documents, that lead to all sorts of productive conversations and idea sharing. Often, I'm able to stand back and let it happen. As in previous days, I just circulate and make sure that kids are able to provide a contextualized interpretation of what they're doing.

**Scale on Part 2**

Determining how to appropriately scale the axes is an important part of this project. Students have been working with number lines and scale since the first month of school (please see September's Number Line Project), and they continue to apply these skills now.

I have two go-to pieces of advice for kids. First of all, I want to be able to see the y-intercept on each graph. For the linear functions, I want to see the x-intercept as well, so both axes should be scaled accordingly. For the exponential functions, the y-intercept will do (we're dancing around the idea that the x-axis is an asymptote on the exponential decay problem), and it's appropriate to count by 1's on the x-axis.

If they need the second piece of advice, I tell students to count the length (in number of grid squares) on each axis (they're both 30). Students should divide the number they need to get up to (it depends on the problem) by 30, and then round up to a nice counting number. It's interesting to see that some students will, for example, divide 8000 by 30, and then take the time to carefully count by 267's on their vertical axis. I want kids to see that this is not wrong, but it's also not too efficient.

I am including here two photographs of notes that I've given on the board, a day or two after today's lesson: Part 2 Scaling i and Part 2 Scaling ii. When all students have had a little time to get started on this part of the project, I'll take a little bit of class time to work through this example. I want students to be able to provide context for each of the intercepts, and I also want them to see that it's unnecessary to plot every single point on a linear function.

**Recursion**

One additional note about filling in the tables: my kids don't have access to a graphing calculator like the TI-83. If they did, the task of filling in the table of values would be different. Most kids come equipped with simple arithmetic calculators, scientific calculators like the TI-30, or the built in calculator programs on their cell phones. I show them how, on most calculators, you can use a recursive definition of a function by entering a starting value, then an operation, and repeatedly pressing the "=" button. This way, as long as you don't lose track of how many times you've hit the equal sign, you can pretty quickly get a set of consecutive outputs for a function.

5 minutes

With about five minutes left in the class, I ask for everyone's attention. I applaud students on the work they've done today, and I might give a few shout outs to individual students who have worked particularly hard, helped others, or gained new insights.

Then, I tell students to take a moment to gather their work, assess what they've done so far, and decide what they need to work on tonight. "You all have homework tonight!" I say. "It's different for each of you, because you're each at a different point in the project, but I expect that everyone can finish whatever you're currently working on tonight." Sometimes, I give a specific time suggestion, like, "Everyone should do 30 minutes of math homework tonight." I find that suggesting a *maximum* amount of work can make homework seem less daunting to kids. "Sure, it's hard to do piles and piles of homework, for hours upon hours, but what if you commit to working for 30 minutes tonight, and see how much you can accomplish?"