@inproceedings{citeulike:1022639,
        title = {Identification of coordination requirements: implications for the Design of collaboration and awareness tools},
        address = {New York, NY, USA},
        author = {Marcelo Cataldo and Patrick A. Wagstrom and James D. Herbsleb and Kathleen M. Carley},
        booktitle = {CSCW '06: Proceedings of the 2006 20th anniversary conference on Computer supported cooperative work},
        journal = {Computer Supported Cooperative Work, 2006, CSCW '06. 20th anniversary Conference on},
        pages = {353--362},
        publisher = {ACM Press},
        year = 2006,
        url = {http://portal.acm.org/citation.cfm?id=1180875.1180929},
        id = {1022639},
	priority = {5},
	isbn = {1595932496},
	doi = {10.1145/1180875.1180929},
	description = {Cites from CiteULike},
	abstract = {Task dependencies drive the need to coordinate work activities. We describe a technique for using automatically generated archi-val data to compute coordination requirements, i.e., who must coordinate with whom to get the work done. Analysis of data from a large software development project revealed that coordina-tion requirements were highly volatile, and frequently extended beyond team boundaries. Congruence between coordination re-quirements and coordination activities shortened development time. Developers, particularly the most productive ones, changed their use of electronic communication media over time, achieving higher congruence. We discuss practical implications of our technique for the design of collaborative and awareness tools.},
	biburl = {http://www.bibsonomy.org/bibtex/22f4651cdfbbaeee8257d84de9296032c/fcalefato},
	keywords = {gsd, ditributed, coordination, collaboration, reticollab0607 awareness,}
}

@inproceedings{citeulike:1143495,
        title = {Let's Go to the Whiteboard: How and Why Software Developers Draw Code},
        author = {Mauro Cherubini and Gina Venolia and Rob Deline and Andy Ko},
        journal = {CHI '07: Proceedings of the 2007 25th anniversary conference on Computer-Human Interaction},
        pages = {1--10},
        year = 2007,
        url = {http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=4031755},
        id = {1143495},
	priority = {3},
	description = {Cites from CiteULike},
	abstract = {Software developers are rooted in the written form of their code, yet they often draw diagrams representing their code. Unfortunately, we still know little about how and why they create these diagrams, and so there is little research to inform the design of visual tools to support developers’ work. This paper presents findings from semi-structured interviews that have been validated with a structured survey. Results show that most of the diagrams had a transient nature because of the high cost of changing whiteboard sketches to electronic renderings. Diagrams that documented design decisions were often externalized in these temporary drawings and then subsequently lost. Current visualization tools and the software development practices that we observed do not solve these issues, but these results suggest several directions for future research.},
	biburl = {http://www.bibsonomy.org/bibtex/2168fe790d78cc758925dfd1141f2e49b/fcalefato},
	keywords = {collaboration, reticollab0607}
}