OU blog

Personal Blogs

Christopher Douce

TM470 notes

Visible to anyone in the world
Edited by Christopher Douce, Thursday, 16 Aug 2018, 14:48

The university has been going through a lot of changes. One of the side effects of these changes is that I have now become a home worker (which I’m a bit grumpy about). To prepare for a delivery of a new desk, I’ve started to sort out loads of old papers. The process usually involves looking at a bundle of papers and thinking, ‘why did I keep this?’

I recently stumbled across a hand written form that relates to my first year of tutoring on the TM470 project module. Rather than putting it in a file (or in the recycling), I thought I would transcribe it and share it. I hope it is useful to someone!

The form is divided into four sections:

Project themes (in my tutor group this year)

The form was asking for the projects that students in my tutor group chose. I’ve decided to edit this bit and be pretty general. The project were about: an app evaluation, a database implementation, and a website redesign.

Issues encountered (and how I resolved them)

One of the challenges was projects that had a very big or wide scope. Subsequently, another issue was projects that had a really narrow scope. It was sometimes quite difficult to get hold of some students. There were many students asking for extensions. The marking (of course) was quite challenging, and on occasions I was asked to do some remarking. It was also difficult to keep students on track, mostly because everyone on the project module is different and have their own circumstances.

What I have learned (including positives)

The first item I noted was: broadness of project topics. The students can, of course, surprise you. What struck me was the importance of the literature review in the module. I learnt more about how the project module was connected to other modules in the Computing and IT programme and also how it was different to other modules. It was useful to think of the module in terms of it being an ‘extension to level 3 modules’; creating a database isn’t enough: students need to demonstrate skills and go further in terms of either their understanding principles (such as transactions or concurrency) or the application of ideas. I also learnt the importance of sending out ‘update’ emails.

Ideas for next year (things I could do differently)

Each student is given four hours of support time. Different students and different tutors may use this time in different ways. One thought is: after initial contact (perhaps even by telephone), is to run an introductory tutorial for the student group. 

Another note I made was, ‘emphasise the library screenshare’; this comment relate to a session that is run by the OU library, to help students with a literature review. Another note I made was: ‘be a bit more persistent in terms of following up; call them after their TMAs’. Another thought was an interesting one: ‘try to get students talking to each other’. A related point was: get students presenting to each other.


Permalink Add your comment
Share post
Christopher Douce

TM470 New tutor day

Visible to anyone in the world
Edited by Christopher Douce, Tuesday, 22 Nov 2016, 09:46

I first joined The Open University as a part time tutor back in 2006 where I tutored a module called M364 Fundamentals of Interaction Design. Knowing that this module was coming to an end I decided to apply to tutor on another module: TM470 The Computing and IT project, and I was successful!

I was invited to attend a ‘new tutor day’ which took place in the West Midlands regional centre in Birmingham (which is, sadly, closing in the new year) to learn about the ins and outs of tutoring this module. This was also an opportunity to meet my TM470 mentor, fellow TM470 tutors, and some of my colleagues who support the delivery of computing and IT modules from the Manchester and Birmingham offices. This blog post has been drawn from a set of notes I’ve made during the day, which took place on 2 July 2016.

Project choice

I’ve noted down the question: ‘what makes a good project theme?’ It’s a simple question and one that is very important: students must have a clear idea about what the problem is that they want to solve within their project. It should also have sensible limits, i.e. students shouldn’t aspire to creating the next big app for the iPhone.

Successful projects are those that draw upon practical skills that have been learnt (or studied) in previous level 3 modules. A project could also build on something that has been done before. Students should (ideally) be knowledgeable about the domain or environment in which a project relates to (so they don’t have to spend lots of time doing research into an area that isn’t familiar to them). Also, importantly, a project should be connected with something that a student is interested in doing (so they maintain their motivation).

Another bit of advice is: students should stick with using software that they know; don’t be tempted to play with new things, since it’s easy to get tied up in knots.

Sometimes students might be tempted to draw upon projects that relate to their work place. An important point is: work and TM470 have different goals; it is probably best to keep work and study separate for the simple reason that changes at work might jeopardise the project. This rule, however, doesn’t have to apply in all cases: students need to understand what is required from TM470.

Another really important point is: a project doesn’t have to have a successful outcome to submit a final project report. Students can still pass if things go horribly wrong: it is the description of the project, the learning, and the reflections that all count towards the final scores. If these are done really well, students will get a really good pass.

Another note I’ve made is all about research: ‘not really understanding what is meant by research that is academic, or what is meant by an academic literature review (and analysis)’. Some projects may be research projects, in the sense that they are an in-depth and critical study of a particular area. If students choose research projects, the need to be clear in terms of what is required of them. 

Independent learning

TM470 is different to other modules, since what really matters is being able to demonstrate independent learning; tutors will not be subject experts in all the areas in which projects are chosen from. A note I’ve made is: ‘if software breaks, it is part of your job on a project to fix it’. The role of a tutor is to push a student into this mind set.

Practicalities

I made a note that we discussed the importance of the introductory letter, and that we might connect this to the use of our module discussion forum.

A really important resource is the OU Library which allows student direct access to a wealth of prestigious journals. Another thought is to direct students to library tutorials (understanding eJournals) about how they can get started.

The project module doesn’t have any official tutorials, since it is difficult to run group events where every student is working on a different project (and will have different learning needs and problems). This said, some tutors do use OU Live to run some unofficial introductory tutors. 

Towards the end of the day, we discussed practicalities about end of module assessment marking, and assignment marking. Key questions that were asked were: ‘how do you do it?’ and ‘what processes do you use?’ The module has a very clear set of marking guidelines that are also known to the students. Ultimately, everything comes back to the question of whether students have met the learning outcomes.

Reflections from first presentation

Now that I have more of an idea how the module works and how it is structured, I think I will run an introductory OU Live tutorial at the start of the next presentation. This will allow me to learn more about the student’s ideas and understand more about their potential problems. I will also use this to emphasise the importance of time management.

In comparison to other modules that I have tutored on, I found the marking to be pretty straightforward once I knew how it worked. It took me a bit of time to find the forms, and then to internalise the marking criteria (but this is always the case when starting to work on a new module). One of the things that I really enjoyed was looking at the diversity of the projects, and how the students tackled them.

Permalink
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: 2677253