Research - ICSE2010Tutorial12
Download
Report
Transcript Research - ICSE2010Tutorial12
What is Ethnography?
© deSouza, Dittrich, Sharp
Ethnography
• Form of participant observation
• Making the implicit explicit
• Regard what you see as ‘strange’
Dr Xargle’s insight that earthlets come in four colours
— pink, red, brown and yellow — but not, interestingly,
in the colour green
© deSouza, Dittrich, Sharp
Ethnography - definition
• Greek:
1.
ethnos = nation;
2. graphein = write;
Writing a culture;
• An approach/ research method to allow one to gain
an understanding about the informant’s point-ofview;
3
–
The main focus is on the informant’s point of view. What
is and is not important, relevant, interesting, painful,
exciting to the informant. Not to the researcher.
–
The researcher aims to gain this understanding and write
about it. Writing is as important as everything else.
© deSouza, Dittrich, Sharp
Ethnography’s hallmark is the notion of participant
observation, the idea that you learn about other
people's cultural practices by going there, being
there, and by doing it with them. Most traditional
anthropologists who would consider themselves to
be ethnographers have spent years living in other
cultures with people, and not just watching what
they do, but actually doing it too
4
© deSouza, Dittrich, Sharp
“Ethnography comes out of anthropology.
Anthropology would be the study of people and
culture at a pretty broad level. Ethnography is
about trying to make sense of people, not as
individual personalities, not in a psychological
sense, and not as societal movements, but as
people embedded in what Clifford Getz used to
call "webs of significance." It's thinking about
people from the multiple ways in which they
identify themselves, in a very
holistic way.”
(Genevieve Bell, May 2004).
5
© deSouza, Dittrich, Sharp
Why should we care?
– Ethnography allows us to understand the
informant’s culture including his values, beliefs,
power relations, myths, and, what is relevant to
us, work practices
– To design, develop, build, evaluate (and sell)
solutions that are useful
– To provide insight to improve practice
– Ethnography considered harmful
Crabtree, A., Rodden, T., Tolmie, P. and Button, G. (2009) ‘Ethnography
considered harmful’, in Proceedings of CHI 09, 879 – 888.
© deSouza, Dittrich, Sharp
Ethnography - History
1915 - Bronislaw
Malinowski’s “Argonauts of
the Western Pacific”
– The modern approach for
field studies. Field studies
should be in the field, not in
a library as done before;
– Focus on exotic, “primitive”
cultures, on understanding
institutions, costumes and
daily life;
7
© deSouza, Dittrich, Sharp
Ethnography - History
Chicago School of Sociology – 30’s to 60’s
– Broad research program focusing on urban northamerican life [Dourish, 2004 pag. 60];
– Lead to several studies of
• marginalized [sub]-cultures: drug addicts, prisioners, etc.
• Specific aspects of work including medical school students,
nurses, policeman, teachers, etc.
– This is relevant because it introduced a concern with
work practices, with how work is carried out by social
actors. This eventually lead to the adoption of
ethnography in the study of use, design, development,
and deployment of computational tools [Dourish, 2004
p60].
8
© deSouza, Dittrich, Sharp
Ethnography - History
In HCI / CSCW,
Suchman’s “Plans and
Situated Actions”
(1987)
– A critique to the AI
planning model;
– The planning model
was embedded in the
design of computational
devices (in the UI);
© deSouza, Dittrich, Sharp
Examples of Ethnography in
HCI/ CSCW
• John Hughes, Bentley,
Randall, Rodden, and others
from Lancaster: air-traffic
controllers;
• Julian Orr (1996): copymachine technicians;
• Bowers, Button and Sharrock
(1995): printing machines;
• Nardi (1990): spreadsheet
users;
• Heath and Luff (1992): London
Underground controllers;
• And several others.
10
© deSouza, Dittrich, Sharp
Ethnography in Software
Engineering
Ethnographic studies as a resource
• Understanding users and their activities
Embedded into methods
• Coherence (Viller and Sommerville)
© deSouza, Dittrich, Sharp
Ethnography of Software
Engineering
Software Engineering as Cooperative Work
• Artificial Intelligence as Craftwork.
• On occurred practices in software engineering.
• The user as a Scenic Feature.
• Multi Organisational Middleware Development
• ...
Why is it difficult to research software engineering?
• Software engineering is a highly skilled practice
• Software is not visible as such
• Software development is coordinated via ‘texts’ only
© deSouza, Dittrich, Sharp
Ethnography in
Software Engineering Research
• A study on maintenance work (Singer et al)
• Ethnography on agile development (Sharp
et al)
• Configuration Management (Grinter)
• Research on distributed development
(DeSouza, Singer, and more)
• Usage-oriented development practices
(Dittrich et al)
But it’s often not only ethnography
© deSouza, Dittrich, Sharp
Why Ethnography is Difficult to
Apply in Software Engineering
• Researching ‘up’.
• Engineering is not only about understanding but
about deploying the understanding for
improvement.
• It is not only the research community that expects
improvements: We expect that ourselves, as well
as the people we research with.
• We get involved with ethics in a different sense
than pure social scientists.
... And what about publishing Ethnography in SE?...
© deSouza, Dittrich, Sharp
Suitable research questions
‘How do software practitioners develop systems using XP?’
rather than
‘Is single programmer coding more productive than pair
programming?’
‘Why don’t Financial mathematicians adhere to a company
manual of software development practice?’ rather than
‘Does structuring the manual in this way help financial
mathematicians produce more lines of code an hour?’
‘What are the characteristics of a technology adoption?’
rather than
‘How did the ideas of Simula develop into Java?’
© deSouza, Dittrich, Sharp
Practical Exercise
This exercise will be a chance to start
working with some real data collected by
one of the presenters
• Read the transcript (5-10 mins)
• Write down up to 6 impressions you have
from the data (10-15 mins)
• Work in pairs if you like
16
© deSouza, Dittrich, Sharp