kirancodes.me
To Proof Maintenance & Beyond!
FSE 2015

Summarizing and measuring development activity

Christoph Treude, Fernando Marques Figueira Filho, Uirá Kulesza

Full textDOI 10.1145/2786805.2786827dblp

Abstract

Software developers pursue a wide range of activities as part of their work, and making sense of what they did in a given time frame is far from trivial as evidenced by the large number of awareness and coordination tools that have been developed in recent years. To inform tool design for making sense of the information available about a developer's activity, we conducted an empirical study with 156 GitHub users to investigate what information they would expect in a summary of development activity, how they would measure development activity, and what factors influence how such activity can be condensed into textual summaries or numbers. We found that unexpected events are as important as expected events in summaries of what a developer did, and that many developers do not believe in measuring development activity. Among the factors that influence summarization and measurement of development activity, we identified development experience and programming languages.

BibTeX
@inproceedings{Treude-al:FSE15,
  author    = {Christoph Treude and
               Fernando Marques Figueira Filho and
               Uir{\'{a}} Kulesza},
  title     = {Summarizing and measuring development activity},
  booktitle = {{ESEC/SIGSOFT} {FSE}},
  pages     = {625--636},
  publisher = {{ACM}},
  year      = {2015},
}

Related papers