The Community for Technology Leaders
RSS Icon
Subscribe
Issue No.04 - July-Aug. (2013 vol.30)
pp: 46-52
Olga Baysal , University of Waterloo
Reid Holmes , University of Waterloo
Michael W. Godfrey , University of Waterloo
ABSTRACT
Prominent technology companies including IBM, Microsoft, and Google have embraced an analytics-driven culture to help improve their decision making. Analytics aim to help practitioners answer questions critical to their projects, such as "Are we on track to deliver the next release on schedule?" and "Of the recent features added, which are the most prone to defects?" by providing fact-based views about projects. Analytic results are often quantitative in nature, presenting data as graphical dashboards with reports and charts. Although current dashboards are often geared toward project managers, they aren't well suited to help individual developers. Mozilla developer interviews show that developers face challenges maintaining a global understanding of the tasks they're working on and that they desire improved support for situational awareness, a form of qualitative analytics that's difficult to achieve with current quantitative tools. This article motivates the need for qualitative dashboards designed to improve developers' situational awareness by providing task tracking and prioritizing capabilities, presenting insights on the workloads of others, listing individual actions, and providing custom views to help manage workload while performing day-to-day development tasks.
INDEX TERMS
Software quality, Software development, Computer bugs, Market research, Software metrics, Software measurement, Software reliability, Analytical models, situational awareness, developer dashboards, qualitative analytics, qualitative dashboards
CITATION
Olga Baysal, Reid Holmes, Michael W. Godfrey, "Developer Dashboards: The Need for Qualitative Analytics", IEEE Software, vol.30, no. 4, pp. 46-52, July-Aug. 2013, doi:10.1109/MS.2013.66
REFERENCES
1. S. LaValle et al., “Big Data, Analytics and the Path from Insights to Value,” MIT Sloan Management Rev., vol. 52, no. 2, 2011, pp. 21–31.
2. D. Eaves, “Developing Community Management Metrics and Tools for Mozilla,” blog, 7 Apr. 2011; http://eaves.ca/2011/04/07developing-community-management-metrics-and-tools-for-mozilla.
3. O. Baysal and R. Holmes, “A Qualitative Study of Mozilla's Process Management Practices,” tech. report CS- 2012-10, David R. Cheriton School of Computer Science, Univ. Waterloo, 2012; www.cs.uwaterloo.ca/research/tr/2012CS-2012-10.pdf .
4. M. Best, “Bugzilla Anthropology,” Mar. 2012; https://wiki.mozilla.orgBugzilla_Anthropology .
5. M.R. Endsley, “Toward a Theory of Situation Awareness in Dynamic Systems: Situation Awareness,” Human Factors, vol. 37, no. 1, 1995, pp. 32–64.
27 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool