From a Scrum Reference Ontology to the Integration of Applications for Data-Driven Software Development

•Organizations often use different applications to support the Scrum process•Useful data for decision-making is spread in different applications•Data integration to support the Scrum process needs to address semantic issues•A Scrum Reference Ontology (SRO) is proposed•SRO is used in application inte...

Full description

Saved in:
Bibliographic Details
Published in:Information and software technology Vol. 136; p. 106570
Main Authors: Santos Júnior, Paulo Sérgio, Barcellos, Monalessa Perini, Falbo, Ricardo de Almeida, Almeida, João Paulo A.
Format: Journal Article
Language:English
Published: Elsevier B.V 01-08-2021
Subjects:
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary:•Organizations often use different applications to support the Scrum process•Useful data for decision-making is spread in different applications•Data integration to support the Scrum process needs to address semantic issues•A Scrum Reference Ontology (SRO) is proposed•SRO is used in application integration to provide data to decision-making Organizations often use different applications to support the Scrum process, including project management tools, source repository and quality assessment tools. These applications store useful data for decision-making. However, data items often remain spread in different applications, each of which adopt different data and behavioral models, posing a barrier for integrated data usage. As a consequence, data-driven decisions in agile development are uncommon, missing valuable opportunities for informed decision making. Considering the need to address semantic issues to properly integrate applications that support the agile development process, we aim to provide a common and comprehensive conceptualization about Scrum in the software development context and apply this conceptualization to support application integration. We have developed the Scrum Reference Ontology (SRO) and used it to semantically integrate Azure DevOps and Clockify. SRO served as a reference model to build software artifacts in a semantic integration architecture that enables applications to automatically share, exchange and combine data and services. The integrated solution was used in the software development unit of a Brazilian government agency. Results demonstrate that the integrated solution contributed to improving estimates, provided data that helped allocate teams, manage team productivity and project performance, and enabled to identify and fix problems in the Scrum process execution. SRO can serve as an interlingua for application integration in the context of Scrum-process support. By capturing the conceptualization underlying Scrum, the reference ontology can address semantic conflicts and thereby support the development of integrated data-driven solutions for decision making.
ISSN:0950-5849
1873-6025
DOI:10.1016/j.infsof.2021.106570