Finally pictures from day 0 and day 1 start to appear on flickr – have a look.
And then to day 2 which started with paper session – as usual here some comments on the ones I found worth commenting ;-)
- “‘… and do it the usual way’: fostering awareness of work conventions in document-mediated collaboration”, Federico Cabitza, Carla Simone: “without conventions work could be hardly be done by practitioners (and be hardly understood by researchers)” – goal: supporting conventions through a “learning device”, need to understand their nature to create a common ground, clarifying ambiguities – conventions vs. business rules (spring from practice, not necessary a best practice, generated locally from the bottom, to solve local problems) – this seems to be quite important! use to support awareness (browsing awareness, alerting/reminding awareness, provisionality awareness, inconsistency awareness, amending awareness, accounting awareness, enabling awareness); “conventions are about action you are expected to do”, “conventions are about interpretation this means that”, conventions and awareness are expressed in terms of condition -> effects; further developed (visualization of awareness) in the WOAD approach … comparable to the approach of expectation awareness (by Prinz et al.) – the paper is surely worth reading in more detail (at least for me ;-)) – interesting idea to use conventions to support awareness event filtering and visualization …
Other blog postings on this talk: ECOSpace Blog - “A safe space to vent: Conciliation and Conflict in Distributed Teams”, L. Watts: conflict as potentially destructive (e.g. storing bad feelings for future interactions) vs. conflict as a creative process; conversations through CMC technologies are prone to conflict escalations, polarisation and entrenchment (Thomson & Nadler 2002) but also can encourage disclosure and reduce uncertainty! very good analysis of recent work on conflict in CMC
- “Semi-Synchronous Conflict Detection and Resolution in Asynchronous Software Development”, Prasun Dewan and Rajesh Hegde: Problem in software development: adding people to the team does not add to productivity in the same way; one reason for this: conflicts; not adequately addressed by versioning systems; solving problem: change virtual environment by new conflict management model (no synchronous pair programming!, but asynchronous work); they built a new systeme CollabVS = Visual Studio + Semi Synchronous Conflict Management and evaluated it; the core idea is somehow providing awareness by automatically detecting concurrent activities (editing code files that are somehow related) and visualizing the information.
One comment in the discussion: “Great and I would like to have it” ;-)
Other blog postings on this talk: ECOSpace Blog