Category Archives: Professional development

Rigour in journal articles

These points are taken from a talk by Sara Hennessy about assessing rigour in papers submitted to the British Journal of Educational Technology.

  • Is the account analytical or purely descriptive?
  • Do the authors critique the literature and present a balanced account or does the review gloss over known issues with educational technology initiatives?
  • How do the theoretical assumptions and explanations of the case compare with alternative explanations?
  • Are links made in the discussion/conclusions back to the conceptual framework?
  • Are the findings critically interpreted in relation to the existing literature?
  • Do the research questions convey genuine inquiry or do they assume that educational technology is a Good Thing?
  • What is the theory of change?
  • Were there any potential sources of bias?
  • What measures were taken to counter them? eg were any counter examples sought when collecting and analysing data?
  • Does reporting seem selective? Are the analyses systematic and explicit? Is the account reflective and evaluative?
  • Was there any kind of control in a technology intervention design?
  • Are there threats to validity and reliability? Does inadequate control of extraneous factors threaten validity of theoretical inferences from data?
  • Are limitations acknowledged?
  • Could reactivity have played a role? Did novelty value of shiny new tools increase motivation?
  • How robust are the claims – how adequately is the argument supported by the evidence provided?
  • Does the sampling strategy permit empirical generalization to a larger population?
  • Who is the audience? Is the work relevant and current?
  • Are there clear conclusions that generalized beyond specific case/context? Do they apply in other institutions?
  • Is the work applicable / of interest in other countries? Is the focus overly parochial?
  • Is educational technology serving only the privileged in developing countries who already have access?
  • SES and gender inequity, rural/urban divide, language, computer literacy, bandwidth and intermittent connectivity / electricity maintenance, technical support, gatekeepers / stakeholders, culturally appropriate content….
  • Is the research innovative or, at least, original
  • What is the significance and contribution to existing knowledge – theory? methodology? empirical data?
  • Has the innovation been tested with real users?
  • Are there any convincing learning outcomes?
  • Are there explicit implications for practice? Policy?
  • Many reports of interventions motivated by ‘how can I use…’ rather than educational need
  • How is it used, by and with whom, how often, for what purpose, under what conditions, with what support…
  • What is the role of the teacher? Has pedagogy-focused professional development been offered? What cultural shift in teacher and learner roles is necessary?

 

Giving a conference presentation

I’m just back from the LAK17 conference in Vancouver. While I was there, I talked to a professor who had given feedback to doctoral students on their presentations in previous years. In most cases, it was the first time they had ever had feedback on their presenting skills. Thinking back to some of the talks I have heard from senior academics, I would guess that some have never had any help iat all in this area.

For me, an important part of presenting is the interactive aspect. If I see people looking puzzled, I try to go into more depth. If I see people looking bored, I’ll try to shift the pace. If a group of people arrives late, I’ll do a brief recap. If something of note happens in the room (loud noises outside, a phone going off , a butterfly circling overhead) I’ll try to react. A presentation is an opportunity to engage an audience and also to engage with an audience. I try to achieve that. I’m not claiming that I always succeed, but it’s always something I aim for.

The opposite of this approach is someone who reads a prepared script. I can see the attraction – particularly if you are nervous or if you are presenting in a language you don’t speak well. However, it’s usually far more difficult for an audience to follow. You put in more words. You use longer words. You start adding in citations. Your audience may be extremely familiar with the major works of every single person you cite – but it’s unlikely. If you cite two or three people in a single sentence, even the most skilled audience will be struggling to keep up. If everything you want to say is in the paper, people could just read your paper. Your presentation needs to offer something extra.

Small text doesn’t work. If you want your audience to read it, it needs to be big. If you are presenting to a large audience in a large room, your text needs to be very big. Unless it’s there as an example of illegible text, then small text serves no purpose. Long text has similar drawbacks. Either you have to pause awkwardly while the audience reads it, or you have to read it to the audience while they are reading it themselves, or you talk over it and the audience isn’t listening because they are reading the text.

You can run into the same problem with inexplicable images. For example, you put up a picture of a bear because you are talking about a big problem and you see a bear as an example of a big problem. While you talk about the issue, your audience is busy running through possible explanations for your choice of image. Woodland creature? About to hibernate? Likes honey? Lives in Canada? I once spent 20 minutes trying to figure out the use of an image on the second slide of a presentation. It was a presentation about a strong piece of work – in fact, it later won the prize for best paper – but I didn’t hear a word of it, because I was so distracted by the image.

Images also routinely get used without accreditation. People who scrupulously attribute the sources of their ideas use pictures without any reference to their creators. Sometimes, they even use ones that are have watermarks making it clear they are commercially available and should not be used without permission. It doesn’t take much effort to find images licensed using Creative Commons (you can filter your searches on both Flickr and Google Images in order to return these images). And when you use the images, credit them. Credit the work that went into them. Creative commons usually requires the author’s name and a link to the appropriate licence. This isn’t arduous, and it’s acknowledgment you would give to others whose work you have used.

