Göm menyn

Requirements and Grading

To pass this course you have to:
-    individually hand in and pass on all literature summaries that are part of the literature seminar
-    take part in a project work in groups of 4 people

1. Literature Seminar

You will have to read, understand and write a short summary of the selected literature for each theme. The literature for each theme is given here.

The summaries shall:

  • consist of about 1000 words (in total)
  • include two questions/reflections that could be raised in the lectures or in your project work.
  • be delivered as pdf or word document to the responsible teachers

You are supposed to hand in your summaries one day prior to the lectures - make sure to check the deadlines in the timetable!

A good summary should convey the impression that the writer of the summary has read the article and it should be written in your own words, not “copy-pasted” from the source. It will take some time to read the articles and write a good summary, make sure you start in due time!

Each literature summary will be graded on a pass/fail basis. To complete the course successfully you have to pass on all summaries that you hand in.

Grading scheme for the literature seminar: pass/fail (U,G)

2. Project work

Your mission is to find an information system (or an information system that is about to be implemented) and apply all the perspectives on IT-evaluation that have been presented in the course. You are responsible for identifying the case that you want to work with. The system can be of any kind. But it will most likely be easier to apply the theoretical models (that we have discussed in the course) if you choose a system that is used/will be used in an organization, and that is aiming for some kind of apparent effects in this organization. We expect you to refer to all five perspectives, but it is your choice if you treat them in equal proportions or if you want to give one of the perspectives more attention.

The project will be carried out in groups of four. You create the groups your selves and send us your group information after the first lecture.

There is always a risk in this type of assignment, that the work starts too late. Therefore we kick off the project assignment already before we have finished the theoretical part of the course.

For documentation and feedback purpose we will also take advantage of Lisam, the university’s internal communication and collaboration platform. Instructions on how to work with Lisam will be given in the class.

2.1 Project proposal

Already in the third week your group will present a project proposal to the rest of the class. It should include a description of the system you are about to study, a description of the stakeholders that have/will have a relationship to the system and a broader description of the context.

For the remainder of the course there will be repeated contacts with the teachers. They will assist you in the project work.

2.2 Evaluation focus

Till 2014-09-24 you have to hand in an extended version of your project proposal that includes some more detailed information about your evaluation focus, aspects that you identify as important to your case and a first idea how those aspects might interact.

2.3 Half-time seminar

In week five you will present your project to the rest of the class and get comments from them as well as give comments on another team’s work.

2.4 Virtual seminar

In week six we will run a “virtual seminar” on your project. You will read two peer groups' reports-in-production and feedback on them (and get comments from two peer groups on your report).

2.5 Final presentation

In week seven you will present your final project report, which should be based on a multi-perspective evaluation of a system that you have chosen, as well as an analysis of the evaluation and the evaluation process as such.

You will also read and prepare a discussion of two other groups' reports, and read at least the executive summaries of all the other reports in your session, to be able to follow those presentations and discussions.

2.6. Report structure

The report structure shall follow conventions for writing an academic report. This means you shall principally provide a motivation, a description on background and context, your methodology, the theories that you have used, the empirical setting, your analysis, discussion and conclusion. You shall also provide an executive summary - a presentation of the main points of the report in no more than one page for the hurried reader.

The report shall comprise about 10 - 12 pages of text (excluding executive summary, table of contents, bibliography, figures, tables, appendix).  

When writing the report make sure to use proper reference management software (e.g. Word's built in system, Latex, Zotero, ...)

Grading scheme for the project work: (U, 3, 4, 5)

3. Final grade

The overall grade will be mainly based on the final report of the project work, as it deals with the content of the entire course. Well written summaries that demonstrate that you have reflected upon the course literature, and constructive participation in class, can earn you a bonus and positively influence your overall grade.

To pass the course you have to pass on all literature summaries and the project work.

Grading scheme for the entire course: (U, 3, 4, 5)


Sidansvarig: carl-johan.petri@liu.se
Senast uppdaterad: 2014-09-03