OU blog

Personal Blogs

Christopher Douce

AL moderators training: using OU Live

Visible to anyone in the world
Edited by Christopher Douce, Monday, 21 Nov 2016, 15:12

The university makes extensive use of a software tool known as OU Live, which allows tutorials to be delivered over the internet. OU Live is, essentially, a branded version of a conferencing and teaching product called Blackboard Collaborate. In the next few years or so, this tool will be replaced with something else, but before this happens tutors are regularly encouraged to attend a series of online training sessions.

Despite being relatively familiar with OU Live, I decided to book myself onto one of these sessions. This blog post is a version of some rough notes that I made during and after the ‘AL moderators’ course that I went on.  (I took these notes back in May, and I’m writing this blog in November, so I hope I can remember everything correctly!)

My main comment is: if you’re an associate lecturer, and you need to deliver the occasional OU Live tutorial, either by yourself, or with other tutors, do try to find the time to book yourself on this course. It’s a pretty useful and it won’t take up too much of your time. It’s also a really useful thing to put on an application form for any other tutoring role that might take your fancy.

Notes

There were three sessions. The first session began with a set of introductions: I really liked the approach that was taken. All participants were asked to put up their hand by clicking on the ‘hand raise’ button. This had the effect of creating an orderly queue of who is going to speak. During the intro, the facilitator got everyone used to turning the ‘talk’ button on and off (which has the effect of preventing background noise). I’m going to term this practice: ‘good microphone hygiene’.

The facilitator had prepared a number of slides and used an interesting technique to create an animation: parts of the slide were covered up with squares which could be dragged out of the way to reveal answers (or other types of information). By way of analogy, think of a big piece of paper that was covered with pieces of card. It was a neat trick!

We were shown how to use OU Live pointers. I tend to use these quite a lot, since they can make things interesting. You can emphasise different points, and move different types of pointer to different parts of a slide.

An interesting open question given to all participants was: ‘What are you looking for from this module?’ It’s a really neat question that gets us talking. Different participants had different perspectives, and the answers allowed the facilitators to create a session that was specialised to those who were attending.

A topic that is regularly discussed is the use and etiquette about recordings. The policies for recordings are not as well defined as they ought to be, but I hold the simple opinion that tutors should always make recordings. In my eyes, recordings have three uses: (1) they help students who have not been able to attend, (2) they can help students who have attended who want to listen to stuff a second time, and (3) can advertise how engaging sessions are, and what a student might miss if they don’t attend a live session. (I don’t hold the view that if you record a session students won’t bother to come along).

Regarding the third point, I remember that there was a discussion session, where the recording was turned off, and a timer was turned on. The timer is a countdown timer, which makes an audible ‘ping’ sound when the time runs out. Two thoughts were: those students who are not attending the live session will miss out on this bit, and ‘I’ve never used a timer before, and it looks like a really useful feature!’

Looking at another tutor’s OU Live session (or teaching practice) really helps you to think about your own. One thing that struck me from the Tutor Moderator’s session was how much space was given over to questions. My own practice is slightly different; I tend to ask for questions at the end (after turning the recording off, to allow students to speak freely). I don’t know whether there is a right or wrong way to do things.

One of the most memorable parts of the course was the bit about breakout rooms. Breakout rooms are virtual spaces where participants can chat between themselves, usually to discuss a predefined issue or problem. Facilitators can also share whiteboard slides to breakout rooms, and can also collate slides from breakout rooms into the main presentation; imagine giving pairs of students’ big pieces of paper which they can write onto during their chat. We were encouraged to click and drag participants between different rooms.

Towards the end of the session, we were asked to consider the difference between ‘ice breaker’ and ‘warm up activity’. I hadn’t ever heard the term ‘warm up activity’ before. I now understand it to be something that a student can do in the moments before the start of an OU Live session. An example might be a message on a whiteboard that goes: ‘write your name, and where you are from’. A warm up activity helps participants to become familiar with the OU Live interface and how it works. An ice breaker, on the other hand is, of course, might be all about talking.

The next step was to share a bit of ‘online teaching’ with someone else who was on the course. Since beginning to study for a PGCE at another institution, I’ve learnt that this kind of practice can be known as ‘microteaching’. In the context of this course, I have to confess that I found myself too busy with various admin activities to complete this bit, which is a shame. If you do this tutor moderators course, don’t repeat my mistake!

Final thoughts

A couple of interesting questions to ask are: ‘what did I get from doing this?’ and ‘where would I use what I have learnt?’

The most useful thing that I learnt was about breakout rooms. Before this session, I didn’t really know how to create breakout rooms, and I found the opportunity to practice really helpful. The idea of dragging live students around on a screen into virtual rooms is pretty terrifying, but it’s a whole lot easier if you’re doing this with a bunch of fellow tutors who are just as befuddled as you are.

Would I use the ‘using white squares to hide bits of the screen’ technique? Probably not. It was a neat idea, but my own practice is to very carefully prep some slides and to use pointers a lot. This said, it’s an interesting technique, and one that I will think about.

I really liked the idea of a warm up activity. I might give this a go.

Since attending the tutor moderator’s course, I’ve used breakout rooms twice. I ran two cluster briefings. A ‘cluster briefing’ as I call them is an online meeting where all the tutors in a group tuition cluster informally discuss tutorial plans. If you are an associate lecturer, and you’re reading this, and you would like a cluster briefing before the next presentation of your module, do ask your staff tutor to run one!

Another question is: ‘what next?’ Or, put another way, ‘what would I like to do better in OU Live?’ The answer to this is ‘team teaching’. At the time of writing, there isn’t any guidance about team teaching best practice with OU Live. Perhaps I’ve stumbled across a whole new research project… Do get in touch if you’re interested in collaborating! 

Permalink
Share post
Christopher Douce

The perfect OU Live session

Visible to anyone in the world
Edited by Christopher Douce, Tuesday, 1 Sept 2015, 11:25

This is a quick summary of a meeting that occurred on Saturday 27 June 2015 at the university's London regional centre.  The aim of the meeting (or session) was to think about a thought experiment, namely, 'what should the perfect OU Live session look like?'

If you've stumbled across this post via a search engine, then I should (perhaps) say something about what OU Live is: it's a tool that tutors can use to deliver on-line tutorials to their students.  Think of it a bit like Skype with a whiteboard and a bunch of other useful controls (such as a 'happy face' button).

This session was attended by around twelve experienced associate lecturers, all of whom had used OU Live quite extensively with their students. 

This, in essence, is what they said a perfect Computing/ICT session might look like.  (One point to bear in mind is that other disciplines might run slightly different sessions - but more about this later!)

Setting the scene

Firstly, the moment we click on our OU Live room, OU Live should open in an instant.  There should be no delay!  We don't have to download anything extra (or enter any really annoying administrative passwords).  The Java software, which we need to run to use OU Live, should always work perfectly.  We should never have to upgrade it!

With the perfect OU Live session, not only will we have a perfect internet connection (which will never go down), our students will have a perfect internet connection too!  Our connection will be really fast (with little or no latency), and none of our students will be connecting up to our session whilst travelling by train.  An important point is: there will be no delays. 

We should also assume that all students have their own microphones and headsets, all of which are perfect.  This means that there is absolutely no feedback.  Of course, our own audio setup works perfectly, and there are no other software products battling to use our computer's audio channel.

The perfect time, length and group

We decided that the perfect time for the perfect OU Live session would be towards the middle of a module presentation (or, roughly half way through).  This means that, of course, everyone is making pretty good progress, and all students are now familiar with the OU Live interface.  Also, everyone has, what I call, good 'mic hygiene'. This means that students don't leave the microphone switched on (so other students can't speak!)

