We write our own reports?

Ever had an idea you just had to act on?

Today with my year 10s, we had 15 minutes to ‘spare’ after we de-briefed their yearly exam paper. Just then, I had a thought to get them to write their own report comment. I figured ‘why not?’

So, I asked my students to spend the next 15 minutes drafting a 500-character report comment for IST. I mentioned that I have already drafted their reports – which was true – and that I wanted to make sure I did not miss anything – which was also true – and that I would use their input – which was more or less true.

One of the more astute ones asked, “Does that mean we write our own reports?”

Boom!

I replied yes, of course. I write the words but in fact, what they do (or not) throughout the year is what is written in the report comment. So technically,  students do write their own reports. Right?

Awesome as they are, they humoured me and actually did the activity.

It was an authentic context to reflect on the year that was, how they were as learners in my classroom and even how they could improve. No scaffold. No prompts. No advice from me….just the time and space to do it…and a bit of ‘rah rah’.

I was so pleased by their honesty and accuracy of self-assessment. I was also pleased that my report comments got validated by theirs which, for my part, means I do know my students and that my data collection (via formative and summative assessments) and feedback systems work.

Writing reports can be onerous, often due to sheer volume and tight deadlines. This has been a ray of sunshine.

I would do this again as a win-win activity. That is, students reflect meaningfully on their learning – content and process and I, their teacher, gets validation and more importantly, personalised insights about them.

 

I do and I understand

Confucius says (oh my, I’ve been wanting to do that for ages…haha):

I hear and I forget. I see and I remember. I do and I understand.

In my random clicking on the internet disguised as professional development (or maybe it’s the reverse), I found a couple of strategies interesting enough to try.

Fishbowl

The first came from an Edutopia video, How to teach maths as a social activity. I’m a big fan of cooperative and collaborative learning and this video has good strategies. What I wanted to try immediately was called Fishbowl (video link). Basically, it’s having a small group sit and discuss while the rest of the class observe. I’ve heard of it before but this is the first time I intended to give it a go.

With my year 10s going into their exam block next week, and coming in from a 2-week school holidays, I thought that Fishbowl would be an interesting way to do some revision. So I set up 3 groups to discuss (1) Bias in algorithm, (2) Use of cookies, and (3) Robotics in employment.

These topics are directly related to the topics we did this year (1) Software Design and Programming, (2) Internet, and (3) Robotics.

I gave them 5-10 minutes to do a quick revision using our class notes or to look up on the web. This had to be done individually, i.e. no discussions. Then, the group took turns to be in the Fishbowl.

While I set this out as a revision exercise, what I found was Fishbowl is also an effective assessment activity. I doubt I’ll use it for summative assessments but as formative assessment, it was really good to see what the small group, and whole class, knew…or did not know…or got confused on. It also contextualised my assessment tips such as – give specific details, use technical terms and make sure you know their definitions, think of positives and negatives when discussing issues, you can link topics we studied,  use Asimov’s Laws on Robotics when discussing issues, and the like.

Tic Tac Toe + Jeopardy

Our current unit of work in 9IST is game design, a culmination of the Digital Media and Software Design and Programming topics we studied this year. They also have a yearly exam coming soon and I thought what better way to do revision than to play games. We will unpack the following experience next lesson and use that to feed into the work they yet have to do.

I found my inspiration in a recently discovered (read: yesterday) differentiation site, daretodifferentiate (link to Choice boards or tic tac toe, though the wiki site warrant more exploration). I wanted to try it straight away but all mu units are already designed so I figured I might as well use it for revision….and as a game!

The plan was to have a choice board with easy, medium and hard questions – that’s the tic tac toe part. Assigning points to the questions was the Jeopardy part.

I’m not going to include all the questions here but here’s a small sample so you get the idea: easy – JPEG is a lossy format (True or False?), medium – Define algorithm, hard – Explain one way that text can be digitised. For points, I gave 100 for easy, 150 for medium and 200 for hard.

Using the simple definition of games = goal + rules, I discussed the rules of tic tac toe and Jeopardy. They work in groups, nominate a speaker (and there can be no repeat speakers) to provide the answer. I also added a rule of ‘stealing’, i.e. if a group can answer a question better then they “steal (the chance to earn)” the points. This was actually good to ensure they all tried their best and that they listened to other groups. Revision and learning were happening at individual, small group and whole class level. Granted, still at different levels but even the quietest student could learn from others at least. I dropped the ‘tic tac toe’ all in a line across three columns because I had 3 groups…but that would be fun to design to get some blocking strategy happening as well.

Speaking of designing the thing, I wanted to implement this in Scratch, or with more time and effort – JavaScript or Python perhaps. But, given that I thought of this on the eve of using it, I resorted to a table in PowerPoint and using animated blocks to hide/reveal the questions. It’s been a while since I used the ‘click on object’ as trigger (default is just click anywhere) that I’ve forgotten about it. On the whole, it worked quite well actually….yep, a PowerPoint hack 🙂

Even with a short activity, I can see the power of differentiation through choice….and of course, I’m convinced about cooperative and collaborative learning anyway.

9IST groups in a huddle, discussing strategies and answers

9IST groups in a huddle, discussing strategies and answers

Back to Confucius

There are so many teaching and learning resources out there and seriously, there are many good ones. Finding ones to try and then actually making it happen help cement them in my mind because I don’t only know of, I also understand.

Also, because I mostly teach via Project-Based Learning, my students have done the ‘do’ bit and yet, as I’ve uncovered in these revision activities today, they don’t always remember or understand. And so then, back to Confucius:

By three methods we may learn wisdom: First, by reflection, which is noblest; Second, by imitation, which is easiest; and third by experience, which is the bitterest.

Revision (look at again) – as an example of reflection (look deeper perhaps over-and-over from different perspectives) – has shown a path for remembering and understanding. In writing this blog post, tired as I am after an all-period teaching day on the first day back at school in 35C heat, I have forced myself to revise and reflect on these strategies.

Ah, I feel wiser now…haha

What did they learn?

This post is about my 9 IST 2014  Game On project originally premised on the notion of making the world more humane (see links for related posts). This was essentially a project-based learning approach (PBL) and it had the 8 essential elements of PBL according to the Buck Institute of Education (BIE), a PBL leader.  It’s tempting to see how I’ve done against that checklist and I dare say it was a good PBL but what I really want to do here is ask the harder question of whether or not this project has achieved what I set out to do.

That is, has the project somehow made the world more humane?

Have the process and product of answering the driving question – “Can developing games help develop resilience?” – somehow created a more humane world, on top of achieving curricular outcomes?

The previous Game On event post has partially answered this … and it is a YES. Connecting with others. Making time for play and enjoying it. Celebrating achievements. Laughing out frustrations. Giving feedback. All good stuff and all told from my perspective.

Let me share what my students said. I used one of  Harvard University’s Project Zero Visible Thinking Routines, “I used to think…now, I think” as a student reflection tool. I’ve quoted a few below but if you want to read more, find it here – SDP reflection (PDF).

on Game Design

I used to think… now I think…
Would be pretty easy as there are so many games already made It’s challenging but now I realise how creating a game isn’t so simple and coming up with a new idea is not as easy as you think. However, designing games is a rewarding process and is absolutely fun.
It is easy to come up with an idea and develop a game and it is the programming and algorithm which is the difficult part in the game designing process. That coming up with ideas take up a lot of patience and skill. It is vital to come up with an idea which has a vitally fun and interesting output. It is essential to consider how the gamer or viewer will find the game as well.
That games you could just tell the computer what you wanted without having to use certain blocks and that it would be quite simple once you have an idea, it would do the rest for you. Actually, there are specific instructions you must use to make games. You have to be determined because sometimes things don’t work and you have to try again.

on Software design and programming

