28.03.2014 Views

isbn9789526046266

isbn9789526046266

isbn9789526046266

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Different phenomenographers define phenomenography differently, and there are distinct movements<br />

within the phenomenographic tradition, some of which are more closely tied to specific research methods<br />

than others are. Some of these variants could well be called methods or methodologies. Hasselgren et al.<br />

(n.d.) give an overview of the main flavors of phenomenography (see also Åkerlind, 2005c; Bowden and<br />

Green, 2005).<br />

Enough generic talk.<br />

17.3 Here is what we did in practice<br />

17.3.1 We collected data from interviews with programming students<br />

The way we conducted the interviews accommodates many of the considerations from the previous section.<br />

The interviewers<br />

To improve the trustworthiness of our research, we wished to have an interviewer who was independent<br />

of UUhistle’s development. On the other hand, the author of the thesis would be doing much of the<br />

analysis, some of it during the interviewing process, so we also wished to involve him in the interviewing<br />

so that he could make use of the early analysis to explore emergent themes in more detail.<br />

Consequently, two researchers collaborated to do the interviews. One interviewer, Jan Lönnberg,<br />

interviewed five students, and the author of the thesis interviewed six, making eleven interviews in total.<br />

The author was in charge of student selection.<br />

Both interviewers had some experience with phenomenographically motivated interview studies from<br />

earlier projects.<br />

Student selection<br />

Our interviewees were students taking the spring 2010 offering of CS1–Imp–Pyth described in Section 16.4.<br />

A couple of weeks into the course, all the students of CS1–Imp–Pyth answered an online questionnaire<br />

in which they were asked to rate their programming background, their attitudes towards programming,<br />

and the workload and difficulty of the CS1 course so far. We used the answers to this questionnaire,<br />

and the results from the assignments submitted, to mold our interviewee selection process so that we<br />

got a mix of interviewees with different backgrounds, attitudes, and estimates of course difficulty, as well<br />

as a mix of scores from the course assignments. Such a selection, we felt, would give us a good basis<br />

for exploring the variation in ways of experiencing. The interviewees also came from a variety of degree<br />

programs within engineering.<br />

We surmised that students who had a harder time with the course or were less enthusiastic about it<br />

would have more trouble seeing VPS in a rich way and might be a good source of data for studying partial<br />

understandings of the phenomenon. We therefore skewed our selection process towards such students,<br />

inviting more of them and fewer of the experienced and motivated students. The selection process was<br />

unformulaic and involved randomly picking out names from a list until we had what appeared to be a<br />

suitable mix.<br />

Given our research interest, we ensured that all our invitees had submitted an answer to at least one<br />

VPS exercise; most had submitted many.<br />

The interviews were conducted partially in parallel to the experimental study described in Chapter 19.<br />

We checked that none of our invitees had been part of the experimental group in that other study.<br />

Both the interviewers had taught at our university in past semesters. We confirmed from our<br />

department’s records that none of the students was interviewed by a researcher that the student had<br />

previously taken a class with.<br />

276

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!