This is Just an Example for HCI Stories of Transfer

1st Author Name
Affiliation
Address
e-mail address
Optional phone number / 2nd Author Name
Affiliation
Address
e-mail address
Optional phone number / 3rd Author Name
Affiliation
Address
e-mail address
Optional phone number

ABSTRACT

This is just a crude example. If you prefer some another way to tell your story, please feel free to do so.

‘old’ method-resources in new context(s)

In this case study we describe how the following method-resources are applied across two or even more different contexts. Note that contexts can be different due to many circumstances: the move of a method user to a different company, the start of a new project within a company, changing constraints with the method user’s work context, etc.

A list of examples [1] is given below, please identify relevant ones and other not listed for your case

·  Participant recruitment

·  Task selection

·  Reporting format

·  Problem identification

·  Problem classification

·  Analysis

·  Heuristics

·  Thinking aloud protocols

·  [Others]

Description of Original Application Context

ABC is a small and medium enterprise (SME) focusing on the development of web-based mini-games for young children…

Description of New Application Context(s)

XYZ is a global enterprise targeting the development of business software applications such as decision-making tools…

Stories of Transfer: Triumph or Tragedy or Both?

When I was working in company ABC, I recruited participants by asking people at lunch to try my prototype, but when I moved to company XYZ, I had to recruit people from outside the company as a budget was available for this purpose....

:

:

:

We tend to conclude that the transfer has been a great achievement or an utter catastrophe…..

Analysis of contextual factors

The triumph (or tragedy) of transfer can be attributed to the following factors

A list of examples [1] is given below, please identify relevant ones and/or others for your case. Elaborate how the factors influence the application of method-resources.

·  Business goal

·  Design purpose

·  Development context

·  Team skills

·  Corporate culture/values

·  [Others]

REFERENCES

[1] Woolrych, A., Hornbæk, K., Frøkjær, E., & Cockton, G. (2011). Ingredients and meals rather than recipes: A proposal for research that does not treat usability evaluation methods as indivisible wholes. International Journal of Human Computer Interaction, 27(10), 940-70.

The columns on the last page should be of approximately equal length.
Remove these two lines from your final version.