A dependency taxonomy for agile software development projects

Strode, Diane E.

doi:10.1007/s10796-015-9574-1

Cited by 58 publications

(110 citation statements)

References 48 publications

Supporting

Mentioning

103

Contrasting

Unclassified

Order By: Relevance

“…• Taxonomies. It has also been possible to find some taxonomies, the first one, is a dependency taxonomy which allows us to identify the dependencies for agile software development projects, this work studies one of the most important features and pillars in agile projects, the collaboration, and how to get it through an effective coordination by means of the analysis of dependence between projects [31]. Similarly, it was possible to find a study which analyses the behavior of project managers when they adopt agile approaches in software development projects [32].…”

Section: An Analysis Of the Current Situationmentioning

confidence: 99%

“…Similarly, for the EAs, ontologies and taxonomies have been defined for specific domains in XP [20], FDD [27], Scrum [28,29], and the generic ontology for agile methods presented in [30]. At the analysis level of the structure of the concepts related to the agility, some defined taxonomies have been found, which have allowed to identify the dependencies between agile software development projects and to facilitate the coordination and collaboration among projects [31] and also, solutions that have allowed analyzing the agile behavior of project managers [32]. However, it has been possible to observe that the proposed solutions are of a preliminary nature and are limited in the following aspects: i) a generic scope that supports multiple AAs and TAs is not included, ii) absence of concepts and fundamental agile relationships such as: values , principles, agile practices and activities of the process, iii) the relationship of the proposed concepts, the concept of quality, the agile principles and values are not observed, iv) there are still inconsistencies and conflicts related to terminology, and vii) the potential and benefits of the harmonization between the concepts and relationships present in AAs and TAs is not maximized.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

OntoAgile: an ontology for agile software development processes

Ordoñez¹,

Pardo²,

Pino-Correa³

2019

DYNA

View full text Add to dashboard Cite

Currently, there is a broad portfolio of agile approaches to software development, however, in many cases their implementation is done informally and without a proper institutionalization of the agile values and principles. Although there are some proposals related to the adoption and assessment of agile approaches, efforts have been made without having a common terminology which has led to confusion and terminological conflict affecting the implementation of these approaches in organizations. This article proposes the ontology called OntoAgile, which aims to suggest a common and consistent terminology that allows sharing the knowledge generated around the implementation of the agile approaches in the software processes in a generic and formal way. Similarly, OntoAgile facilitates the assessment of the agility of the software processes from the identification of the relationships between the elements of the software processes and the agile principles and values. OntoAgile was assessed satisfactorily by three cases of application.

show abstract

Section: An Analysis Of the Current Situationmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

OntoAgile: an ontology for agile software development processes

Ordoñez¹,

Pardo²,

Pino-Correa³

2019

DYNA

View full text Add to dashboard Cite

show abstract

“…Since agile development projects are distinctly different from traditional development projects in terms of requirement gathering and team structure and management mechanisms, understanding dependencies is critical. In her paper, A dependency taxonomy for agile software development projects, Strode (2016) proposes a categorization of dependencies and selection of agile software development practices through the analysis of three case studies. Eight types of dependencies (three categories) are identified, including requirements, expertise, historical, task allocation, activity, business process, entity, and technical dependencies.…”

Section: Papers In the Special Issuementioning

confidence: 99%

Collaboration technology in teams and organizations: Introduction to the special issue

et al. 2016

View full text Add to dashboard Cite

“…These two models are presented in Figure 1. Agile software development [3] can be seen as an extension of the spiral model.…”

Section: Introductionmentioning

confidence: 99%

Towards knowledge interoperability between the UML, DMN, BPMN and CMMN models

et al. 2019

View full text Add to dashboard Cite

Development of modern software systems consists of many different phases, the sequence of whom is referred to as the software life cycle. During these phases, business analysts gather requirements from clients and try to design a system in order to fulfil these requirements. Software design of complex systems exploits various notations for representing knowledge about system structure and behaviour, decisions, processes and different cases. These elements are modelled using such graphical notations, maintained by Object Management Group (OMG), such as UML (Unified Modelling Language), DMN (Decision Model and Notation), BPMN (Business Process Model and Notation), and CMMN (Case Management Model and Notation). In this paper, we present our work-in-progress analysis of the current state of the art in knowledge interchange for these notations. Moreover, we identify the integration or interchange approaches in terms of application areas. Our goal is to provide an input for an integrated method of designing systems with the use of these notations.

show abstract

A dependency taxonomy for agile software development projects

Cited by 58 publications

References 48 publications

OntoAgile: an ontology for agile software development processes

OntoAgile: an ontology for agile software development processes

Collaboration technology in teams and organizations: Introduction to the special issue

Towards knowledge interoperability between the UML, DMN, BPMN and CMMN models

Contact Info

Product

Resources

About