Design and validation of precooked developer dashboards
Abstract
Despite increasing popularity of developer dashboards, the effectiveness of dashboards is still in question. In order to design a dashboard that is effective and useful for developers, it is important to know (a) what information developers need to see in a dashboard, and (b) how developers want to use a dashboard with that necessary information. To answer these questions, we conducted two series of face-to-face individual interviews with developers. In the first step we analyzed answers, build a Goal-Question-Metric model and designed a precooked developer dashboard. Then, during the second separate series of interviews, we validated the GQM and derived feedback on the designed dashboard. Given that the cost of dashboard customization prevents developers from utilizing dashboards, we believe that our findings can provide a solid starting point to build precooked developer dashboards that can be readily utilized by software companies.
BibTeX
@inproceedings{Ivanov-al:FSE18,
author = {Vladimir Ivanov and
Vladislav Pischulin and
Alan Rogers and
Giancarlo Succi and
Jooyong Yi and
Vasilii Zorin},
title = {Design and validation of precooked developer dashboards},
booktitle = {{ESEC/SIGSOFT} {FSE}},
pages = {821--826},
publisher = {{ACM}},
year = {2018},
}