A final thought. Your final slide. This is the one that stays up through the questions and answers that follow your talk. It is the slide that the audience spends most time looking at. Don’t waste it by filling it with ‘Thanks!’ Reiterate your key point. Provide a link to your work. Offer your contact details. Pose a question. Help the audience to engage with you once your presentation has ended.

A PhD is more than a thesis

Inspired by a Tweet I read recently about the distinction between a thesis and a PhD, I have been thinking about the difference between the two.

The university really focuses on the thesis, which must :

  • be of good presentation and style
  • be a significant contribution to knowledge and/or to understanding
  • demonstrate capacity to pursue further research without supervision
  • contain a significant amount of material worthy of publication or public presentation.

What else? Well, our university specifies you must be a registered student, you must live in the UK, you must pass your probationary period, you must spend a minimum amount of time as a registered student, you must make satisfactory progress, you must have a viva, you must make any specified corrections and you must present your thesis according to the guidelines.

All very thesis focused.

Vitae has a Researcher Development Framework that covers knowledge and intellectual abilities;  personal effectiveness;  research governance and organisation; engagement, influence and impact. The university encourages students to engage with this but, apart from reporting satisfactory progress at probationary review, it isn’t enforced or assessed.

Typically, students are assessment focused. They learn what they will be assessed on. It’s not surprising, then, that many doctoral students focus their entire attention on the thesis. That is the centre of their activity – everything else that takes place at the university is a distraction and has lower priority. In extreme cases, they only visit the university for supervision sessions, talk to nobody but their supervisors about their research, and focus totally on putting their thesis together and passing their viva.

But what then? A PhD is one line in a CV – perhaps five or six if you bulk it out with a description of your research. Permanent academic jobs in the UK and in many other countries may not be as rare as hens’ teeth, but they come pretty close. Even fixed-term contracts are difficult to get.

For employers, the PhD is not just one line in a CV, it’s also one line in a long job specification.

Academic employers want to know that you can publish papers, put together grant proposals, attract funding, increase impact via social media, create course materials, teach, mentor, work as part of a team, initiate projects, provide connections to a wider academic community and work on several projects at the same time.

The people getting the academic jobs are the people who can produce evidence that they can do all those things, and that they have already done those things. The people who treated their PhD as a period of academic apprenticeship, when the thesis is just one activity among many. The people struggling to get a toehold in the academic sector are the ones who have simply written a thesis.

Scrum management framework

With its scrums, sprints and stories, Scrum Management always sounds intriguing. I’ve been involved with several teams who have either used this system knowingly, or have employed elements from it. However, I’ve never seen the process formalised until I spotted it in the January 2015 edition of Wired magazine (where they had compressed a version of Jeff Sutherland’s book). Wikipedia tells me that this style of software development emerged in 1986 – so I guess I’ve been slow in investigating the approach.

Wired describes it as a seven-step process:

1. Small  teams. These should include the product owner, who has the vision and decides on the order in which things should be done, and the scrum master who facilitates communication and removes obstacles.

2. Tell stories. Each new features should be associated with a short story about the user and why the feature will add value for the user.

3. Assign effort points. Compare the stories and give them points for effort involved (or T-shirt sizes: small, medium, large and extra large).

4. Prioritise features. Each sprint should end with something that can be demoed, so make the chunks of work small enough to fit into a sprint.

5. Sprint. A sprint should be 1-4 weeks long – long enough to deal with a set amount of effort points.

6. Scrum. A 15-minute meeting every morning, standing up, so you’re not tempted to settle in. Three questions. What did you do yesterday to help finish the sprint? What will you do today to help finish the sprint? What obstacles need to be overcome?

7. Sprint review. At the end of the sprint the team meets to discuss what has been achieved, and to improve working practices for the next sprint.

 

OpenPAD

HEA accreditation is a ‘recognition of commitment  to professionalism in teaching and learning in higher education’.

You can be an associate of the HEA, a Fellow, a senior fellow or a principal fellow.

At the OU, this will be replacing our taught courses such as the postgraduate certificate in teaching and learning in HE and the postgraduate certificate in academic practice.

People who benefit will include central academic staff, staff tutors, ALs…

To participate – engage with the wiki, the resources and the faculty-based forums on the OpenPAD Moodle site, have support from a faculty mentor, completion of practitioner inquiry based on own practice, this should take 6-12 months, and will be assessed by he accreditation panel for OpenPAD fellowship. This will lead to both internal and external accreditation.

IET provides accreditation for staff via the HEA.