User:Sputniza/Interview guide line

Interview guide line/ 1st draft
I suggest the oral conversations to be held as semi-structured interviews. This is to ensure there will be a common base for evaluation of the results, as well as enough place for individual ideas and comments of the participants. The following is to give an idea about the structure of the interview - to discuss it - without determined wording.

Introduction
Short introduction of myself and introduction of the participant.

1st part - Technical Info/ Personal Data
About the participant of the interview (if not provided yet in the introduction).
 * function (instructor, student, ambassador)
 * experience with the course page system (courses held/ participated in e.g. size of the courses, results of the past courses, frequency, amount, fields of study)
 * related experience/ background (use of wikis, wikipedia, use of other software in course administration)

2nd part - Structured Questions/ Experience with Course Pages

 * collecting overall impressions (look and feel)
 * concrete working experiences of the participant
 * documenting possible struggles/ problems concerning both functionality and design
 * going in detail on the quality of working with single aspects of course page software
 * ideas for improvement of given functionality
 * additional functionality (wish list)

added (from Sage's comments)
 * on-wiki feedback from the instructor to the students/ find out whether they have done that before (and if not, why not), and find out what (if anything) would make them more likely to do so (tools needed)
 * how to design software to help with the problem of grading
 * how important is cross-wiki-integration of the extension?

3rd part - Additional Questions

 * ask additional questions of the participant to gain greater detail in their responses
 * ask the participant, if there is anything, she/ he would like to add?

Feedback and Notions from the talk with Kacie Harolds
Kacie led some interviews on a wider scope (concerning not only the EP extension, but the education program as a whole) and I had the chance to talk to her and to profit from the observations and experiences she made

- how important it is to have the questions in advance - there might be need to reframe the questions after first experiences - the necessity to redirect your interview partner sometimes to the subject of the interview, as people tend to get carried away (and the point about mentioning this in advance - I may need to interrupt you..) - she mentioned some people, who might be interesting or helpful to talk to - what she was told about the extension (short short summary): people find it a considerable high barrier to use it, but if they made the effort, finally find it very useful and feel content about the functionality the EP extension provides (this agrees with our impression as well)
 * she provided me her script of the interview she led
 * we had a long conversation, where among others, she stressed -