Last year, Kevin and I taught a yr 7 digital technology module based around the digital technology curriculum. (If you like, you can read about our efforts here and here). Part way through last year we got a new Technology HoD, who has ‘encouraged’ us to include more from the technology curriculum, and we are reporting based on the technology curriculum rather than the progress outcomes like we did last year. This was a real challenge for me and took me a bit to get my head around – being a science teacher I knew the sci curriculum pretty well, and I have spent a lot of time working on being more familiar with the digit tech curriculum. But the technology curriculum was a whole new experience and initially I really struggled to get my head around it, especially ‘planning for practice’.
So, I went and tried to learn up. And slowly but surely I think I’m finding my way – a work in progress shall we say.
Planning for Practice
The CD for Tech (who is awesome, fyi, it has been good to be challenged and have crunchy conversations and to try new things) asked if we could ‘assess’ on planning for practice so across all the yr 7 and 8 modules they have a range (our modules are 6-7 weeks with 4 periods a week).
And with a bit more detail, thanks to TKI
I also used this resource from TKI which explains planning for practice in a bit more detail, and got some exemplars from TKI and from the other technology teachers in the school
Essentially, I figured out that Kevin and I already did some of this without making the learning explicit. To try and make it more explicit, I modified a TKI resource and asked the students to do a little more planning around the minecraft design than last year.
We got some nice examples of planning and work 🙂
But (there is always a but!!) there were a couple of things that hindered us this time. One was the students got SO excited building in Minecraft that they often forgot to record changes they had made, or progress they have made into their Onenote. We have a policy of if it isn’t in the Onenote it doesn’t exist, but in this case there has been some fabulous learning that didn’t get recording. So I am having a wee think over the next 2-3 weeks (before we get to this in the next module which starts on Thursday) of how else I could record this? There were such rich discussions occurring with the groups building collaboratively that I just didn’t capture…..
AND I need to modify our template a little more. I hadn’t used one like this before for this purpose, and see now it doesn’t quite fit….And we also ended up running out of time to do this properly, we thought we had 6 full lessons and ended up with 4 (because schools have things come up!) so we will try to get a full 8 lessons for the next module
Fortunately, we also did some planning with algorithms and coding with the microbits so we can make a holistic judgement around students abilities to reach an outcome from their evidence portfolios. And we will tweak it for next time 😉
So, again to ensure that across all the junior modules, we adapted the module to cover inputs, transformations and outputs.
And again some more details from TKI
This was way easier to incorporate, given we had already been doing a lot of it without realising.
Through out the module we spent a little more time on inputs and outputs around the microbit, and when introduced the topic. We also included some questions in the ‘form’ we used for an assessment
Progress outcomes for digitech
We still also incorporated progress outcomes from the digitech curriculum around computational thinking. We covered data representation with binary and ASCII code. We walked through algorithms (love making toast) and did some coding. with hour of code and with the microbits. Kevin put some of this into the assessment as well so we had a bit more ‘hard data’ around whether the students understood the aspects of code in addition to their evidence portfolios. It wasn’t a memory test, students were encouraged to copy the code and test it to see what it did.
What the students thought
We gave an end of module survey, and generally got positive feedback. Minecraft was a clear favourite with the students
And it was really heartening to see that some students picked up on prototyping and multiple ways, although most felt they gained skills in simple coding and using office 365 (which is awesome, as these students are new to TC this year and getting them upskilled with office 365 is really awesome as an ‘offshoot’ of the module.)
So overall I think it was a good first go. We do need to tweak the planning template, and I’d like to find a way to get students to design a success rubric (we ran out of time this time round). And I’ll keep working on building my own confidence and understanding of the technology curric.
Would love any ideas/feedback as we work through, or happy to talk it through if you are doing something different