That software design and development has to strictly follow the design process of design, produce, evaluate. That evaluation is the most key part of design as it enables communication between the designer and user.
That it was really boring and that there wasn’t really many things you could do with software. Also, that people just made things that already existed and that it wasn’t helpful or fun. Software design and development is very good and useful and there is so much you can do with it that is not already created but you make new things and new ideas.
It really only involved one person and that you always typed in binary. It involves a whole group of people for it to be successful. Now I know there are many other computer languages that you can use.

on being a Software Designer / Developer

That it was a simple and mindless job people did and that it was boring and stressful. It takes a lot of creativity and thinking to be able to design and produce something. Also, that although it may be stressful, it’s a lot of fun and incredibly rewarding when you see your finished product.
That in order to create a good idea, it was only the creator’s mindset or viewpoint on it that shaped how it turned out. That repeatedly seeking advice and information is important to keep you on the right track. Reviewing your work from different perspectives help in taking your creation to a new level.
You didn’t need to know much maths. Never have I been so wrong.
It involved a set of rules to need to follow to do your job. It involves more creativity. Successful games have creative people who made them.

They’re thinking of software as a creative process and tool.

They’re thinking of and “using” others.

They’re thinking of writing games for others to enjoy.

They’re seeing challenges – and perseverance – as a way to learn.

They’ve realised that their thinking has changed.

 

This being the last teaching day in 2014, it is good to reflect that teaching can be good. It’s not always good but good times, like this, make up for when it’s not so good.

Perhaps a relevant recap to where this “journey” started with a quote from John Maeda (Make it more humane) is this new video by @veritasium looking at the on-going search for technology to revolutionise education, and I quote…

The foundation of education is still based on the social interaction between teachers and students. For, as transformative as each new technology seems to be…, what really matters is what happens inside the learner’s head and making a learning think is best achieved in a social environment with other learners and a caring teacher.

 

Make it more humane

“Don’t make the world more high-tech, make it more humane.”

This quote is from a Fast Company article, 10 Crucial Lessons From History’s Graphic Designers, attributed to John Maeda. I’ve never head of Maeda before but the quote really struck a chord with me as this is exactly what I’ve been pursuing in my IST projects this year.

For example, year 10s tried to answer ‘How can multimedia help engage learners?‘ They are also currently working on “How can robots help solve the plastics problem?” Year 9s tried to answer “How can digital movies help address teens’ problems?” and this year’s crop of videos are particularly good. Year 9s are also currently working on Game On 2014, which will be bigger and better than Game On 2013.  I actually launched the year 9 project with the quote above and Jane McGonigal’s TED talk on building resilience (strengths) through video games. One of her most salient points is this:

Good games should …bring out [the best] in players…courage, creativity and empathy…really tap into strengths.

That is my current challenge to year 9s. I’m excited because I believe this class gets this ‘humane’ thing. They are girls who understand the beauty of a flower as Richard Feynman puts it, in the context of computing; they will never look at software in the same way again. This is more of the ‘make it more humane’ stuff. Learning Science helps us understand the world we live in; ipso facto, learning Computer Science helps us understand the digital world we live in…and in understanding, we have a better hope of engineering a better world, digital or otherwise.

What I’m seeing is increased engagement, particularly with year 9s and I feel I struck a goldmine in engaging girls in computing. The catalyst for blogging about this is the story of the women behind Vidcode (Alexandra Diracles and Melissa Halfon ) – where they talk about what it could be like if there were more women in computing along with their journey as a startup company. They echoed some of the issues mentioned in Fortune’s Why Women Leave Tech article. I am hoping these Vidcode women never leave tech, and instead continue to build more humane tech….better futures.

A more humane future, a better future, or preferred future (in ACARA’s Technologies curriculum parlance) is possible and worth pursuing. This is why I am passionate about increased diversity in computing and at the moment, I’m working on addressing the pipeline though issues remain in the industry (re: why women leave tech – read it). And while I still maintain the question ‘why is it so hard to get girls to study computing?’ (a post written just over a year ago), I feel somehow that I’m moving towards the right direction. Some of the strategies I shared in that post are working for me and it feels good to look back to it a year later and be able to see positive changes.

