Sciweavers

CSCW
2004
ACM

Learning from project history: a case study for software development

14 years 5 months ago
Learning from project history: a case study for software development
The lack of lightweight communication channels and other technical and sociological difficulties make it hard for new members of a non-collocated software development team to learn effectively from their more experienced colleagues while they are coming upto-speed on a project. To address this situation, we have developed a tool, named Hipikat, that provides developers with efficient and effective access to the group memory for a software development project that is implicitly formed by all of the artifacts produced during the development. This project memory is built automatically with little or no change to existing work practices. We report an exploratory case study evaluating whether software developers who are new to a project can benefit from the artifacts that Hipikat recommends from the project memory. To assess the appropriateness of the recommendations, we investigated when and how developers queried the project memory, how they evaluated the recommended artifacts, and th...
Davor Cubranic, Gail C. Murphy, Janice Singer, Kel
Added 30 Jun 2010
Updated 30 Jun 2010
Type Conference
Year 2004
Where CSCW
Authors Davor Cubranic, Gail C. Murphy, Janice Singer, Kellogg S. Booth
Comments (0)