25 January 2010

On explaining grades

The linked piece is a column (dated yesterday but I think I've seen it before) in the Chronicle of Higher Education by Gina Barreca of the University of Connecticut. What I found most remarkable was not the piece itself but part of the first comment:
"Nobody should explain a grade to a student."
As flat and dogmatic as that. On the contrary, nobody should ever give a student a grade without explanation.

The principles of formative assessment (or "assessment for learning") suggest strongly that students can learn an enormous amount from good feedback. Indeed, Hattie concludes that the single most effective way of improving learning is to give "dollops of feedback". And all assessment can be formative. The mark or grade is simply a summary or proxy for the feedback, but it is so abstracted as to give practically no information. On a course on which I currently teach, there are no grades, just "pass" and "refer" (which caan lead to an outright "fail"). But there are dollops of feedback.


Last week one of the participants--"student" is not quite the word for well-qualified professionals in their fields who happen to be learning to teach that field--did ask a colleague for a grade.He demurred, but he could see how uncomfortable it made her. She had been through school, an undergraduate degree and a Master's getting grades all the time; a piece of work had not been properly assessed unless it got a grade, as far as she was concerned even if as in this case, it carried credits if it passed.

It's interesting that the education system is so hooked on grades; in the rest of the working world we get plenaty of feedback, but only in teaching do we get graded (by Ofsted)*.

I suspect that the sub-text of the original comment is that no student should ever question the judgement of a faculty member, however arbitrary.

*Not entirely true, but substantially so.

Labels: , ,

08 December 2009

On an ingenious approach to marking assignments

Steve Hill of Southampton Solent University has been experimenting with Camtasia, a screen recording package which also takes audio, as a means of recording his spoken comments on students' work, which he can then send to them.
Students submit assignments electronically using our Moodle-based VLE. I then get a student’s Word file on screen and edit it, whilst simultaneously giving a live commentary on the changes that I’m making. This is like giving a student their own personal tutorial.
Sounds like an excellent idea!

Labels: , ,

08 May 2009

On feedback

Do read the linked column—and, as important, the comments.

The author (now a professor) has kept her former professor's annotation of an essay she wrote in her second year as an undergraduate. She reproduces them and her readers comment on them. It's fascinating, and also rather disconcerting to see how many ways the notes can be interpreted, as well as to consider whether that kind of feedback would be acceptable thirty years on.

Labels: , , ,

19 November 2008

On less being more at Master's level

I have been on a validation panel today, grappling with the problem of how to specify modules at Master's level. It was very instructive.

The team developing the programme had understandably assumed that outcomes for a Master's level module would have to be more tightly specified than for a lower level course, in order to ensure that the learning and the assessment would be at greater “depth” than for an undergraduate module.

First, though, it is quite easy to specify “learning outcomes” for low-level courses. When people are learning the basics of any subject or skill, what any one person learns will have to be the same as any other learner. It's easy to assess, and “correct” knowledge or performance is clear-cut. It's not so easy at higher levels. Knowledge and “understanding” (not to mention, for those who care, the higher regions of Bloom, or Krathwohl and Anderson) may be contestable, and indeed one person's understanding or “take” on the subject may quite legitimately be different from their neightbour's. So when you get to Master's level it may be reasonable to specify that the outcomes will include so-and-so, but it may well be patronising and simply counter-productive to presume to set them out completely and exhaustively.

Even so, how do you incorporate the academic level requirements into the outcomes? It's traditional to use all those recommended “Bloom verbs” to produce “SMART” objectives. (What's the difference between an objective and an outcome, in this context? Strictly between ourselves, I no longer have to pretend that I know, and I don't care.) So the first-year students “list” or “describe”, the second-years “analyse” and the third-years “evaluate”... So Master's students? They “critically evaluate”, it seems. (That means in practice that they evaluate on the basis of one or more over-arching frameworks, showing that there are no simple answers.)

That is fair enough but it does risk becoming formulaic, and also implying that there is a correct procedure for doing it. The more specific the directions, the more restricted the outcomes, and the less the scope for the exercise of individual initiative and creativity (if that is desirable in your discipline, of course!) Master's students are experts, or at least nearly there. They need to be given their heads rather than constrained. (I am referring mainly to experienced practitioners of their discipline undertaking Master's study part-time, here; I am aware that full-time “second cycle” students who were undergraduates last year may not fit this picture.)

Personally I would rather just set out the aims of the module just so the students know what they are letting themselves in for, and recognise that the outcomes will be different every time it runs, and different for every participant. But that won't wash in the compliance climate where standardisation is all. So what can we get away with?
(Specify the level and assessment criteria at a scheme/programme level so you don't have to do it at a module level)
"On completion of this module, participants will (I prefer “participant” to “student” at this level);
  • Come to their own informed conclusions about the significance of...
  • Explore ... in the context of ...
  • Use ... as the basis of original work on ...
Or have I got it wrong?

Labels: , , ,

25 October 2008

On the other side of plagiarism

Or "confessions of a term paper ghost-writer". Interesting in its own right as a sub-cultural phenomenon, but with a sound point at the end;

I don't have the academic credentials of composition experts, but I doubt many experts spent most of a decade writing between one and five term papers a day on virtually every subject. I know something they don't know; I know why students don't understand thesis statements, argumentative writing, or proper citations.

It's because students have never read term papers.

It's an exercise re-discovered time and again, like the wheel; get students to mark/grade and comment on specimen papers written for your module, so they know what they are supposed to look like.

Labels: , ,