Monday, December 21, 2015

Teaching Integer Rules with Google Sheets - Addition

Integer operations confound middle schoolers everywhere. And understandably so. After all, imagine that everything you thought you knew about addition was suddenly turned on its head: numbers start moving the "wrong" way on the number line, adding two negatives gives you a smaller sum, and combining two integers with different signs can look a lot like what your teacher use to call subtraction.

A lot of the issue stems from students being given rules and memorizing them instead of discovering and making sense of them. Since math is the study of patterns, students need space to explore the patterns that happen when you combine positive and negative numbers.

Manipulatives like two-color counters and number lines are a pre-requisite to working with naked numbers. So after those experiences, I think Google Sheets provides some interesting possibilities.

I'm still working through the best way to do this, but a spreadsheet with pre-formatted functions seems like a good space for students to experiment with plugging in numbers, seeing the outcome, and deriving the patterns. It's sort of like a science lab for math: students input, observe, tweak, generalize, and then make meaning of their discoveries. In other words, they think like mathematicians.

Take a look at the Sheet below and let me know how it could be changed to help students understand integer addition. And if you'd like, make a copy for your Drive and mess around with it on your own.


How To Use It
  1. If you're using Google Classroom, attach the Sheet to an assignment and set to "Every student gets a copy."

  2. Students enter positive or negative integers in row 2, columns A and C. Anything positive will format green, negative as red to emphasize patterns. The sum will calculate automatically.

    Enter integers

  3. Next they'll use the dropdowns in columns G-J to answer the questions about the signs of the addends. This emphasizes two things: first, if addends have the same sign, the sum will have the same sign as well. Secondly, if addends have different signs, the sum will have the sign of the number with the greater absolute value.

    Answer questions about equation

  4. If the addends have different signs, columns K-M will be populated with the absolute value of the addends and the sum. Students need to think about how the absolute values of the addends are related to the absolute value of the sum, then select their answer from column N.

  5. Absolute value relationships

  6. Repeat steps 2-4 and fill in the remaining equations.

  7. When students have completed the Sheet, have them discuss the patterns they observe with a partner (try these Accountable Talk posters from Education to the Core to get the conversation started).

  8. Finally, have students go to the "Questions" sheet and explain their discoveries.

  9. Reflection questions

Again, this is totally a work in progress and feedback would be great. I just think there's great potential in Sheets to help students experiment with math concepts and start thinking like mathematicians. It's definitely worth exploring.

Saturday, December 19, 2015

Using Google Sheets to Track Student Progress

A teacher came to me last week looking for a way to quickly see the changes in her weekly student assessment data. She had been scoring each quiz, giving feedback to students, then calculating the percentage increase/decrease for each student by hand.

Clearly, the answer here is a spreadsheet. (Thanks, Alice Keeler, for burning that into my brain.)

The Google Sheet I created for her calculates the student's percent change from one week to the next, then highlights increases in green and decreases in red. It's a simple way to see how students are doing without having to bust out the calculator every Friday afternoon.

Enter scores, percent change automatically calculates

If you're interested in peeking under the hood at the functions and conditional formatting that make it run, I've listed them below the embedded Sheet.

Want to use it? Make your own copy and add it to your Drive by clicking here. Happy tracking!


Under the Hood
  1. Finding the percent change
    In the Change column, the formula for finding the percentage is to take the current week minus the previous week, then divide it by the previous week. I used =sum(-C2,E2)/E2 to make that happen. I made the previous week's score negative so that if the second week's score is lower, it will return a negative value and show a decrease in the form of a negative percent change (as in a larger negative plus a smaller positive equals a negative). In retrospect, there's probably an easier way, but I'm still pretty new to spreadsheets and that's the integer rule that came to me in the moment.

  2. Getting rid of "#DIV/0!"
    When there's no score for the previous week, the function above returns the ever-so-irritating "#DIV/0!" to remind you of what you've known since 2nd grade: you can't divide by zero. I didn't want that showing up in the change column for the weeks that hadn't happened yet, so I used the IFERROR function.

    IFERROR let's you decide what shows up in a cell if there is an error (clever, right?). To use it, surround the original function inside IFERROR parentheses, then after the comma in quotation marks, put what you want to show up instead of the error message. In this case, I wanted it to show up as "N/A". So the function in the Change column ends up looking like this: =IFERROR(sum(-C2,E2)/C2,"N/A"). In other words, if there's an error when the Sheet runs the sum function, just stick an "N/A" in that cell instead.

  3. Conditional Formatting
    Finally, after the change in score is calculated, there needed to be a quick way to see if a student increased or decreased from the week before. Enter conditional formatting, which is located under Format > Conditional Formatting in the toolbar. Each cell in the change column has four conditional formats applied to it, in this order (conditional formatting is applied sequentially, so order matters):

    If the value is greater than or equal to 0, green background, black text
    Emphasizes, in green, an increase from the previous week to the current week.

    If the value is equal to -100%, white background, white text
    This hides an unfortunate byproduct of the function in the Change column which returns "-100%" if there isn't a value in the current week. The only way this formatting could be a problem is if a student gets a 100 one week and a 0 the next, the change won't show up. If you know another way around this, let me know.

    If the value is less than 0, red background, black text
    Emphasizes, in red, a decrease from the previous week to the current week.

    If the text contains "N/A", white background, grey text
    This makes the "N/A" from the IFERROR function less obtrusive when you're looking at the entire sheet and lets you focus more clearly on the data.


Friday, December 18, 2015

The 10 Characteristics of Effective #Edtech PD


We all know that school districts often purchase technology with no real plan in place for teacher professional development. Those of us in the Edtech community beg for more time to train and support our teachers, but even then those trainings end up taking the form of one-time, sit-and-get workshops with little to no follow-up.

