Actionable software metrics : an industrial perspective

Abstract

<div lang="en" class="abs"><p class="abs_header">Abstract</p><p><em>Background:</em> Practitioners would like to take action based on software metrics, as long as they find them reliable. Existing literature explores how metrics can be made reliable, but remains unclear if there are other conditions necessary for a metric to be actionable.</p><p><em>Context & Method:</em> In the context of a European H2020 Project, we conducted a multiple case study to study metrics’ use in four companies, and identified instances where these metrics influenced actions. We used an online questionnaire to enquire about the project participants’ views on actionable metrics. Next, we invited one participant from each company to elaborate on the identified metrics’ use for taking actions and the questionnaire responses (N=17).</p><p><em>Result:</em> We learned that a metric that is practical, contextual, and exhibits high data quality characteristics is actionable. Even a non-actionable metric can be useful, but an actionable metric mostly requires interpretation. However, the more these metrics are simple and reflect the software development context accurately, the less interpretation required to infer actionable information from the metric. Company size and project characteristics can also influence the type of metric that can be actionable.</p><p><em>Conclusion:</em> This exploration of industry’s views on actionable metrics help characterize actionable metrics in practical terms. This awareness of what characteristics constitute an actionable metric can facilitate their definition and development right from the start of a software metrics program.</p></div>