| Experiences applying automated architecture analysis tool suites. | 5 | 0.46 | 2018 |
| Deploying Software Team Analytics in a Multinational Organization. | 0 | 0.34 | 2018 |
| A Case Study of the Effects of Architecture Debt on Software Evolution Effort | 0 | 0.34 | 2018 |
| A proposed sizing model for managing 3rd party code technical debt. | 0 | 0.34 | 2018 |
| Reducing Interruptions at Work: A Large-Scale Field Study of FlowLight. | 16 | 0.71 | 2017 |
| Technical Debt: A Research Roadmap Report on the Eighth Workshop on Managing Technical Debt (MTD 2016). | 4 | 0.51 | 2017 |
| A case study of program comprehension effort and technical debt estimations | 1 | 0.36 | 2016 |
| Improving Code Maintainability: A Case Study on the Impact of Refactoring | 1 | 0.38 | 2016 |
| A field study on fostering structural navigation with prodet | 6 | 0.43 | 2015 |
| Developers' code context models for change tasks | 27 | 0.72 | 2014 |
| A Framework for Estimating Interest on Technical Debt by Monitoring Developer Activity Related to Code Comprehension | 12 | 0.51 | 2014 |
| Experiences gamifying developer adoption of practices and tools | 15 | 0.85 | 2014 |
| Towards recognizing and rewarding efficient developer work patterns | 7 | 0.59 | 2013 |
| Defining the decision factors for managing defects: A technical debt perspective | 19 | 0.98 | 2012 |
| Code Hot Spot: A tool for extraction and analysis of code change history | 1 | 0.36 | 2011 |
| Approximating Deployment Metrics to Predict Field Defects and Plan Corrective Maintenance Activities | 4 | 0.47 | 2009 |
| Predicting failures with developer networks and social network analysis | 112 | 3.96 | 2008 |
| How should software reliability engineering (SRE) be taught? | 12 | 0.47 | 2006 |
| On the Value of Static Analysis for Fault Detection in Software | 102 | 4.09 | 2006 |
| Designing an SRE program for commercial software organizations | 0 | 0.34 | 2005 |
| Preliminary results on using static analysis tools for software inspection | 18 | 1.30 | 2004 |
