Data driven structure for exam prep

Item Analiysis

I have a Regents prep course (basically students that need to pass a New York State math exam in order to graduate) that I have been teaching all semester. These students are about six weeks away from the exam. I’ve decided to adopt a new structure to help them get over the hump of passing it. These kids are a challenging bunch, but their attendance is solid and they have good attitudes.

Every Monday, starting this past Monday, I will give them a simplified mock Regents exam. This will essentially be a diagnostic: it will not effect their final report card grade. My students usually buy into this pretty well. I will use the results of this assessment to identify which concepts we will focus on for Tuesday, Wednesday, Thursday, and Friday. During these days my co-teacher I will reteach and review these concepts, pretty much one concept a day to keep it simple and bite size. The following Monday we will repeat this process with an exam and using the rest of the week to tackle four more concepts (hopefully not needing to repeat those that we had previously relearned).

This targeted, structured, data-driven approach is something I’ve been seeking for this class for a little while. I’m consistently using data analysis for all my classes and I knew I was going to take this approach with them, I just didn’t know how it would look. Now I do.

After looking at the data from today’s exam a short time ago and mapping out the concepts for the week, I am really excited for the benefit this structure could provide my students.

Concepts for the first week:
1. Identifying trigonometric ratios from a given right triangle
2. Translating verbal statements into mathematical expressions
3. Basic operations on polynomials
4. Writing equations of lines and their graphs

Ready. Set. Go.

bp

Blind Trust

I attended Math for America’s Master Teachers on Teaching event last night. If you’re not familiar with it, it’s essentially a Ted-ED style event where math teachers give presentations on topics that they are passionate about. One of my biggest takeaways had to deal with technology and how I address how my students use it.

There were some awesome presentations and one that stood out to me was Patrick Honner’s talk about the shortcomings of technology as it relates to teaching and learning. A couple examples that Patrick pointed out were the TI-84’s inability to accurately represent continuity (asymptotes) and Desmos’s failure in representing holes in polynomial functions. Normally, technology allows beautiful, helpful representations of mathematics, but in all of these instances technology utterly fails to do this. Patrick encouraged the audience to embrace these types of pitfalls as teachable moments that could enable deeper understanding of the concepts.

This whole discussion reminded me of something that happened in my class a while back. Once during an exam, I witnessed a (precalculus) student enter “1 + 2” into their calculator as they solved a problem. In the moment, I almost laughed out loud (and afterwards I did). The next day when I handed back the exam, I brought my observation up to the class. The guilty student openly took ownership of the act and said:
“Mr. P, on an exam, you never know!

This example is slightly different than the ones Patrick highlighted, but it nonetheless brings attention to my students’ increasing dependency on technology. This connects with what was Patrick’s concluding point: our students blindly and inherently trust most all technologies they use – more so than they trust their own intuition. Combining this with technology’s pitfalls, and I see a recipe for disaster: students wholeheartedly trusting a flawed tool.

This means that I have a crucial responsibility to transform student reliance on technology into teachable moments that enable deeper understanding. It also means that if my students blindly trust technology and all it’s shortcomings and fail as a result, I have also failed.

bp

For a long time

For a long time, I taught my students in a way that I thought was effective.

During the last couple of years, I’ve now discovered that I was all wrong. I actually made this revelation two years ago while “flipping” my classroom.

Student learning is best when it comes from complex, indefinite situations and then, after contemplation, taken to broader ideas and concrete generalizations. When learning begins, students should be confused and perplexed, or at least unsure about what is going to happen during a lesson. The problem comes first and the solution/generalization later. I think this really stems from how we, as humans, learn on an everyday basis.

Let’s say I’m confronted with a problem, like back pain. When my back starts to hurt, I immediately begin thinking about why. I’ll probably ask myself many questions and if I injured myself during that dunk I had over Lebron James. Or was it Carmelo? Either way, I’ll try various solutions like adjusting my sleep patterns, changing my exercise routine (no dunks), and using my knees more instead of my back – all to try and alleviate the pain. Let’s say that I struggle for a while and nothing seems to work.

Over time, I begin to realize a pattern. I notice that every day I wear my old, worn out sneakers, my back hurts at the end of the day. And on days when I don’t wear them, I feel fine. So I conclude that my sneakers are the problem (and not my dunking). They seemed to have caused my joints misalign causing a chain reaction to my back. I toss them and get a new pair and my back pain goes away. Also, I learned that moving forward I should replace my sneakers more than once every 7 years.

That was a weird example, but whatever. It still sort of frames how “normal” learning happens.

When confronted with a problem we use our inherit problem solving abilities to find solutions. It’s natural to be perplexed initially and to later understand. In no way is someone going to come along and immediately present a solution for my back pain. Similarly, neither should I, as a teacher, initially provide clear theorems or concepts to students as solutions to problems I will soon give them on an exam. In a math class, we should have them identifying problems and use problem solving abilities to find solutions and generalize ideas. This doesn’t necessary mean real-world problems, just critical thinking situations overall.

I didn’t approach teaching and learning in my classroom like this for a long time. Sometimes now, even though I value the approach, it’s still hard to for a bunch of reasons. But now I try to do everything I can to teach discovery-based, problem-based lessons.

Oh, and I DID dunk on Lebron. Once. Then I woke up.

bp

The Quotient ~ 11.14.14

Whew.

What an incredible few weeks it has been. A school year of four preps, among other things, has finally caught up to me. Yes, four preps. Here are the things that having running around in my head over the last several weeks.

1. Student questions. When I get a lot of them, I’m pleased because I know my students mind’s are stimulated. But how to handle all those questions can be a challenge at times. What about when there are no questions?

2. Checking for student understanding during the lesson and adjusting on the fly. Basing the direction of my lesson on their level of mastery on any given day.

3. Relations with administrators, new and old. I’m learning a great deal about this dynamic and it’s impact on me and the overall school community.

4. Listening is a very underrated skill.

5. Including the proper scaffolding into each lesson. Specifically, having multiple entry points for students at the onset of learning.

6. After an assessment, the value of data analysis. Numbers never lie. Also, how structured analysis (time and protocol) can really help reveal the story behind the numbers.

7. Related to above: point biserial.

8. Always remember that kids are kids. Relate to them, laugh with them, have fun. They’ll enjoy your lessons a lot more – and work harder for you too.

9. I let one of my students borrow one of my ties to wear at his interview with Harvard University. Very cool. Awesome kid.

10. How much my use of Desmos has increased. I’m literally using it every day.

11. Reflect as much as possible. You’ll grow in ways that you otherwise cannot. Even just 10-15 minutes of concentrated reflection is substantial.

bp