As I conducted research for Master's thesis, I focused on the components of effective edtech professional development. After organizing notes from a multitude of peer-reviewed articles, I synthesized the top 10 characteristics of effective PD based on their mentions in the literature.

I offer them below so we can pursue more impactful forms of professional development for our teachers (and if you're desperately interested in the reference list and full literature review, you can find it here.)

So with no further ado, effective edtech professional development needs to include...
  1. Clear, content-specific connections to classroom practice
    The most frequently mentioned characteristic of effective PD is that it has a clear link to a teacher's content area and their classroom practice. To accomplish this, we may need to restructure the way we present PD so that teachers can be clustered together based on content areas. We may also need to consider blending our PD so we present a whole group, face-to-face session on the general functions of a digital tool, then allow teachers to choose an online pathway that walks them through the applications of the tool in their content area. Whatever route we choose, the adult learner is focused on practical application and learns to solve problems, so we need to make sure we provide clear connections to their daily context.

  2. Time for collaboration and reflection
    Without reflection, there's a danger that the teacher's PD experience could be misunderstood and misapplied in the classroom. For example, if a teacher walks away with plans for implementing at only the lowest levels of integration, they've missed a chance to increase rigor and engage students. Reflection and collaboration provides time for teachers to develop plans and for us as facilitators to make sure that our intended takeaways are actually taken away...

  3. Extended duration
    The duration of effective PD includes both an extended span of time to implement the new learning as well as a high number of contact hours outside of the initial session. One-time workshops are ineffective in changing teacher practice, especially when there is little to no follow up outside of the training. Positioning our training in the context of regularly scheduled Professional Learning Communities (PLCs) or other forms of job-embedded PD allow us to extend the contact time we have with teachers and support them in their new learning.

  4. Non-threatening support and follow up
    The teacher's support shouldn't also be the teacher's evaluator. This is where the role of coaches comes  into play. The teacher has to feel that they have a partner in implementation who will respect their need for confidentiality as they incubate new ideas and attempt to execute new plans in their classroom. 

  5. An engaging and active format
    Often, if we were the teachers in our own PD, we'd be checking Facebook too. If we're not doing our part to model active learning and engaging instruction, we have no one to blame but ourselves for the slack-jawed faces staring back at us. Teachers need "sandbox time" to experiment and play with new technology, and it should happen during our sessions where we can provide structure, guidance and support.

  6. The same technology teachers will use in the classroom
    With our current Chromebook pilot, we made assumptions early on that teachers would understand how to use the devices. Based on that assumption, we moved to quickly into digital tools without making sure teachers could navigate their way around a different interface than what they were use to. Teachers need to experience the actual classroom technology to understand what student's will experience as they use the tools. Additionally, greater learning transfer will happen if what teachers experience in training matches what they will be using in the classroom.

  7.  Modeling by colleagues
    I've been out of the classroom 8 months (and here are some lessons I've learned). In the eyes of a teacher, I'm out of touch. Whether that's true or not, perception can quickly become reality. The more we can get classroom teachers presenting the PD and sharing what they do with real live students, the more buy-in we'll have from the teachers we're training. 

  8. Institutional support
    How does your campus or district show support for your early adopters? Do they allow them to take risks, make mistakes, and blaze a new trail? Or do they flog them at the first sign of a data dip, blame the devices, and remove the technology from the classroom? For PD to be effective, teachers must feel they have the support of the broader institution to take the often uncertain path of pushing through to new and higher levels of learning.

  9. Processes for evaluating teacher learning
    Exit surveys are an awful way to evaluate professional development, but that seems to be our default method to determine if PD has been effective. To truly evaluate and refine our PD, we need to find ways to see if what teachers have learned is reaching the classroom, changing teacher practice, and impacting students. How do we do that? I'm not sure. There are so many variables that go into effective teaching that it becomes difficult to tease out exactly what is making an impact. If anyone is using metrics to measure PD that are working, I'd love to hear about it in the comments section.

  10. The feeling that the time invested is outweighed by the benefits gained
    We've all walked out of training sessions that were a complete waste of our lives. So for PD to be effective, the teacher has to feel like the time they just put in will result in positive changes in their classroom. It's incumbent on us as facilitators to make sure that connection is clear, so that when teachers leave our initial face-to-face, they have plans for immediate implementation with their students.

That's what the literature says. What would you add to the list?

Friday, December 11, 2015

Techie Holidays Lunch-and-Learn


One of the issues I'm finding when it comes to training teachers in technology is the priority of other content areas. Having taught a state-tested subject and grade level, I get it: there's an immense amount of pressure to keep the data where it should be and develop teachers in their core area. However, this crowds out the time that's necessary to develop teachers in how they use technology.

One of the solutions I'm exploring is voluntary Lunch-and-Learns. Inspired by this "Innovation in Action" column by Rick Czyz, I'm calling this first run "Techie Holidays," and I'm pleased with it so far. I start by posting invitations on the door of every classroom in the building the day before, followed by an email invite. The day of the Lunch-and-Learn, I set up in the campus conference room (with snacks and gift card giveaways) and teachers come to learn a few new tech tools in about 10 minutes.

The turnout has been strong, with 70%-80% of teachers attending on each campus. I plan to do two more of these this year, as it seems to be a workable solution to getting teachers trained in the midst of all their other campus and classroom requirements.

This form of PD isn't about in-depth conversations over edtech philosophies or the finer points of SAMR, it's about relationship-building and some "quick-win" tech tools. And I've learned quite a bit about what teachers need just by sitting and talking with them over some cookies and cider.

If you're interested in using the "Techie Holidays" resources, the link to my Drive folder with handouts, etc. is below.

"Techie Holidays" Resource Folder

Techie Holidays Training Website