The hot summer in Europe provided a lot of time for relaxation and contemplation:) I’ve spent some of the warm days reading some articles for the upcoming SEAA session on software analytics, which is a follow up of the special issue of IST: https://doi.org/10.1016/j.infsof.2018.03.001
Software analytics, simply put, is using data and its visualisation to make decisions about software development. The typical data sources, both in literature and observed in many companies, are:
- Source code measurements from Git
- Defect data from JIRA
- Requirements data
- Customer data, a.k.a. field data
- Performance/profiling data from running the system
- Process data from time reporting systems, Windows journals, etc.
These data sources allow us to find bottlenecks in the performance of our software and the performance of our progress.
Software analytics has been in the heart of such paradigms as the MVP from The Lean Start-Up, where they provide the ability to steer which features are developed and which are abandoned.
Our experiences from Software Analytics are described in the book Software Development Measurement Programs, chapter 5: https://www.springer.com/us/book/9783319918358