Summarizing and measuring development activity
Open accessThe DOI matches its Crossref record; 7 of the 7 references it cites were found in a registry or an index.
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.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Awareness and coordination in shared workspaces
Dourish, P., & Bellotti, V. (1992) · Proceedings of the 1992 ACM conference on Computer-supported cooperative work - CSCW '92 · doi:10.1145/143457.143468 · Cited by 2,550 · cited 1×
“Awareness is related to social transparency [55] and de-fined as “an understanding of the activities of others, which provide context for your own activity” [18].”
BackgroundLayers of Silence, Arenas of Voice: The Ecology of Visible and Invisible Work
Star, S. L., & Strauss, A. (1999) · Computer Supported Cooperative Work (CSCW) · doi:10.1023/a:1008651105359 · Cited by 1,500 · cited 1×
“One of the challenges is the prevalence of invisible work [53] and articulation work [40] in software development that cannot be measured in terms of lines of code, number of commits, or number of issues.”
BackgroundTowards automatically generating summary comments for Java methods
Sridhara, G., Hill, E., Muppaneni, D., Pollock, L., & Vijay-Shanker, K. (2010) · Proceedings of the IEEE/ACM international conference on Automated software engineering · doi:10.1145/1858996.1859006 · Cited by 514 · cited 2×
“Sridhara et al. [51] presented a technique that summarizes a method’s actions, which requires the detection of code fragments implementing high level actions within methods [52].”
BackgroundMethodUsing task context to improve programmer productivity
Kersten, M., & Murphy, G. C. (2006) · Proceedings of the 14th ACM SIGSOFT international symposium on Foundations of software engineering · doi:10.1145/1181775.1181777 · Cited by 452
People, organizations, and process improvement
Perry, D. E., Staudenmayer, N. A., & Votta, L. G. (1994) · IEEE Software · doi:10.1109/52.300082 · Cited by 401
Software developers' perceptions of productivity
Meyer, A. N., Fritz, T., Murphy, G. C., & Zimmermann, T. (2014) · Proceedings of the 22nd ACM SIGSOFT International Symposium on Foundations of Software Engineering · doi:10.1145/2635868.2635892 · Cited by 224 · cited 3×
“Looking at different conceptualizations of developer productivity in the literature, Meyer et al. [39] found a long list of defini-tions: the number of tasks [59], function points [30], lines of code [17, 44], modification requests [42], or logical source statements [34] in a given time frame or…”
BackgroundInfluentialSocial transparency in networked information exchange: a theoretical framework
Stuart, H. C., Dabbish, L., Kiesler, S., Kinnaird, P., & Kang, R. (2012) · Proceedings of the ACM 2012 conference on Computer Supported Cooperative Work · doi:10.1145/2145204.2145275 · Cited by 100 · cited 1×
“Awareness is related to social transparency [55] and de-fined as “an understanding of the activities of others, which provide context for your own activity” [18].”
Background
Cited by
The Work Life of Developers: Activities, Switches and Perceived Productivity
Meyer, A. N., Barton, L. E., Murphy, G. C., Zimmermann, T., & Fritz, T. (2017) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2017.2656886 · Cited by 170
Design Recommendations for Self-Monitoring in the Workplace: Studies in Software Development
Meyer, A. N., Murphy, G. C., Zimmermann, T., & Fritz, T. (2017) · Proceedings of the ACM on Human-Computer Interaction · doi:10.1145/3134714 · Cited by 60
“…been identified towards the adoption of self-tracking technologies at the workplace, including not fully understanding users’ needs [43], not knowing in what measures users are interested in [54, 59, 67], and not providing users with a holistic understanding of their work behavior [2, 7, 27, 33].”
BackgroundNo Single Metric Captures Productivity
Jaspan, C., & Sadowski, C. (2019) · Rethinking Productivity in Software Engineering · doi:10.1007/978-1-4842-4221-6_2 · Cited by 20
Detecting Developers' Task Switches and Types
Meyer, A. N., Satterfield, C., Zuger, M., Kevic, K., Murphy, G. C., Zimmermann, T., & Fritz, T. (2022) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2020.2984086 · Cited by 14
“software development [74], [75] could be presented to the”
Method
Metadata
- Authors
- Treude, C., Figueira Filho, F., & Kulesza, U.
- Venue
- Proceedings of the 2015 10th Joint Meeting on Foundations of Software Engineering
- Publisher
- ACM
- Published
- 2015-08-30
- Pages
- 625-636
- OpenAlex
- W2044422867
- Cited by
- 42
- References
- 7
- FWCI
- 3.51
- Type
- conference paper
- Language
- en
- Open access
- green
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Summarizing and measuring development activity. https://app.cochat.ai/papers/10.1145/2786805.2786827
- The paper
- Treude, C., Figueira Filho, F., & Kulesza, U. (2015). Summarizing and measuring development activity. Proceedings of the 2015 10th Joint Meeting on Foundations of Software Engineering. https://doi.org/10.1145/2786805.2786827
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.