Find research datasets worth reusing
Search datasets from major research repositories and use ShareScore to quickly assess how well each record supports discovery, access, and reuse.
35
datasets available to search
ShareScore release 0.9.0
Dataset results
35 results for “Agile development”
Integrating Co-design activities in agile development
<p>Within the Cos4Cloud project the agile methodologies recommended the instrument of co-design digests. This instrument was intended to form a bridge between co-design and the actual agile development process. During the project, the final process was elaborated closely with the co-design team, and was documented in the project's wiki page.</p> <p>The process includes the following steps:</p> <ul> <li>Set up a co-design digest page in the wiki</li> <li>co-design session is taking place</li> <li>results are collected in a co-design report (as it used to be)</li> <li>essential feedback/requirement will be added to the digest page</li> <li>Note to the developer team to review and update the digest table</li> <li>Developer team refines and decides on each entry in the digest table and links to user</li> <li>stories in their backlog (does not have to be accessible, though)</li> <li>Developer team updates the digest table during development of related user stories</li> <li>(decisions, implementation status, changes to the story, ...)</li> <li>Occasionally development team is reminded to update the digests</li> </ul> <p>Partners were invited to adopt this intermediary step to densify, and evaluate the outcome of co-design sessions before further integrate them into the actual agile development process.</p> <p>For one co-design session 52°North and Science for Change prepared a session where participants were asked to think in user stories. The outcome was a list of user stories which only had to be reviewed and refined. For such sessions the development teams chose to make evaluation and integration into the backlog an ad-hoc task and skipped the extra creation of a digest to avoid duplicated work. A proximity of co-design output and agile input naturally accelerates the intermediary step of a Co-design digest and its integration work or (in the extreme) even makes it superfluous.</p>
Supplementary Material for Disruptive Solutions on Requirement Engineering for Agile Software Development: A tertiary study
<p>This repository delivers the supplementary material for the paper: <em>Disruptive Solutions on Requirement Engineering for Agile Software Development: A tertiary study.</em></p> <p>In the following, we present the abstract of the study:</p> <p><strong>Context:</strong> Agile Software Development (ASD) is a disruptive process compared to traditional software development. Therefore, traditional Requirements Engineering (RE) forms may not be the best way to do RE for ASD (RE-ASD). <strong>Objective:</strong> Working with ASD using traditional RE ways could limit ASD's potential. Thus, it is necessary to investigate what academia and industry have done in RE to take full advantage of all of the capabilities of ASD beyond traditional RE. <strong>Method: </strong>We conducted a Tertiary Study looking for solutions for RE-ASD using the Systematic Literature Review (SLR) protocol described by Kitchenham and Charters. We then categorized the solutions into families using Targeted Coding and Constant Comparison, tools from Socio-Technical Grounded Theory (STGT). Afterward, we classified the solutions as disruptive using our model based on the Hype Level Curve concept, assessing their hype (popularity) in the software engineering community using Google Trends and Google Colab tools. <strong>Results:</strong> After executing the SLR protocol, we accepted 37 studies and encountered 136 solutions used by academia and industry for RE-ASD. We categorized these solutions into 21 solution families, six of which we classified as disruptive. Design Thinking (DT) and Artificial Intelligence (AI) were the two families of solutions that stood out the most. We also identified the type of solution (e.g., process, method, technique, tool, model, framework) and domain (academia or industry). Furthermore, we cataloged the challenges presented by the solutions. <strong>Conclusion:</strong> We concluded that only a few solutions that have been used for RE-ASD have the power to successfully challenge the mainstream Agile Software Development process by using innovation (26 out of 106). There is a gap between academia and industry regarding these disruptive solutions, and some challenges still need to be addressed in using these solutions.</p> <p>The repository contains the following:</p> <ul> <li>Dataset from the Tertiary Study: <ul> <li>Data of the retrieved studies. It presents the classifications of the documents as 'Accepted,' 'Rejected' (with the indication of the step of the protocol the authors rejected the study), or 'Duplicated.'</li> <li>Data of all solutions retrieved from the accepted studies</li> </ul> </li> <li>Socio-Technical Grounded Theory (STGT) tools <ul> <li>Result of the use of Targeted Coding and Constant Comparison</li> </ul> </li> <li>The Google Colab Notebook <ul> <li>Code in python</li> <li>Results</li> </ul> </li> </ul> <p> </p>
Replication Package for a Systematic Literature Mapping of Agility in Safety-Critical Software Development within the Aerospace Industry
<p>This file collection package facilitates the replication of a Systematic Literature Mapping (SLM) focused on Agility in Safety-Critical Software Development within the Aerospace Industry. Authored by J. Eduardo Ferreira Ribeiro, João Gabriel Silva, and Ademar Aguiar, this dataset is dedicated to improving transparency and reproducibility in this field of study and future research.</p> <p>Specifically, the package includes:</p> <ul> <li><a href="https://github.com/zemacedo99/Replication-Package-Builder/releases/tag/v1.0.2">Replication Package Builder Version 1.0.2</a></li> <li>A list of terms (both inclusion and exclusion) used to construct the research string.</li> <li>A list of venues unrelated to the research topic, to be excluded from the results.</li> <li>The inclusion and exclusion criteria applied during the study.</li> <li>Lists of publication results from indexing services like Scopus, IEEE Xplore, Science Direct, HAL Open Science, Springer Nature, and the ACM Digital Library are all provided in CSV file format.</li> <li>A list of all publications in CSV format, compiled after the automated exclusion phase using the established inclusion and exclusion criteria.</li> <li>Finally, a complete list of all publications, including those from Snowball sampling, in XLSX format was compiled after the manual exclusion phase using the established inclusion and exclusion criteria.</li> </ul> <p>Compiled and published on Saturday, September 14, 2024, this dataset is crucial for researchers seeking to replicate or extend the SLM's findings.</p> <p>Lastly, we thank J. Antonio Dantas Macedo for contributing to developing and providing this <a href="https://github.com/zemacedo99/Replication-Package-Builder">replication package builder</a>.</p>
Dataset for the study "Agile Change Approach for Collaborative Software Development Contexts" - Umbrella Review
<p>Dataset for the study "Agile Change Approach for Collaborative Software Development Contexts"</p> <p>Umbrella review - First review</p> <p>The objective of this umbrella review is to check that there are no reviews in the defined period from 2000 to 2024 that respond to the objective of this research</p> <p> </p>
Dataset for the study "Agile Change Approach for Collaborative Software Development Contexts" - Systematic Literature Review
<p>Dataset for the study "Agile Change Approach for Collaborative Software Development Contexts" </p> <p>Second review</p> <p> </p> <p>This is the dataset for the full systematic literature review</p>
Agile Global Software Development: A Systematic Literature Review
<p>Global Software Development (GSD) continues to grow substantially and it is fast becoming the norm and fundamentally different from local Software Engineering development. Withal, agile software development (ASD) has become an appealing choice for companies attempting to improve their performance although its methods were originally designed for small and individual teams. The current literature does not provide a cohesive picture of how the agile practices are taken into account in the distributed nature of software development: how to do it, who, and what works in practice. This study aims to highlight how ASD practices are applied in the context of GSD in order to develop a set of techniques that can be relevant in both research and practice. To answer the research question, "how are agile practices adopted in agile global software development teams?'" We conducted a systematic literature review of the ASD and GSD literature. A synthesis of solutions found in seventy-six studies provided 48 distinct practices that organizations can implement, including "collaboration among teams", "agile architecture'", "coaching", "system demo" and "test automation". These implementable practices go some way towards providing solutions to manage GSD teams, and thus to embrace agility.</p>
Study Data: Semi-Automated Prioritization of Industrial Security Findings in Agile Software Development
<p>Dataset for the study of the paper "Semi-Automated Prioritization of Industrial Security Findings in Agile Software Development"</p>
Raw data for the article "Combining STPA and BDD for Safety Analysis and Verification in Agile Development: A Controlled Experiment"
<p>These files include the raw data of pre-questionnaire, operation report, post-questionnaire and hypothesis testing in the experiment. </p>
Dataset for AGILE Platform: A Deep Learning-Powered Approach to Accelerate LNP Development for mRNA Delivery
<p>This document contains the lipid datasets used for fine-tuning and candidate selection in the AGILE study.</p>
Evolution of Teamwork Quality Instruments in Agile Software Development: A Systematic Literature Review
<p>Suplemmentary Material of the article: Evolution of Teamwork Quality Instruments in Agile Software Development: A Systematic Literature Review</p>
Supplementary Material for: On the Challenges to Documenting Requirements in Agile Software Development: A Practitioners' Perspective
<p><strong>Abstract: </strong>Agile Software Development (ASD) is an iterative and incremental methodology designed to accelerate project deliveries. In this dynamic environment characterized by constant changes, the task of documenting requirements becomes increasingly challenging, leading to the emergence of the technical debt issue. This research involved a survey of 84 practitioners to identify the techniques and practices employed in documenting software requirements within ASD teams, as well as their perceptions of the documentation process and the challenges, regarding what factors influence it and its consequences. Our key findings indicate that user stories are the most commonly utilized technique by practitioners for documenting requirements. Furthermore, a deficient documentation process results in two primary consequences: rework and a knowledge deficit. To address these challenges, various techniques are implemented across different development phases, including requirement refactoring, documentation refinement meetings, and template reviews. Participants also emphasized the significance of having a requirements expert to enhance the documentation process and expressed uncertainty regarding the adequacy of their existing requirements documentation. This study highlights the growing issue of technical debt within ASD teams' documentation and requirements and raises awareness about the need to develop habits for documenting and maintaining up-to-date software requirements in agile projects.</p>
Transformed raw data and R scripts for the paper Problem reports and team maturity in agile automotive software development published at CHASE2022
<p>Transformed raw data and R scripts for the paper Problem reports and team maturity in agile automotive software development published at CHASE2022</p> <p>15th International Conference on Cooperative and Human Aspects of Software Engineering, May 21–22, 2022, Pittsburgh, PA, USA}´</p>
Raw data for the article "Speed up BDD for Safety Verification in Agile Development: A Partially Replicated Controlled Experiment"
<p>This is the raw data for the paper "Speed up BDD for safety verification in Agile development: A partially replicated controlled experiment". </p>
Online Appendix of the Paper "The Power of Words in Agile vs. Waterfall Development: Written Communication in Hybrid Software Teams"
<h2>GENERAL INFORMATION</h2> <div>In our publication “<em><strong><a href="https://doi.org/10.1016/j.jss.2024.112243">The Power of Words in Agile vs. Waterfall Development: Written Communication in Hybrid Software Teams</a>,”</strong></em> in the Journal of Systems and Software, we present an exploratory case study conducted in a large software organization, AFAS Software. Our study investigates the influence of the development paradigm and the formality of communication channels on written communication within hybrid development teams. Our main research question is: <em>“<strong>How do the employed development paradigm and the formality of the communication channel impact the written communication content within hybrid software development teams?”</strong> </em>To address the main research question, we operationalize communication content through a coding scheme comprising codes derived from the Project Management Life Cycle (PMLC), the Software Development Life Cycle (SDLC), and speech acts types, which leads to the following sub-research questions:</div> <ul> <li><em>How do the employed development paradigm and the formality of the communication channel impact </em><em>the content of written communication pertaining to the Project Management Life Cycle phases? </em><em>(RQ1A & RQ1B)</em></li> <li><em>How do the employed development paradigm and the formality of the communication channel impact </em><em>the content of written communication pertaining to the Software Development Life Cycle phases? </em><em>(RQ2A & RQ2B)</em></li> <li><em>How do the employed development paradigm and the formality of the communication channel impact </em><em>the use of speech acts types in written communication? (RQ3A & RQ3B)</em></li> </ul> <div>To answer these research questions, we test the following hypotheses regarding the PMLC, the SDLC, and speech acts types:</div> <div> </div> <div><em><strong>The content of written communication within a development team</strong></em></div> <div> <ul> <li><strong>H1</strong>: is affected by the development paradigm. <ul> <li><strong>H1.1</strong>: in formal communication channels is affected by the development paradigm.</li> <li><strong>H1.2:</strong> in informal communication channels is affected by the development paradigm.</li> </ul> </li> </ul> </div> <div><em><strong>The content of written communication within</strong></em></div> <div> <ul> <li><strong>H2:</strong> a development team is affected by the formality of the communication channel. <ul> <li><strong>H2.1:</strong> a non-agile development team is affected by the formality of the communication channel.</li> <li><strong>H2.2:</strong> an agile development team is affected by the formality of the communication channel.</li> </ul> </li> </ul> </div> <div>This online appendix contains supplementary material to uphold transparency and facilitate the reproduction of the statistical analysis. For more information, refer to the publication:</div> <ul> <li>Section 2.5 for the projects sampling</li> <li>Section 2.6 for data extraction and preparation</li> <li>Section 2.7 for the coding scheme and data analysis</li> </ul> <p><strong>Software Dependencies: </strong></p> <ul> <li>PDF Viewer (e.g. Acrobat Reader)</li> <li>IBM SPSS</li> <li>Microsoft Excel</li> <li>Python</li> </ul> <h2>FILES OVERVIEW</h2> <h3>JSS Online Appendix</h3> <div>The root folder includes the <strong>“Project Teams Composition.pdf</strong><em><strong>”</strong></em> file, which contains the anonymized compositions of 20 project teams: 11 agile (PrAG) projects and 9 waterfall (PrWF) projects. This file lists the project team members involved in communication within the Microsoft Teams and Insite channels. </div> <h3>Subfolder “SPSS Files”</h3> <div>This subfolder includes the SPSS files, which contain the normality test and Mann-Whitney U Tests. </div> <div> <ul> <li><strong>Normality Test.spv</strong>: This file contains the results of the normality test.</li> </ul> </div> <div>We performed the normality test. In most cases, the significance of Shapiro-Wilk is below 0.05; thus, the data is not normally distributed and fails to meet the assumption for the t-test. We, therefore, opted for the Mann-Whitney U test, the non-parametric alternative of the t-test.</div> <div> </div> <div>The files below contain the results of Mann-Whitney U Tests, which are presented in Appendix A - Tables A.7 (a), A.8 (a), A.9 (a):</div> <ul> <li><strong>H1 - PrAG vs PrWF Product.spv</strong>: This file contains the results for hypothesis 1. </li> <li><strong>H1.1 - PrAG vs PrWF Formal.spv</strong>: This file contains the results for hypothesis 1.1.</li> <li><strong>H1.2 - PrAG vs PrWF Informal.spv</strong>: This file contains the results for hypothesis 1.2.</li> </ul> <div>The files below contain the results of Mann-Whitney U Tests, which are presented in Appendix A - Tables A.7 (b), A.8 (b), A.9 (b):</div> <ul> <li><strong>H2 - PrAG vs PrWF Formality.spv</strong>: This file contains the results for hypothesis 2.</li> <li><strong>H2.1 - PrWF Formal vs Informal.spv</strong>: This file contains the results for hypothesis 2.1.</li> <li><strong>H2.2 - PrAG Formal vs Informal.spv</strong>: This file contains the results for hypothesis 2.2.</li> </ul> <h3>Subfolder “Excel Files”</h3> <div>This subfolder includes the necessary files to perform calculations and the results of these calculations.</div> <ul> <li><strong>JSS Paper.xlsx</strong>: This file contains the absolute numbers, which are used as input for the calculations.</li> <li><strong>JSS-Statistics.py</strong>: This Python script uses the <strong>“</strong><strong>JSS Paper. xlsx<em>”</em></strong><em><strong> </strong></em>file to perform calculations based on the hypotheses for Project Life Cycle Management (PMLC), Software Development Life Cycle (SDLC), and Speech Acts.</li> </ul> <div>The files below contain the results of the calculations:</div> <ul> <li><strong>PMLC (RQ1A & RQ1B)_v1.xlsx:</strong> This file contains the results for the PMLC phases. The results are presented in Appendix A.1.</li> <li><strong>SDLC (RQ2A & RQ2B)_v1.xlsx:</strong> This file contains the results for the SDLC phases. The results are presented in Appendix A.2.</li> <li><strong>Speech Acts (RQ3A & RQ3B)_v1.xlsx:</strong> This file contains the results for the speech act types. The results are presented in Appendix A.3.</li> </ul> <h2>DATA ACCESS AND SHARING</h2> <div><strong>Recommended citation for this dataset:</strong> Ly, D., Overeem, M., Brinkkemper, S., Dalpiaz, F., 2024. Online Appendix of the Paper “The Power of Words in Agile vs. Waterfall Development: Written Communication in Hybrid Software Teams”. [Data set]. In The Journal of Systems and Software. Zenodo. doi: 10.5281/zenodo.13894086.</div> <div> </div> <div><strong>License information:</strong><em><strong> </strong></em>Creative Commons Attribution 4.0 International</div>
Emergent Solutions on Requirement Engineering for Agile Software Development: A tertiary study (Auxiliary Documentation in PDF)
<p><strong>[Context and motivation]</strong> Agile Software Development (ASD) is a new trend in software development and has become popular. Its advocates claim that ASD is well suited to solving traditional software development problems by valuing human factors over technical ones. However, one of the most critical phases in software development, Requirements Engineering (RE), can be overwhelming for ASD values.<br> <strong>[Question/problem]</strong> Trying to work with RE in a traditional way for ASD can limit ASD's potential. Therefore, it is necessary to investigate what academia and industry have done in RE to exploit all of the capabilities of ASD beyond traditional RE. <br> <strong>[Principal ideas/results]</strong> This work presents an overview of the state-of-the-art Requirement Engineering (RE) for Agile Software Development (ASD). We conducted a Tertiary Study in secondary studies published from 1st January 2015 to 30th June 2021, looking for solutions for RE-ASD using the Systematic Literature Review (SLR) protocol described by Kitchenham and Charters (2007). After executing the SLR protocol, we accepted 37 out of 169 studies and encountered 136 solutions used by academia and industry for RE-ASD. We considered only a few solutions that could be classified as emergent for RE-ASD, 24 out of 106. Furthermore, we cataloged the challenges presented by the emergent solutions (e.g., a steep learning curve due to the lack of experience, process, or culture) that should be addressed. Finally, we identified a possible gap between academia and industry regarding these emerging solutions that need further investigation. <br> <strong>[Contribution]</strong> By highlighting emerging Requirements Engineering (RE) solutions for Agile Software Development (ASD), we made our contribution to help researchers who need to propose new solutions to some of the problems that remain unsolved by pointing out the recent trends for RE for ASD.</p> <p>The repository contains the following:</p> <ul> <li>Auxiliary Documentation in PDF;</li> <li>Dataset from the Tertiary Study - compressed file (refsq2023Complement.zip): <ul> <li> <p><strong>REFSQ2023-ALL-ARTICLES.csv:</strong> is a comma-separated file with all 198 (including the duplicates) found in our search in the digital libraries with their respective status (accepted, rejected, or duplicated).</p> </li> <li> <p><strong>REFSQ2023-DISTINCT-SOLUTIONS.csv:</strong> is a comma-separated file with all the distinct solutions we found in our research. They are classified according to our classification method, explained in the article.</p> </li> <li> <p><strong>REFSQ2023-GOOGLE-TRENDS-RESULTS.csv:</strong> is a comma-separated file with all results of our query in the Google Trends tool. It also brings the used search terms and the code and classification of each solution.</p> </li> </ul> </li> </ul>
Agile Development of a Digital Exposure Treatment for Youth With Chronic Musculoskeletal Pain
ClinicalTrials.gov study NCT05079984. IPD Sharing: NO. Countries: 1. Publications: 23.
Replication package for the article "Combining STPA and BDD for Safety Analysis and Verification in Agile Development: A Controlled Experiment"
<p>This replication package includes all the instruments we used in our experiment. </p>
Data Extraction and Quality Assessment about Cybersecurity in the Context of Agile Software Development
Open the record for dataset details and reuse information.
Metrics in Agile Software Development: Repository
Open the record for dataset details and reuse information.
Sustainability in Agile Software Development - Results
Open the record for dataset details and reuse information.
ScienceDex guides
Understand access before you commit
These curated guides explain access requirements, typical timelines, costs, and reuse considerations for widely used research datasets.
Allen Brain Atlas
Allen Brain Atlas is an Allen Institute collection of brain map atlases, datasets, APIs, and analysis tools covering mouse, human, and non-human primate brain resources.
Annotated Behaviour and Observability Dataset (ABODe)
ABODe is a University of Edinburgh DataShare dataset for behavior classification in group-housed mice using home-cage video, identities, bounding boxes, ground-plate positions, and annotator labels.
DANDI Archive for NWB datasets
DANDI is a BRAIN Initiative archive for publishing and sharing neurophysiology data, including electrophysiology, optophysiology, and behavioral data packaged as NWB and related standards.
International Brain Laboratory public data
The International Brain Laboratory public data releases expose standardized mouse decision-making experiments, including Neuropixels recordings, widefield calcium imaging, behavior, and session metadata accessed through the ONE API.
OpenNeuro
OpenNeuro is a free, open platform for sharing neuroimaging datasets, with public search, dataset pages, and download paths for web, S3, DataLad, and the OpenNeuro CLI.