Division into Decimals - Undone

This is a pretty focused game and it is undone.  Even the fifth graders couldn't help me finish it... maybe a reader can help?  We were playing Manga High games with my preservice middle school teachers this week, and they noticed something.  The context can be completely silly.  They liked "the penguin game" in particular.  They thought it was mathematically worthwhile, teaching estimation.  They found the problems worth doing in the game and felt like it could help students improve their estimation and computation.  But we never really have to chuck penguins to safety.

There's something appropriate to the context.  We're approximating, acting quickly, there's the idea of what fraction of the way across are we... but it doesn't bear much scrutiny.  It's just silly and a bit of fun.  I think that's an element missing from some of my practice games.

The Game
The game premise is complete simplicity: race from one end of the paper to the other (25 cm) by drawing rectangles with area = 10 sq.cm.  Each turn your rectangle is determined by rolling the width with 2 dice.

That's it.

The Lesson
I shared that we were playing a game that had no name and no context.  I needed their help.  Immediately they began shouting names and ideas.  If I were a game designer, I would do this.  Just get a bunch of kids and let them throw ideas at you.  Holy cow were they enthused and specific.  Sadly, I had to tell them I wanted ideas for this game, and we'd have to play it first.  Me versus the entire class, like we usually do.

I showed the graph paper and explained that the goal was to get to the top by drawing rectangles with an area of 10 sq. cm.  I drew a 1x10 rectangle.  But that wouldn't be very interesting. So instead we're going to roll the width of the rectangle.  I rolled a 2 and asked, "how tall should it be?"  A couple students quickly jumped to 5, so I drew it and we checked - there were 10 squares.  We rolled for them.

Aside: that worked well enough that I would fake a 5 if doing this again.  (Faking a 2 is greedy.)

Their roll - a 7!  That's how wide it should be, but how tall? "3!" kids are quick to say. Hmm - that makes for an area of 21.  "1!"  That's only 7.  "1 and a half!" Let's check.  They talk me through 1.5x7. (Not a few couldn't recall.) Hmm, 10.5, too much.  "1.4!" They walk me through that... so close! 9.8. "1.45?" We try it and get 10.15.  Wait, I say, aren't we really doing division?  What times 7 equals 10? We started an saw that 7 goes into ten once.  "It doesn't work," someone said.  Another student said, "add a zero!" I used the notation my son has been using, which I like.  We got to 1.428, and then realized that was close enough for drawing the rectangle.  "Is it point-4-2-8 repeating?" "Will it ever repeat?"

We finished our practice game, and recorded our calculations on the white board.  When they played for themselves (mostly 2 on 2, with a few 1 on 1's), they referred to the ones we had calculated, but had also several others that needed to figured out.

In the summary, they thought the game was fun enough to play, and had good math.  25 cm made for about the right length of game.  (Hah!) They really got into trying to come up with a context. REALLY.  "Monkeys climbing!" "Monkeys escaping from sharks!" "Tiger sharks!" "People escaping from sharks!"  "You're escaping evil aliens."  "It's an alien trying to climb to the moon!" "It's ..."

OK... it should connect somehow to what we're doing.  I see why the climbing.  But why sharks?  Where is the shark chasing?  Could it connect to what we're stacking? What would you stack that has different sizes? "Students escaping an evil teacher by stacking homework!" "Books!" 

OK... maybe the game remains undone.  Maybe it should be unfinished?

Reflection
The game made a good context for modeling the division on which they needed practice.  The representation of the rectangles was supportive.  We talked about the connection between 10/2 and 10/4, for example.  They got the indirect variation aspect of it, and were rooting for small numbers for themselves and large numbers for me.  The familiarity with common division computations was good.  For such a vanilla game, it might be a nice aspect to keep it vanilla, and keep the game design aspect to the lesson.

If I was developing this into a video game, the subsequent levels would introduce some variability of the dividend also.  I also think you could have kids estimate the division.  If they overestimate, no block.  Increased decimal places would get you farther faster.  One variation that I ruled out was to have the game be a race to 2.5, so that the kids were dividing 1 instead of 10.  But then the area is .1 sq. units - not nearly as intuitive.  My next lesson would be how you can use these results to get at other computations, and to strengthen that multiplication connection.  I'm convinced that 99.9% of kids do not see the partial product connection with the division algorithm.

My 1cm graphpaper (pdf) is at Scribd if you'd like it.

Twitter Conditions

I had the good fortune to win a bet recently (well, best 2 out of 3) by the performance of the Yukon Huskies (jk) in the 2011 NCAA Division I men's Basketball Tournament.  My prize? A guestpost from Dave Coffey, @delta_dc.  (I was actually rooting for Butler, but that's a quality consolation prize!) This is Dave with Juneau.  Juneau is asking, "How could you bet on bulldogs?  Have I taught you nothing?  Haw!"

A few weeks back, one of our teacher assistants said, “You just started on Twitter this semester. I never would have guessed.” I wasn’t sure if she was talking about my quantity or quality. I chose quality and explained that it could be traced to Cambourne’s Conditions of Learning (a Foundational Framework of our Teacher Assisting Seminar).

This reminded me that John, my co-teacher, had asked me about blogging about the Conditions. I turned to him and said, “I’m thinking about writing about how the Conditions of Learning helped me to communicate using Twitter.” I thought this would be a good example of authentic learning in action.

The teacher assistant chimed in, “Maybe you could describe each condition in a Tweet.” John laughed, understanding that she had issued me a challenge without knowing it. Well, “challenge” accepted…


[Note from John - t was very tempting to put this in twitter-typical reverse order... but that would make it less readable.  Please forgive the lack of verisimilitude.]

Thanks, Dave and Jim Calhoun! And Brian Cambourne, of course.  The Reading Teacher has put the article introducing the Conditions online for download.  Or you can read the whole story in his book The Whole Story.  Also, I put the date on the cartoon at '95, the date of the RT article, but 1988 would be more accurate.

Photo Credit: Kathy Coffey, Rosaura Ochoa @ Flickr

Sites, Gadgets and Widgets

Warning: entirely a novice.  Trying to give that perspective on using these tools.

My university, Grand Valley State University, is in Michigan, a famously economically hard-pressed state.  Much like Wisconsin, any kind of education funding is suspect and under inspection.  We have think-tanks requesting faculty emails, and newspapers and TV stations soliciting financials.  (The financials are public info - no worries.  The emails - creepy.)

We got an email from the administration with some information to contest the spin being put on the data, and I started wondering about making it a webpage.  So I used it as a chance to practice with Google sites, embed a Google spreadsheet, and a Wolfram|Alpha widget.  Unfortunately, you can't embed a W|A widget directly, you have to wrap it in a Google gadget, then embed it in the site.  This site was very helpful, and the whole process boiled down to pasting the W|A javascript code in the Google gadget builder. I was using the builder at this page, just adapting their most basic example.

The W|A gadget was pretty easy to manufacture, following their steps.  After entering a request, you'll see options for sharing.  The far right W|A sigil starts the widget builder.

The thing that took me the longest to get was just me being dense.  To get at component properties, select a component in your proto-widget.  And then the settings will show in the bottom left.

Then to get the embed code to paste in your blog (will work directly) or to put in the gadget to put in a google site, click on the code button in the embed box on the finished widget.

The (sort of) finished project is here: Facts and More: How does GVSU stack up?

And, of course, I'd happily take any suggestions for improving that page.