One important thing to say about our 'perfect group' is that they're all willing to interact; they're all engaged.  No one has kids in the background vying for attention, and there are no cats jumping on keyboards.

A 'perfect size' for an OU Live group would be considered to be around 10-12 students.  Since there would be no technology problems, there won't be any drop outs.  Also, everyone arrives exactly on time.  There will be no one arriving half way through the session asking, 'what have I missed?', or 'could you just go over that bit?'

Ideally, all the students who turn up would belong to our own tutor group.  This way, we know who they are and what their learning needs might be.

Our view was that our perfect session should last anything between 60 and 90 minutes.

(One thing that we didn't talk about was the best time to hold the perfect tutorial)

The perfect preparation

Preparation can be considered from two different perspectives: the tutor's side, and the student's side.  A tutor might prepare by, perhaps, doing a practice run through.  A tutor could also post a copy of a draft agenda on a tutor group forum.

Of course, in a perfect situation, all students would read the OU Live session agenda, and take the time to prepare for the session, which might mean having read sections of module materials, and having some questions to ask the tutor at the OU Live session.

Another thing that we could do to help with our preparation is to ask all our students in advance what topics they would like you to cover.  Since every student reads every message you post on the forum, you're able to design a session that is just for them.

The perfect OU Live tutorial structure

Since we're running 'the perfect session' in the middle of a module presentation, we can dispense with the idea of running any icebreakers: all the students should know each other already.

In our perfect session we would present a short introduction which relates to a set of really clear learning objectives.  This would be followed with a series of short interactive activities (say, around three).  These activities, of course, would be entirely appropriate for OU Live.

Since we (of course) would have planned out everything (and have a backup plan!) we would know how long each activity should take (also, in a perfect world, we would have run the session before, so we know what to expect!)

Towards the end of our tutorial, we would ask all students if they had any questions about what has happened.  We would then do a quick recap of what has happened, and remind everyone about the next TMA cut-off date.  We would also say something about what is going to happen in the next OU Live session (or module activity).

The perfect use of OU Live features

During our session, we chatted about the perfect use of various OU Live features.  One thing we discussed was the importance of polling, i.e. asking our students to respond during a session; students clicking on the 'tick' or the 'happy face' icon.   One suggestion (which was apparently given as a part of Blackboard training, the company that has created OU Live) is to poll students every 20-30 seconds.  Polling will allow you to keep the students engaged; it enables you to check whether everybody understands all the points that you are making (which is important since there's an obvious lack of visual cues).

Even though all students will have perfectly working microphones (with no crackle, delay or feedback), the text chat channel is still considered to be useful.  Students can ask for clarifications.  It can also be used to share links and other resources.  (Such as links to the OU study guides).

During our activities, we might want to use breakout rooms.  Of course, all our breakout rooms will work perfectly!  (There won't for example, be a situation where one student has a microphone and another hasn't)  We would be able to set a timer and move between different rooms, checking on what is happening in each of the sessions.

One of the things that we can't do in breakout rooms is to make a recording.  A related question is: 'should we record our perfect OU Live sessions?'  Different tutors have different opinions about this.  On one hand, a recording of an OU Live session becomes a useful (perfect) resource (that could be potentially referred back to, perhaps during the revision period).  Alternatively, if we record a session, students might argue that they don't need to turn up.  Also, if students know they're being recorded, they would be reluctant to speak.  (This is clearly an issue that is going to be debated for quite some time; there are clear arguments either way).

All tutors have used the application sharing feature of OU Live to show students how to use features of the programming tools that they need to use.  In the case of TU100, this is the Sense environment.  In the case of TM129, this would be RobotLab.  Sharing an application can allow the tutor to ask students some questions to determine whether they understand certain concepts.  It can also be used to demonstrate what happens when you run some code, and also how to begin to use different debugging strategies.  You might also give control of the application to students, so they can demonstrate their skills.

Of course, in a perfect world, the application sharing feature is really responsive!  (One comment was that, in the real world, we might use quite a small window, since this uses less bandwidth)

After the perfect session

At the end of the session, you would post a copy of the slides to your tutor group forum, and share any other resources.  A tutor might also post a number of follow up questions or activities, and the date and time of the next session.

Closing thoughts and acknowledgements

Before running this meeting I had never explicitly asked myself the question of 'what does a perfect OU Live session look like?'  Instead, I had worked on instinct: trying something out, and then reflect on whether it seemed to work or not. 

I found it really useful to hear everyone's opinions and views about what makes a good session.

During our meeting, I remember there was a conversation about OU Live examples.  I've managed to dig out the resource I was once told about.  It's called:  Teaching with online rooms (OU VLE). The page contains a set of different OU Live examples that have been created by tutors who are working in different disciplines. For those who teach programming and computing modules, the 'writing and running simple code' is a really interesting link.  The other resources about level 1 and academic referencing, and study skills are useful too.

I would like to personally hank all the tutors who attended this session for their contributions: everyone who was at the London region on the afternoon of Saturday 30 June contributed to discussions and ideas that led to the writing of this quick blog.  Thank you all!

Permalink Add your comment
Share post
Christopher Douce

Associate Lecturer Development Conference – LSE, April 2015

Visible to anyone in the world

This is a quick blog about an AL development conference I attended on 25 April at the London School of Economics.  I was looking forward to this event because I helped to put together parts of the programme.  Plus, I foolishly volunteered to run a session and facilitate the Mathematics Computing and Technology session.  It was destined to be a busy day.

The keynote talk was by my colleague Pat Atkins who presented a summary of some of the changes that were happening across the university.  These included a gradual alignment of associate lecturer contracts to various student support teams, and the introduction of a new group tuition policy, which is likely to substantially affect both tutors and module teams.

Other sessions

I helped to ‘pull together’ three AL development sessions during this conference.  After being inspired by ‘acting’ sessions that had been organised by colleagues from the South East region, I discovered that I knew someone who offered training to deal with difficult telephone calls.

Another session was about working with different pieces of technology (which was facilitated by two experienced technology associate lecturers). 

The third session was about working with students who have visual impairments.  I remember that the tutor, Richard Walker (who ran a similar session last year) saying that there is likely to be a high probability that every associate lecturer will have to work with a student who has a visual impairment at some point. 

Other sessions at the conference were about working with students who have English as a second language and a session about the role of the advisors in the London region.

The main purpose of this blog is, however, to present a quick summary of the session on OU Live Pedagogy that I ran.

The pedagogy of OU Live

For the uninitiated, OU Live can be thought of a bit like a version of Skype that has a whole load of other features, such as a shared whiteboard, and tools that enables a tutor to ask students different questions.  It also enables tutors to share portions of their screen, so students can see exactly what a tutor sees.

I think I was inspired to run this session by going to a number of other similar sounding sessions over the last few years.  A thought was, ‘what could I add to the debates about OU Live that I haven’t already heard’.  I had two objectives for my session.  The first objective was to share some of my own views about what it means to teach (or to facilitate learning) through OU Live.  The second objective was to share experience and practice.   Or, put another way, to learn about how different tutors use it to teach different modules.

A big part of the session was drawn from an earlier blog post where I wrote about the different ways to use OU Live.  For this session, I renamed a couple of the approaches.  The approaches that I talked about were:

  • Traditional tutorial: which is similar to a face to face session
  • Demonstration tutorial: where a tutor demonstrates something, such as a set of pages or some software.
  • Practical workshop: a session where a tutor puts a lot of focus into a product, tool, system, or activity.
  • Debate: an interactive debate between two tutors.
  • Recording a lecture: a short lecture which potentially augments materials provided by the module team, or to offer further explanations.
  • Drop-in session: an informal scheduled time where students can interact with a tutor and ask questions.
  • Student session: a scheduled but unfacilitated session that allow students on the same module to chat to each other.
  • Special (or additional support) session: a one to one session between a student and a tutor.

These ‘types’ are very informal.  I’ve created these types by trying to summarise all the different ways I’ve heard people talking about how they use OU Live.  It isn’t systematic, and it isn’t informed by theory; this rough taxonomy (of you could call it that) is more informed by the sharing of practice.

An important point that I made during the session is that, in some ways, technology moves a lot faster than pedagogy.  Tools such as OU Live offer us tutors a lot of different features.  The challenge is trying to figure out how to use them in the best possible way to make sure that students can learn efficiently.  It’s tempting to use these tools to just deliver dry lectures, where there are sets of PowerPoint slides.  The real challenge (from where we can create really engaging learning experiences) is to understand how to apply these tools to enable active learning.

Final thoughts

I always enjoy coming along to AL development events, and this one was also fun too: I enjoy running sessions!  The next conference is likely to take place in November 2015 in the Camden Town centre.

There’s going to be a couple of months off, before the conference planning group starts thinking about the next event.  (And, in the meantime, I’m going to take the liberty to visit the Oxford region to see what they’re doing).

 

Permalink Add your comment
Share post
Christopher Douce

Different ways to use OU Live

Visible to anyone in the world
Edited by Christopher Douce, Saturday, 24 Feb 2024, 17:38

From time to time I use a system called OU Live.  OU Live is a software application that tutors use to deliver learning events (such as tutorials) through their computer.  It’s taken me quite some time to get used to it because teaching through OU Live is very different to teaching face to face. 

When I first learnt about OU Live it immediately stuck me that there were loads of things that that you could do in during face to face tutorials that you certainly can’t do in OU Live.  I really enjoy planning and running face to face tutorials; they are a great opportunity to share your enthusiasm about the subject that you’re teaching.  They are also a great opportunity to learn from your students and to immediately understand what aspects of your tuition works and what aspects don’t work. 

Teaching ‘electronically’ is very different: it’s harder to get a more direct connection with your students and it’s also difficult to know whether certain concepts are understood well enough so you can move to other topics: it’s more difficult to see ‘the whites of their eyes’!

Over time, I have been persuaded that OU Live offers some really great opportunities for students.  Although you can do things in face to face settings that you can’t do in OU Live, I’ve also come to see that the opposite is also true: you can do things in OU Live sessions that you can’t in face to face sessions.  I’ve also realised that one of the challenges for the university is how to share best practice in how to use OU Live not only between tutors, but also between module teams.

This blog post aims to summarise my understanding of different ways that OU Live can be used; it is a post that connects with the broad idea of ‘OU Live pedagogy’.  It aims to share some ideas about how it can be used during the presentation of an OU module.  Some of these approaches have been picked up by chatting with colleagues, and others are methods that are currently used today.  I’ve also added a couple of approaches that I’ve invented (but other people might have also thought of them too).

In essence, I’m posting this as a really rough ‘grab bag’ of tentatively named pedagogic tools that I hope someone might find useful.  If you have any comments, or have accidentally found this useful, do get in touch.

On-line tutorials

When I first started to use OU Live I used it to replace face-to-face tutorials.  There are two situations where I’ve needed to do this.  One of the modules that I tutor is completely on-line; students can be from different parts of the country (or even different parts of the world).  In this situation, face to face tutorials are obviously impossible: the only thing that we can do is to run OU Live sessions. 

Another situation was where I wasn’t able to physically get to a tutorial due to a scheduling clash.  Unfortunately, it wasn’t possible to reschedule the event for the weekend since the new date would then be too close to the TMA cut-off date.  To get around this problem, I decided to run an evening OU Live tutorial, which I then recorded.  I was pretty surprised that a good number of students came along to the session (including some students who were never able to get to the face to face sessions).

In some respects, an OU Live tutorial can become a bit like a face to face tutorial (if you plan it well).  A tutor can present materials, do some talking, set up activities, ask for student responses, and even get students to work on a shared task by putting them into ‘breakout rooms’: there is a lot that is similar.  There are, however, some differences.  OU Live sessions can be pretty tiring for the tutor.  A tutor can’t just ‘glance across’ a classroom to see what is going on.  Instead, a tutor has to engage with a cognitively demanding interface and very regularly request students to ‘do stuff’, to ensure that their attention is maintained.  Tutors might also be faced with technical issues of challenges to contend with, i.e. some students might not have microphone headsets, they might have connected up the microphone jack to the headphone jack, or they might have set the volume setting so low that they can’t hear anything at all.

Another point is that sometimes the material designed for a face to face session might not be easily transferrable to an OU Live session because it just isn’t appropriate.  Students can’t write things on pieces of paper and exchange notes, or move to an empty space in a room (with the intention of demonstrating a physical concept or idea).  For an OU Live tutorial to work and work well, tutors (and, arguably the module team), need to come up with a learning design that is appropriate for the on-line environment.  Also, tutors and students need to be given some time so that they become familiar with the on-line environment.

I believe that an OU Live session can replace certain aspects of a face to face session, as long as they are designed with a lot of care and attention.  A final point is that an OU Live session shouldn’t go on for as long as a face to face session.  Longer sessions, for some reasons, just don’t seem to feel right.  We all need a break from looking into a screen.

Demo tutorials

A couple of months ago, I was alerted to some OU Live training materials (OU VLE) which shows how you might use OU Live during tutorial sessions (you might have to have ‘tutor permissions’ to be able to see these).  These exemplar sessions cover a range of different subjects, and they are quite short (around ten minutes), which means that you don’t have to go through an entire tutorial.  If you can access these, I do recommend them.

The first one is entitled ‘Working with metre in poetry’ makes use of highlighter and a web tour (from around the seven minutes mark).  The next session, entitled ‘Multisensory pronunciation training’ was all about learning German.  What was really nice about this one was the way that the ‘put your hand’ button was used and how the tutor used the webcam.

A subject that is close to my heart has the title, ‘Writing and running simple code’.  This makes use of the application sharing feature from around the two minute mark.  I also liked ‘Finding and using secondary sources in legal essay writing’, where the whiteboard was used from around the three minute mark.  I really like the way that ‘click and drag’ is used.

There are, of course, other exemplars.  Do have a look; it’s a really good resource.

On-line debate

A week or so ago I was chatting with a really experienced tutor who said that he really enjoys running OU Live sessions.  He told me that he had teamed up with another tutor.  ‘We have a debate’, he said.  ‘One of us takes one view, and the other tutor takes an opposing view.  Our students love it!’ 

This struck me as a whole other way to use OU Live.  TV programmes like Newsnight have a very familiar format.  OU Live not only allows us to create a ‘virtual TV studio’, but it also allows us to create a situation where the ‘virtual TV audience’ can ask the experts some questions.  Another thought is that we could potentially create situations where students can (and should) be encouraged to challenge the points of views that are exposed by the experts.

From my perspective, I would really like to see an example of how this might work.  There are aspects of technology and computing education where ‘the debate’ format might work.  Another point to bear in mind is that to get the best out of these opportunities, module teams need to be considering these opportunities when they are designing modules.

Recording a lecture

Running an on-line tutorial can be a tough business; there’s a lot going on.  You’ve got slides, different OU Live tools, students talking, problems with microphones, text messages appearing and also the need to manage and control activities. 

During the presentation of a module a tutor might discover that some students might struggle with a certain topic.  Rather than to offer comments through a discussion forum, or perhaps a group email, another approach is to run, and to also potentially record, a short lecture.  OU Live can be used to record a short session that can be considered to be akin to a ‘video podcast’.

When a session has been recorded, tutors can then refer students to the resource in their correspondence tuition, as well as during examination preparation sessions. 

I used this approach to run a revision session for M364 Fundamentals of Interaction Design.  I kept getting scuppered by technology.  The first time I ran the revision session there was a power outage at the university which meant that students couldn’t login to my session.  The second time I ran the session, I discovered that I couldn’t use the record button, and after the session students contacted me asking when a recording would be available.   The third time I ran the session, I just made a recording; there were no students.  When I had finished the recording and I had made it available to everyone, I let all the students know by making a post to the module discussion forum.

One question is: how long should a ‘recorded lecture session’ last?  Unfortunately, I don’t have any research to back this up, but when it comes to student engagement my instinct is to try to keep them pretty short.  This is something that I ought to look into.

Focused Demo

The idea of a ‘focused demo’ pretty much follows on from the idea of a lecture.  Quite a few computing modules make use of some specialist software, such as programming environments such as Eclipse, Netbeans or Sense (you don’t have to worry about what these are, just know that they’re special bits of software).  For design and engineering modules, students might have to use tools such as Open Design Studio.  Some students might find that some of these pieces of software pretty baffling to use, especially if they’ve never seen them before.

One approach to help students is to ‘show’ them how to use a piece of software.  OU Live has got a great facility called ‘application sharing’, which means that you can show students what you see on your screen.  You might show students how to begin to use a software tool during an on-line tutorial, but there’s always the risk that things might go wrong, i.e. an internet connection might go down, or a big and complex bit of software might begin to misbehave. 

Rather than doing a ‘live’ demo (which is, ultimately, a really good thing to always try to do), another idea is to record what could be loosely called a ‘focussed demo’, i.e. you could show students how to use a particular bit of a software system by recording a quick demo using OU Live. 

If you’re teaching programming, you could also use this approach to show how to solve a particular problem.

Drop in session for students

I remember when I was an undergrad our human-computer interaction lecturer said to everyone, ‘I’ll be in my office on a Wednesday afternoon between these times… if you have any questions about anything, just pop in to see me: I’ll be very happy to have a chat’.  I thought it was a great way to encourage informal discussions about the course, and the materials.

After having a chat with my colleague from the South East region, I discovered that she used the exact same approach to support her students.  Rather than running a face to face ‘drop in session’, she ran a virtual one.

The way it worked was that she would advertise times when she would be available for a chat in her tutor OU Live room, and students could just turn up if they wanted a chat about anything. She would keep an eye on what was going on in the room whilst doing other things: exactly the same way that it used to work when I was an undergraduate.

What I really liked about this approach was how informal it is. There is no plan or agenda, but it clearly suggests to students that they can ‘drop by’ and gain some support if they need to.  I haven’t tried this approach in my own tutoring, but I am certainly going to!

Additional support session

For students who struggle with some aspects of a module the university can offer something called an ‘additional support session’.  This usually takes the form of a one to one session between a student and a tutor.  There are different ways that an additional support session could be run.  One way is to run a face to face session at a regional centre (or another venue that could be booked by the university).  Another approach might be to have a telephone session.  A third way is to run an additional support session through OU Live.

One of the main advantages of using OU Live for an additional support session is that both the student and the tutor can make use of the whiteboard.  In some cases, a tutor might decide to prepare a couple of slides so the tutor can work through some of the ideas that a student might be struggling with.  This might be particularly useful with arts subject, languages (where a tutor might write things onto a whiteboard), or even mathematics, where a tutor might take a student through how to solve an equation, or work through other mathematical ideas.

In the big scheme of things, face to face is always better than on-line, but on-line can certainly be (with adequate planning) significantly better than the telephone.  One question that should be asked if one is faced with running an OU Live session is: ‘how can I make the best use of this tool to help this particular student?’  One way to get a feel for how to approach a session is to take the time to explicitly ask the student which areas to focus on.   When we know a bit more, we can use the time that we have a whole lot more effectively.

Session between students

After recording the M364 revision session that I mentioned earlier, I noticed an interesting discussion on one of the module discussion forums.  One student proposed the idea of an ‘on-line chat’ in a module wide OU Live room.  I seem to remember that this started a short debate between tutors about whether students should be left alone in an on-line space that is operated by the university.

In a face to face university, students chat with each other in university owned common rooms and corridors all the time, so why shouldn’t this happen in an on-line space?  The tough thing about distance learning is the isolation, so it seemed like a really good idea to allow students to chat to each other about a forthcoming (or impending) exam.

I sense that different people have different views about the use of on-line spaces, but I also can see that module team members, forum moderators, or curriculum managers might be able to play a role in facilitating (or seeding) student led discussions through on-line rooms.  Plus, in some modules where group work is essential, I sense that the use of OU Live has the potential to play a pivotal role.

Final thoughts…

One of the things that I really like about OU Live is that you can record sessions which is one of the things that you can’t easily do in a face to face session: if you’ve missed a face to face session, it means that you’ve missed it.  The recording facility gives tutor the power to create new types of potentially transitory learning resources that have the potential to help students in a number of different ways.

Recordings

My own (personal) view about recording is that we should record everything, since this has the potential to help the widest number of students.  Also, if a tutor makes a recording of an on-line tutor, students need be clearly told that they will be recorded: they should be given sufficient information to help them to make a decision about whether they wish to come along to a ‘live’ on-line session.

There are differing views about recording OU Live tutorials.  One argument is that if they are recorded, students won’t bother turning up; they’ll just watch the tutorial.  A counter argument to this is: if they don’t come along then they won’t be able to influence the tutorial in a way that will allow them to get their best possible learning.  A recording, I argue, should show students what they’re missing so they become suitably motivated to come along to the next live session.

Another argument is that if a session is recorded then students might be less likely to participate during a session.  This might well be the case, but I don’t see this as a very strong argument.  It’s very easy to forget that a recording is being made, and if there are exceptional points that a student wishes to share with a tutor then perhaps an on-line session isn’t the best place.

A final argument that I’ve heard is: ‘a tutorial is a tutorial; if you want to record something that students can access as a resource, then perhaps it should be recorded as just that: a resource’.  My point is that there isn’t any reason why we can’t do both.  OU Live allows us to do this, and there’s no reason why tutors can’t reference one type of resource from another.  During a ‘lecture’, you might hear the recorded phrase, ‘… and it was exactly this point that we covered during our earlier on-line tutorial’ (which students then might be tempted to go and listen to).

As far as I am aware, there isn’t yet any explicit faculty wide guidance about the recording of OU Live sessions, but I hope that there will be some one day.  When it comes to recording, my argument is very simple: we should use technology to help as many students as we can, irrespective of when and at what time they study.  Recordings of OU Live sessions can help with this, but I accept that there are important debates to resolve, especially the ethical dimension.

Module teams

One of the main points of this blog is that OU Live can be used in very different ways.  A lot can be done, but to get the best out of it, tutors (and staff tutors, who manage tutors) need a steer to understand how OU Live can be best used in the context of a module.  From the module team perspective, it’s important to offer explicit guidance to tutors about how it should and could be used.

Also, there is no reason why module teams cannot run their own OU Live sessions.  An OU Live session run by a module team should, of course, have a very different feel to any OU Live sessions that are run by tutors.  One idea is that a module team might run a series of ‘introductory lectures’ for a module: one at the start of a module, and one at the start of each major block.  This could be distinct from the sessions that tutors run which is all about small group work.

The module teams also have an important role to play in offering advice and guidance to tutors about the types of activities they consider to be useful.  At the beginning of a module presentation, the module team are the experts, and the tutors will occasionally need help in terms of understanding what to do in terms of how to effectively design a pedagogically engaging on-line tutorial.  Suggestions from the module team, perhaps working in collaboration with experienced tutors, can be invaluable.

Using OU Live for research

OU Live can be also used for research.  I’ve been recently been involved with an internal research project that has been all about understanding tutor experience on on-line modules.  The approach that the researchers (who were fellow associate lecturers) took was really interesting: they used OU Live to as a way to not only to help to facilitate a research interview, but also to record a research interview too.  The tutors managed to convert the recorded sessions into MP3 format and pass them onto me for analysis.

Group Tuition Policy

The university has recently been working on something called a ‘group tuition policy’, which is a university wide policy that aims to improve the learning opportunities that are available for students.  I’ve yet to fully appreciate the full significance of this policy, but one thing that I have heard is that students will be offered different types of session so that they will be able to attend a wider variety of learning events.  In the ‘new world’ of the group tuition policy, there may be on-line equivalents of face to face sessions.  I fully expect there to be a need to ‘group’ tutors together for on-line sessions in a way that my faculty currently groups together tutors for some face to face events.

Concluding points

This blog has considered the different ways that OU Live can and has been used.  I’ve heard it said that technology can move and develop a lot faster than pedagogy.  Put another way: we’re still figuring out how to most effectively teach using these new interactive tools.  As I mentioned earlier: you can do some things in face to face tutorials than you can in on-line tutorials.

It has personally taken me quite a bit of time to understand that there are a whole range of different interesting, exciting and dynamic opportunities that couldn’t have been possible if you only adopted face-to-face teaching.  A continued challenge that we have to collectively grapple with is how to effectively manage the important blend between the two.

Permalink Add your comment
Share post
Christopher Douce

New Technology Day - June 2014

Visible to anyone in the world
Edited by Christopher Douce, Tuesday, 8 Oct 2019, 17:42

This post is a quick summary of a New Technology Day event that took place at The Open University London regional centre on Saturday 14 June 2014.  I’ve written this post for a number of reasons: for my esteemed colleagues who came along to the day, so that I help to remember what happened on the day, so that I can share with my bosses what I’m getting up to on a day to day basis, and for anyone else who might be remotely interested.

One of the challenges that accompanies working in the area of technology, particularly information technology and computing, is that the pace of change is pretty relentless.  There are always new innovations, development and applications.  There are always new businesses doing new things, and using new techniques.  Keeping up with ‘the new stuff’ is a tough business.  If you spent all your time looking at what was ‘new’ out there, we simply wouldn’t get any work done – but we need to be understanding ‘the new’, so we can teach and relate to others who are using ‘all this new stuff’.

The idea for this day came from a really simple idea.  It was to ask colleagues the question, ‘have you heard of any new technology stuff recently?  If so, can you tell me about it?’  Rather than having a hard and fast ‘training’ agenda the idea was to create a space (perhaps a bit like an informal seminar) to allow us to have an opportunity to share views and chat, and to learn from each other.

Cloud computing

After a brief introduction, I kicked off with the first presentation, which was all about cloud computing.  A couple of weeks back, I went to a conference that was all about an open source ‘cloud operating system’ called OpenStack as a part of some work I was doing for a module team.  The key points from the presentation are described in a series of two blog posts (OU Blog)

Towards the end of the presentation, I mentioned a new term called Fog Computing.  This is where ‘the cloud’ is moved to the location where the data is consumed.  This is particularly useful in instances where fast access times are required.  It was interesting to hear that some companies might also be doing something similar.  One example might be companies that deliver pay-on-demand streaming video.  It obviously doesn’t make a lot of sense if the movies that you want to see are located on another continent; your viewing experience may well be compromised by unforeseen network problems and changes in traffic.

It was useful to present this since it helped to clarify some of my understandings, and I also hoped that others found it interesting too.  Whilst the concept of a ‘cloud’ isn’t new (I remember people talking about the magic of an X.25 cloud), the technologies that realise it are pretty new.   I also shared a new term that I had forgotten I had written on one of my slides: the concept of a devop – someone who is also a developer and an operator.

JuxtaLearn project

The second presentation was about the JuxtaLearn project, by Liz Hartnett, who was unable to attend.  Liz, however, still was able to make an impact on the event since she had gone the extra mile to make an MP3 recording of her entire presentation.  Her talk adopted the PechaKucha format.  This is where a presenter uses 20 slides which change every 20 seconds.  Since her slide deck was setup to change automatically, it worked really well.

We learnt about the concept of the threshold concept (which can be connected to the concept of computer programming) and saw how videos could be made with small project groups.  I (personally) connected this with activities that are performed on two different modules: TU100 My Digital Life, and T215 Communication and Information Technologies, which both ask students to make a presentation (or animation).

OU Live and pedagogy

The next talk of the day was by Mandy Honeyman, who also adopted the PechaKucha format.  Mandy talked about a perennial topic, which is the connection between OU Live and pedagogy.  I find this topic really interesting (for the main reason that I haven’t yet ‘nailed’ my OU Live practice within this format, but it’s something that I’m continuing to work on).  I can’t speak for other people, but it has taken me quite a bit of time to feel comfortable ‘teaching’ using OU Live, and I’m always interesting in learning further tips.

Mandy has taken the time and trouble to make a version of her presentation available on YouTube.  So, I’ve you’ve got the time (and you were not at the event), do give this a look.  (She prepared it using PowerPoint, and recorded it using her mobile phone).

The biggest tip that I’ve made a note of is the importance of ‘keeping yourself out of it’, or ‘taking yourself out of it [the OU Live session]’.  When confronted by silence it’s easy to feel compelled to fill it with our own chatter, especially in situations where students are choosing not to use the audio channel.

One really interesting point that came out during the discussion was how important it is to try to show how to use OU Live right at the start of their journey with the OU.  I don’t think this is done as it could be at the moment.  I feel that level 1 tutors are implicitly given the challenging task of getting students up to speed with OU Live, but they will already have a lot on their hands in terms of the academic side of things.  I can’t help think that we could be doing a bit better when it comes to helping students become familiar with what is increasingly become a really important part of OU teaching and learning.

It was also mentioned that application sharing can run quite slowly (especially if you do lots of scrolling) – and one related thought is that this might well impact on the teaching and learning of programming.

A final point that I’ll add is that OU Live can be used in a variety of different way.  One way is to use it to record a mini-lecture, which students can see during their own time.  After they’ve seen them, they can then attend a non-recorded discussion seminar.  I’ve also heard of it being used to facilitate ‘drop in sessions’ over a period of a couple of hours (which I’ve heard is an approach that can work really well).

Two personal reflections that connect to this session include: we always need good clear guidance from the module team about how they expect tutors to use OU Live, and secondly, we should always remember to give tutors permission to use the tool in the ways that make the best use of their skills and abilities, i.e. to say, ‘it’s okay to go ahead and try stuff; this is the only way you can develop your skills’.

The March of the MOOCs

Rodney Buckland, a self-confessed MOOCaholic, gave the final presentation of the morning.  The term MOOC is an abbreviation for Massive Open Online Course.  From the sound of it, Rodney has taken loads.  (Did he really say ‘forty’?  I think he probably did!)

He mentioned some of the most popular platforms.  These include: Coursera, Udacity and FutureLearn (which is a collaboration between the OU and other universities).  Rodney also mentioned a swathe of less well known MOOC platforms, such as NovoEd.   A really interesting link that Rodney mentioned was a site called MOOCList which is described as ‘an aggregator (directory) of Massive Open Online Courses (MOOCs) from different providers’. 

Rodney spoke about his experience of taking a module entitled, ‘Science of the solar system’.  He said that the lecturer had really pushed his students. ‘This was a real surprise to me; this was a real third level physics module’.

A really important point was that MOOCs represented an area that was moving phenomenally quickly.  After his talk had finished there was quite a lot of discussion about a wide range of issues, ranging from the completion rates (which were very low), to the people who studied MOOCs (a good number of them already had degrees), and to the extent to which they can complement university study.  It was certainly thought provoking stuff.

Assistive technology for the visually impaired: past, present and future

The first presentation after lunch was by my colleague Richard Walker.  Richard is a visually impaired tutor who has worked with visually impaired students.  He made the really important point that if an associate lecturer works for an average of about ten years, there is a very significant chance that a tutor will encounter a student who has a visual impairment.  Drawing on his previous presentation, there is an important point that it is fundamentally important to be aware of some of the challenges that visually impaired students can face.

Richard recently interviewed a student who has a visual impairment by email.  Being a persuasive chap, Richard asked me to help out: I read out the role of his student from an interview transcript.  The point (to me) was very clear: students can be faced with a whole range of different issues that we may not be aware of, and everything can take quite a lot longer.

Another part of Richard’s presentation (which connects the present and the future) was all mobile apps.  We were introduced to the colour recogniser app, and another app called EyeMusic (iTunes) which converts a scene to sound.   Another really interesting idea is the concept of the Finger Reader from the Fluid Interface group at MIT.

A really enjoyable part of Richard’s session was when he encouraged everyone to explore the accessibility sessions of their smartphones.  Whilst it was easy to turn the accessibility settings on (so your iPhone spoke to you), it proved to be a lot more difficult to turn the settings off.  For a few minutes, our meeting room was filled with a cacophony of robotic voices that proved to be difficult to silence.

Towards utopia or back to 1984

The penultimate session of the day was facilitated by Jonathan Jewell. Jonathan’s session had a more philosophical tone to it.  I’ve made a note of an opening question which was ‘how right or wrong were we when predicting the future?’

Jonathan referenced the works of Orwell, Thomas More (Wikipedia) and a vision of a dystopian future depicted in THX 1138, George Lucas’s first film.  Other subjects included economic geography (a term that I hadn’t heard before), and the question of whether Moore’s Law (that the number of transistors in a microprocessor doubles every two years) would continue.  On this subject, I have sometimes wondered about what the effect of software design may be if and when Moore’s law fails to continue to hold.

Other interesting points included the concept of the technological singularity and a connection to a recent news item (BBC) where a computer was claimed to have passed the Turing test.

A great phrase was infobesity – that we’re all overloaded with too much information.  This connects to a related phrase that I have heard of before, which is the ‘attention economy’.  Jonathan made a similar point that information is not to much a scare resource.  Instead, we’re limited in terms of what information we can attend to.

We were also given some interesting thoughts which point towards the future.  Everything seems to have become an app: computing is now undeniably mobile.  A final thought I’ve noted down is Jonathan’s quote from security expert, Bruce Schneider: ‘surveillance is the business model of the internet’.  This links to the theme of Big Data (Wikipedia).  Thought provoking stuff!

Limits of Computing

The final talk of the day was by Paul Piwek.  Paul works as a Senior Lecturer in the Department of Computing and Communications at The Open University.  Paul works on a number of module teams, and has played an important role in the development of a new module: M269 Algorithms, Data Structures and Computability.  It is a course that allows students to learn about some of the important fundamentals of computer science.

Paul’s brief was to talk about new technologies – and chose to explore this by considering the important question of ‘what are the limits of computability?’  This question is really important in computer science, since it connects to the related questions: ‘what exactly can we do with computers?’ and ‘what can they actually be used to calculate?’

Paul linked the title of his talk to the work of Alan Turing, specifically an important paper entitled, ‘on computable numbers’.  Paul then went onto talk about the differences between problems and algorithms, introduced the concept of the Turing Machine and spoke about a technique called proof by contradiction.

Some problems can take a long time to be solved.  When it comes to computing, speed is (obviously) really important.  An interesting question is: how might we go faster?  One thought is to look towards the subject of quantum computing (an area that I know nothing about; the page that I’ve linked to causes a bit of intellectual panic!)

Finally, Paul directed us to a Canadian company called DWave that is performing research into the area.

Reflections

After all the presentations had come to an end we all had a brief opportunity to chat.  Topics included location awareness and security, digital forensics, social media, the question of equality and access to the internet.  We could have chatted for a whole lot longer than we did.

It was a fun day, and I really would like to run another ‘new technology day’ at some point (I’ve just got to put my thinking hat on regarding the best dates and times).  I felt that there was a great mix of presentations and I personally really liked the mix of talks about technology and education.  It was a great opportunity to learn about new stuff.

By way of additional information, there is also going to be a London regional ‘research day’ for associate lecturers.  This event is going to take place during the day time on Tuesday 9 September 2014.  This event will be cross-faculty, cross-disciplinary event, so it’s likely that there might be a wide range of different events.  If you would like some more information about all this, don’t hesitate to get in touch, and I’ll point you towards my colleague Katy who is planning this event.

Permalink 1 comment (latest comment by Mandy Honeyman, Tuesday, 17 June 2014, 15:40)
Share post
Christopher Douce

London Associate Lecturer development day, London, November 2013

Visible to anyone in the world

The Open University is divided into a number of regions and twice a year the London region runs a staff development event for its associate lecturers who live in and close to our capital.  This blog post is a brief summary of an event that took place on Saturday 16 November 2013.  My own role during the day was quite a modest one (I was only required to do a couple of introductions).  This meant that I was able to wear my ‘tutor hat’ for much of the day.

Challenges for ESL students

ESL is, of course, a common abbreviation for ‘English as a second language’.  From time to time I’m asked what the university is able to do to help students who struggle with English.  There are a couple of schools of thought about this.  One school of thought is that English and writing skills should be embedded within modules (this is certainly the case within computing and engineering modules).  Another school of thought is that there should be a particular course or module that is dedicated to writing (which is the approach that the science faculty takes).  There are, of course, pros and cons with either approach.  The aim of this session was to offer tutors useful guidance about different resources and materials that could be shared with students.  It also aimed to help tutors chat about different challenges they have faced.

One skill that was considered to be important was the reading of papers, and a point was made that this is something that could be practiced.  Reading is, of course, a prelude to writing.  Although some people might argue that university level academic writing is something that is done only within the university (or academic) context, it can also be argued that learning how to write in an academic way can benefit learners in other ways, i.e. when it comes to writing for business and commerce, or the ability to distil evidence and construct cohesive arguments.

One question that was raised was, ‘how do you offer feedback in instances where students may struggle to read suggestions?’  This was a very good question, and sometimes interventions, or special sessions to help students are necessary.

Our discussions about writing led onto other discussions about plagiarism and academic conduct.  Plagiarism is, of course, a word that has very negative connotations.  In some cultures, using the words of an authority may be considered to be a mark of respect.  On the other hand, developing the ability to write in one’s own words is a really important part of distance learning; it’s both important and necessary for students to demonstrate how they are able to evaluate materials. 

The university has very clear policies about plagiarism and academic practice, and this is something that I’ve blogged about previously.  (Academic practice conference: day 1 summary, day 2 summary). From the tutor’s perspective, it isn’t an easy task to address these issues thoroughly and sensitively.  One thing that tutors could do is to run an activity (which exposes issues that relate to academic conduct).  Tutors (or module teams) could show how things should be done, and then tutors could facilitate a discussion using on-line forums, for example.

Another discussion that I’ve noted was the use of the ‘voice’.  Different modules may have a preference as to whether students can or should write in the first person.   One of the arguments about writing in the third person is that it allows other voices to be more clearly exposed.

During the session, we were all encouraged to do a bit of group work.  We were given a sample of writing and we were asked, ‘what resource would you choose to share with your students to try to help them with their writing skills?’  This was a fun activity and it emphasised that there is a lot of resources that both students and tutors can draw on.

To underline this point of resources, there were sets of study skills booklets that were available in the presentation room.  These had the titles:  Studying with the OU – UK learning approach, Reading and Taking Notes, Preparing Assignments and Thinking Critically.  If you’re interested, these can be downloaded from the Skills for Study website.

Developing resources and pedagogy for OU Live

I arrived at this afternoon session slightly late, since I was having too much fun chatting to colleagues.  OU Live is an asynchronous teaching and learning tool (which is a posh term to say that people can do things at the same time).  In essence, think ‘skype with a whiteboard’.  It allows tutors to run on-line sessions with groups of students, offering both audio and text-chat channels.  From my own experience, running OU Live can be pretty hard going, so I try to take every opportunity that I can (time permitting) to attend whatever training sessions the university offers.

This afternoon session was presented in two parts.  The first part was from the perspective of a science tutor (Catherine Halliwell), whereas the second part was from the perspective of a languages tutor.

Science perspective

I arrived in the session right at the moment when an important point was being made.  This was: ‘find a style of delivery that suits you’. It can be quite easy to use OU Live just to give ‘lectures’, but it is possible to use it to deliver dynamic interactive sessions.

One thing that tutors can do is to record their on-line sessions.  More students might use a recording of a session than there are students who are able to attend a live session.  One of the benefits of recordings is that they have the potential to become a very useful resource.  Tutor might, for example, refer students to sections of a recording when they start to revise for their exams.  Another thought is that you could explicitly refer to them when a tutor gives assignment feedback (guiding students to parts of a presentation where you have explained potentially difficulty concepts).

Catherine mentioned that her faculty had trialled the use of pairing tutors together to run single OU Live session.  Her module, a third level chemistry module, has 10 hours of tuition time.  Each session was shared; one tutor would take the lead, and the other would be a ‘wing man’.

Another aspect to OU Live pedagogy which can be easily overlooked is the importance of preparation.  Students can be asked to carry out certain activities before a session, such as completing one or more worksheets, for instance, to help to prepare students – or even performing observations, with the view to sharing data.

Catherine also spoke about some features that I had never used, but had been (slightly) aware of.  One of these features was the ‘file transfer’ facility, which could be used by the tutor to send students sets of ‘unseen questions’, perhaps in the form of a word document.  In some ways, this could be considered to be the electronic equivalent of giving everyone some handouts.  (I can also see that this would be especially useful during programming sessions, where tutors might hand out working copies of computer code to all participants).

We were given a number of very useful tips: make the first session as interactive as possible, and feel free to use a silly example.  Also, use things like voting, or drawing on a map.  Another thought is to turn the webcam on at the start so that the participants know who you are (you can turn it off after a few minutes, of course!)  Tutors should try their best to make their sessions friendly and fun.

There are a number of other points to bear in mind: some students can be reluctant to use the microphone, and this is okay.  Another approach (and one that I’ve heard of before) is to use OU Live as an informal drop-in session, where students are able to log in to have a chat with a tutor at a pre-arranged time.  It’s also important to take the time to look at a student’s profile to make sure whether there are any additional requirements that need to be taken into account.   Finally, because it’s possible to record a session, a tutor can always say, ‘I’m going to go through this bit quite quickly; because I’m recording this, you can always go back and play it back later if there’s anything that you miss’.

Languages perspective

The presentation from our language tutor was rather different.  We were given, quite literally, an A to Z tour of topics that relate to the use of OU Live, leaving us (and our facilitator), pretty breathless!

A couple of points that I’ve noted include the importance of developing routines and forcing habits (in terms of running sessions at the same time).  It’s also a good idea to send group emails, both before and after sessions (so students are aware of what is going to happen).  In terms of preparation, it’s a good idea to get on-line around half an hour before just to make sure that you don’t run across any technical problems or issues; having been confronted with the situation of Java software updates in the past this is very sound advice.

During the question and answer session at the end of the afternoon, the issue of the recording of day schools also cropped up again.  Our tutors were very pragmatic about this: recording of OU Live sessions should happen, since it allows the creation of resources that all students can use (especially those who could not attend any of the sessions).  It is therefore important to let all students know that recording is going to take place either before events, or at the start of an event.

Reflections

There’s always something to pick up from these events.   There were two main things that I gained from this session.  The first was the early discussions about language support consolidated what I already knew about the importance of academic conduct (and how the university procedures work).  Secondly, I picked up some tips about how to connect things together, i.e. connecting together assignment feedback with the use of OU Live recordings. 

The next event is to be held at the London School of Economics in March.   This event is likely to include a Mathematics Computing and Technology faculty specific session which will be held in the afternoon.  The fine detail hasn’t yet been decided on, but this too is also likely to be a good day.

Permalink
Share post
Christopher Douce

TU100 My digital life: AL development event

Visible to anyone in the world
Edited by Christopher Douce, Tuesday, 8 Oct 2013, 12:15

The second TU100 development day for associate lecturers in London and the surrounding regions was held on Saturday 7 September in the London regional centre.  The overall purpose of the day was to give associate lecturers who tutor on TU100 an opportunity to share experiences and to gather some useful feedback about the module that I could pass onto the module team.  These days are often great fun since everyone is very much up for sharing and talking (and this day was no exception).  This blog post represents a quick summary of what happened (from my own perspective, of course).

I’m writing this post for a number of reasons.  The first reason is to remember what happened on 7 September (since my memory is somewhat fallible), and the second reason is to give those tutors who couldn’t attend a bit of a feel for some of the subjects were discussed.  The third reason is to try to encourage other tutors to come along to other events that we run in the region.

There were essentially three different parts to the day.  The first part was all about teaching programming and Sense.  The second was about issues relating to student retention (where we heard about a university initiative called Project Retain), and the third was a general ‘feedback (or feedforward) to the module team’ session.

Session 1 : Teaching programming and Sense

During the first session we were put into small groups and Leslie, one of our very experienced TU100 tutors, distributed a questionnaire to inspire discussion.  These had the headings: ‘how does TU100 teach programming?’, ‘how does TU100 teach Sense?’, ‘student contact hours’ and ‘marking’.  Since I’m not a TU100 tutor I didn’t contribute too much to the group discussions, but I did make some notes of some of the themes that had emerged.

It wasn’t too long before the subject of programming cropped up.  One of the comments I’ve made is that the module doesn’t contain too much about testing.  One other thought is that early on in the module it is a good idea to emphasise the importance of Sense, particularly the Sense programming guide.  Another thing that tutors could do is to emphasise the wealth of Scratch resources that are available from MIT, and that perhaps we should more explicitly brief students that Sense is an extension of Scratch.

We soon began to talk about the on-line sessions which are presented through Blackboard Collaborate (or OU Live, as the university calls it).  One of the challenges with using the OU Live software is that it takes time to hand over screen sharing control when tutors ask students to complete certain tasks. 

An interesting point is that OU Live might not only be useful for running tutorials.  Since it contains a facility to record sessions it can also be used to record how any application is used.  Tutors (or faculty staff) could use OU Live to make ‘video’ recordings to demonstrate some programming concepts.

One of the biggest challenges that tutor’s face is the marking of assignments.  Sometimes tutors come across some puzzling situations, i.e. if students submit work where a screenshot represents a correct functioning program, but the program that is submitted isn’t actually correct.  When it comes to correspondence tuition, one of the fundamental challenges is to get into the head of the student.  This led to the question of whether we might be able to record video clips to show how students could have created correct solutions.

Plenary

After around fifteen or twenty minutes of chatting, all groups were asked to report back.  This section is a quick summary of some of the key points that some of the groups mentioned. 

TU100 doesn't contain a section that is dedicated only to programming.  Instead, programming can found in different sections throughout the module.  One point mentioned by tutors was that whilst TU100 teaches coding it doesn’t say much about how to do the 'problem solving' part of programming.  Instead, students are required to spend time discovering how to program by exploring and playing with the Sense environment.

Aware of this issue, some TU100 London tutors have started to present the fundamentals of how to break apart problems into pieces that could then be used to create code (either in the face to face sessions, or on the on-line sessions).  The precursor to TU100, M150 contained some materials to introduce students to something called structured English.  This gave way to a debate about whether some additional material might be added to TU100, but the problem is that there are already lots of materials that students and tutors need to cover. 

The point is that the foundations (in terms of learning to program) are really important, especially for students who might potentially struggle with the fundamentals of programming.  One tutor said that some students never make it to the starting line on Sense and this kind of resources could be a bridge between high level thinking and programming.  Some of the fundamentals that could be covered (by tutors) include the basic constructs of programming, which includes sequences of instructions, selection, iteration, the use of variables and debugging.

One tutor said that ‘we need to emphasise that it is important that students have a go’ (so students gain an understanding of what the building blocks of software is all about).  Also, there is need for a Sense forum, something or some area that allows sharing of materials and ideas between students and tutors. 

One piece of advice to students should be, ‘go look at what people do with Scratch’.  Another comment was, ‘add a couple of YouTube type videos about program analysis’.  The interactive nature of programming does lend itself to the use of OU Live, via application sharing, but on-line asynchronous tutorials are always going to be difficult and it takes a skilled facilitator to use more sophisticated functions such as on-line break out rooms.

Another perspective was that it might help the students if there was slightly more signposting to different resources.  (I understand that this is something that the module team have been working on for the new presentation).

Contact hours, tutorials and day schools

Different regions do different things when it comes to on-line tutorials and day schools.  When it comes to on-line time, the London region has given tutors the opportunity to schedule and run individual sessions.  The south region runs join sessions, as does the south east region.

When it comes to the face to face sessions, all the London groups come together to form a series of big day schools with the intention of creating a critical mass of both students and tutors.  In other regions tutors run sessions with pair of tutors.  The differences can be down to geography, both in terms of the location of the students and the location of the tutors.  One other thought from my side is that it is also important to emphasise to all students that they are encouraged to go to any of the tutorials that they might find in the tutorial finder (so they can discover evening as well as weekend events).

Some tutors use materials that are created by the module team, whereas others create their own materials.  One example is the London region tutors creating materials in structured English, with a view to trying to ‘plug a gap’ in the module materials (regarding how students new to programming might set about splitting a program into different components).

Another approach that some tutors adopt to use their allocated on-line time is to run on-line drop in sessions via OU live.  The idea for this is that students could just pop into an on-line room to have a chat with a tutor if they had any questions.  I personally find this a really compelling way of making use of the on-line rooms, particularly when students might be wishing to chat about programming.  The breaks with the formality of a one-to-one conversation of the technology, but also allows participants to see what is being displayed on a shared whiteboard.

Working with OU Live

The first tip (for tutors) was, ‘remember to switch on your microphone’.  Another thought was, ‘can we make headsets compulsory please?’  The reason for this is simple: when students use the microphone and headset that is built into a laptop, a whole group of participants can be easily distracted by feedback, making communications a whole lot more difficult.

In some respects, participating in an OU Live session can be quite intimidating and one observation was that there are lots of students who don’t want to speak at all.  Sometimes some students prefer to use the text chat window rather than using the microphone, which can then make if quite difficult for the tutor to keep on top of everything (which is why some regions share OU Live sessions between tutors).

One point was that it is useful to ‘do something’ every 20 or so seconds.  This might be asking students questions, requiring them to respond with yes/no answers.  Another thought is to use a series of polls to assess understanding of certain concepts.  (One thing that I have personally learnt from my experience with the South East of England training is to poll students using the, ‘happy face’ button, i.e. by asking the students, ‘is everyone happy?, can you click on your happy face?’  When you regularly ask this, it helps to keep the student’s attention).

Marking of code

This section of the plenary discussion echoed an earlier point, that when it comes to communicating what needed to be done with complicated TMA questions (which involve programming), could the module team produce a video about how things should run, or have been constructed (using Sense)?

I’ve learnt that there are two different ways to add comments into Sense code.  One way is to use something called a comment window.  Another is to add some in-line comments.  I made a note of a debate about the use of different types of comments and that in previous assignments a TMA question asked students to add comments.  The consensus was that comments help; they help students to reflect on the code that is being written and help tutors to understand what has been submitted.

Project retain

An interlude between the first and the second session was presented by Maggie King, our associate dean for teaching and learning.  One of Maggie’s responsibilities has been to be a part of a university wide project called ‘project retain’.  

Project Retain is intended to increase the university’s retention (and progression) of students across different levels of study.  The project has given the university a number of recommendations, which include: offer a guide to key learning points and module materials, schedule and communicate real-time contact sessions during the first two weeks of a module (ideally through a letter), open module materials and web sites before the module starts, and make it clear when assignments are coming up (so our students are not surprised when they have to submit their assignments).  The first year of study, it was argued, is absolutely crucial.

Session 2 : Retention

Terry, one of our experienced TU100 tutors facilitated the second main session of the day, which was also about retention (which is an issue that affects student satisfaction scores, recruitment and funding). 

Terry introduced us to HEFCE performance indicators.  These include dimensions such as the national student survey and other aspects such as the measurement of research performance.   Terry also introduced the difference between retention and progression.  Progression is all about moving from one level of study to another.  In some circumstances students can defer, allow them to take a bit of time out from study and enabling them to pick up a module again at a later date.

One of the biggest changes in the university in the forthcoming couple of years will be the introduction of something called student support teams.  Since more and more students will be registering with the intention of studying for a particular qualification, student support teams will play an important role in helping students with their choices along a student pathway – it is hoped will positively impact on student retention.

Terry covered a wealth of materials, including sharing with us points from a national audit office report, drop out rates, how retention in UK HEIs compare with the retention in other countries, and how the university compares with others in the national student survey.  During his session Terry asked us to consider the causes of student drop out during different stages of study, such as pre-entry, induction, on-programme and movement to the next level.  In the university both tutors, student advisors and module teams all have an important role to play.  The final question of the day was, ‘how can the university support you in the task of improving retention in your tutor groups?’  This was an exceptionally very good question to ask and is something that I’m keen to pick up on and delve into when I have a bit more time.

Session 3 : Open Session

I have to confess that I haven’t taken too many notes about this final session mainly because we ran out of time!  Everyone was very willing to share experiences and opinions throughout the day, which was one of its fundamental objectives.

Reflections

One tutor made the comment: ‘you can make a full time job of teaching TU100’.   TU100 is, without a doubt, a very big module: there is a lot of material and there are a lot of demands on the tutor’s time.  What struck me about this day was the willingness of tutors to do their utmost to help their students along their TU100 journey and their willingness to share experiences with each other.  The event had lots of energy and there was a lot of positive talking going on, yielding some very good ideas.  From my own perspective, I certainly hope to be running a similar event next year.  I’ve already had a couple of thoughts about what we might do.

I have learnt quite a few things from this session.  I’ve learnt about the opinions that tutors have about certain aspects of the module and I’ll be happy to forward these directly to the module team.  It is also clearly apparent that some students struggle with programming and the idea of producing some video material to help to explain certain concepts might be something could be useful.

Acknowledgements

Many thanks to all our TU100 associate lecturers who kindly gave up their valuable time to attend this event on a Saturday. If any of the tutors who have attended would like to add further comments, please don’t hesitate to comment below.

Permalink 1 comment (latest comment by Jonathan Vernon, Tuesday, 2 July 2019, 11:32)
Share post

This blog might contain posts that are only visible to logged-in users, or where only logged-in users can comment. If you have an account on the system, please log in for full access.

Total visits to this blog: 2357366