Forgot your password?
Informal notes from discussions about this paper
Document Actions
James's Notes on May 10
The task has structure and it is somewhat controllable. The argument is that the structure of dependencies in Task impact the extent and style of shared mental model.
select a few high level dependancies, low level dependencies.
compare core and peripehry members
compare groups that are using different types of technology
sychronicity vs asynchronuous
- social presence
compare code management tools
- automated regression testing tool
In the face of high levels of interactive complexity shared mental models are a good way to do things, but actually tools can do some of this for us (eg regression testing).
Yeliz's Notes on May 10
Organizational Science Paper
·
IT enables
or constrains shared mental models (in short term)
·
In long term:
structuraction theory
·
We can use
Weick's scheme: Coordination, subordination, representation (built by
conversation, recapitulation, socialization)
·
Recapitulation
and socialization (we should unpack what socialization includes)
·
For heedful
interaction, document that there's a core and perifery and the periphery
doesn't interact with the core on the mental model. Understand how your actions
a
Using
IT to collaborate and building IT.
Studying
tasks: We're interested in the technology that supports the group
We
can get started with Gaim
Wait
until Praveen analyzes different software programs. And compare a
high-dependency project with a low dependency one.
We
can also compare technologies used (IRC versus Forums/Emails)
·
IRC might differ
in terms of social presence? (says James)
We
can look at project that use CVS versus non-CVS
Finding
a project without heedful interrelating and finding one with heedful
interrelating might be useful. (Theory says high level of interactive
complexity might require more heedful interrelating)
CVS:
has automated build system and regression test system.
C++
or C project (++ is better)
