IT-Universitetet

Guidelines for WiP sessions

During the last weeks of class we will scrutinize drafts of your final research papers by having work-in-progress (WiP) seminars in which you present your own writing and review others' work.Identifying the highlights and weak links from others' papers should help you avoiding the pitfalls you may encounter when writing an academic paper. Please do not underestimate the importance of writing a high-quality paper, as the exam format of the course is: External examiner, 7-point marking scale, C1: Written work without oral exam.

Logistics

Roles:

A (presenter)

B (reviewer)

C (audience)

Presentation tips for the author
Do not worry or get stressed if you feel your paper is “not ready to be presented yet”. The sessions are called “work-in-progress seminars” because the baseline is that you present more or less unfinished work. However, as the end of the course is rather near already, you should at least put together and submit a paper with your core idea surrounded with motivation, preliminary analysis and some critical discussion, i.e. you should have alpha or beta version of the final argument. Rather than leaving out ideas because of the lack of time to unpack them in writing, you should put them in some condensed form, e.g. as bullet points, and deal them in more detail in your presentation.

As the others will have read your paper, your presentation doesn’t have to be a faithful summary of the paper’s contents and you should instead just provide some initial followup comments, framing, you want to kick things off with. You might, for example, flag an area of the argument or data you have been struggling with as a way of getting useful feedback.

Reviewer guidelines
Put this info on top of anything else:

Your Name, email address
Review of [Paper title] by [Author]

The 1-to-1½-page (12 pts, single spaced) review should begin with an original 100-200-word summary of the paper you’re reviewing. The summary should cover the topic area, goals, research questions, the theoretical background, analysis, and conclusions (where applicable). This is to ensure you read the paper thoroughly enough to give meaningful feedback.

The summary should be followed with critical and constructive comments, or, proposals for improvements regarding, but not limited to, the areas listed below. Whether you write full-fledged sentences or bullet points is up to you, as long as your thoughts can be understood.

Subject area & motivation:

Theoretical background & relevant past work:

Research questions

Empirical work / material

Anything else

Please, be detailed when you comment on specific ideas, passages, or sentences in the paper. (For example, a comment starting with “When you mention rapid prototyping for the first time…” is much more useful as “In the 3rd paragraph on p.3, where you mention…”.) You can also make notes and markings on the printout of the paper you’re reviewing, so you can easily point out the passages during the discussion and, possibly, hand the copy with your marks to the author after the session.

See examples of good reviews and bad reviews at CHI2005 page.

After the session, remember to give one copy of your review to the author.