There is hope.

Footnote:

According to GoodReads, the actual Maeda quote is:

“The problem isn’t how to make the world more technological. It’s about how to make the world more humane again.”

This isn’t just about teaching, learning or using technology. It’s not just about integrating technology. It’s about creating technology to make a more humane world…and you don’t have to work in IT to do this….more likely, it would be work with IT for the vast majority…so, a bit of computer science for everyone, yes? (go on, read the Richard Feynman link above).

Shall we?

Multimedia PBL and wrestling with the marriage problem

After a term break from PBL, I’ve gone back to it with both my 9 and 10 IST classes. I’ve been meaning to share the ‘idea’ but just haven’t got there (Is it really week 4 now?). Anyway, I’m glad I’m doing PBL again now as well as incorporating some of the things I’m learning as I do my Masters in Special Ed.

So then, in this post I’ll share my 10IST PBL plus a (rough) lesson plan that targets content (IST: problem definition, GUI design) as well as an example of teaching approach that promotes active response (one of the effective teaching principles I’ve learned about recently).

PBL

PBL_HowCanMMengageLearners

We’re about a third of the way in and most of the theory have been covered (via direct instruction) by  now. However, I’ve noticed that while students ‘get’ the idea of what engagement looks like or what ‘good’ GUI looks like, I wasn’t convinced that they’ve wrestled with it enough to apply in their own projects.

(rough) Lesson Plan

So I designed this lesson to show how a topic could be presented online in three different ways. The topic is a probability problem popularly known as the marriage or secretary problem.

I divided the class into discussion pairs.

First, I showed the wikipedia version which provided a  brief description of the problem. Discussion was first done in pairs and then as a class. This is the first time the class have heard of the problem so there was a lot of “I don’t get it” and a few, “yeah, I’ve encountered that problem heaps of times”.

Then, I showed this academic article version which provided, as expected, a more academic description of the problem and solutions. There were ‘whoas’ as we scrolled through the voluminous and dense text blocks and equations. Again, discussion pairs followed by class discussions. We got to unpack some of the GUI principles to do with form, function, navigation, layout, etc. just by comparing this with the wikipedia version. They were applying the content previously learned, both in terms of concept and language. Their analysis of GUI design is becoming more sophisticated and this is awesome.

Finally, I showed this NPR article with a sensationalist and attention-grabbing title of How to marry the right girl: a mathematical solution (thank you @fawnpnguyen for the inspiration!). We went straight into class discussions on this one and highlighted which GUI principles made this one more engaging, including the use of graphics and share/comment buttons – a feature they may well include in their projects.

There was also a bit more discussions when one of the students piped in that she thought the wikipedia version was more engaging with its neutral tone and predictable structure. This emphasised one of the key things in the design process, i.e. problem definition and how wikipedia addresses a different problem (and audience) than the other two. Engaging‘ then, is relative (gotta love those lightbulb moments). Therefore, as they set off creating their own solutions (project product), they need to be mindful of the problem they are actually trying to solve.

Then, I asked them to create their own version of the topic in what they think is engaging. Students challenged themselves to learn more HTML and CSS tags and JS scripting, based on what they want to learn and incorporate in their own projects.

Sometimes lessons work according to plan, if not better. This was one of those. It can be better but I sure was pretty happy with it.

Discussions in pairs and whole-class with plenty of opportunities to raise and answer questions as well as working in pairs with plenty of opportunities to synthesise are strategies for active response to help with learning engagement. Students are constantly wrestling with the content from different angles. 

An exciting footnote:

The student who preferred the wikipedia version went on to do more research on the marriage problem because she really wanted to understand it (she was in the minority, I assure you, but enough to make this ex-maths teacher a little bit happy). And in doing so, has illustrated yet again the beauty of tangential learning and the power of inquiry driven by curiosity.