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.
492
datasets available to search
ShareScore release 0.9.0
Dataset results
492 results for “Agile”
PCA Filtering of Apache Point Observatory 3.5m Agile Observations of LCROSS
<p>This archive contains data products from observations of the 2009-10-09 impact of the Lunar CRater Observation and Sensing Satellite (LCROSS) spacecraft on the Moon by the Agile instrument on the Apache Point Observatory 3.5m telescope. We use principal component analysis (PCA) filtering both to improve the coregistration of the raw time series and to effectively remove a static background signal that is spatially and temporally modified by atmospheric and instrumental effects. We iteratively remove principal components from the data through cumulative sequential elimination (CSE) to find a maximum signal-to-noise ratio of the LCROSS ejecta plume signal.</p> <p>Full details are available in the published journal article:</p> <p>Strycker, Paul D., Nancy J. Chanover, Ruth L. Temme, Jonathan M. Schotte, Payton L. Mueller, and Emily L. Karls. 2023. "Time Series Analysis Methods and Detectability Factors for Ground-Based Imaging of the LCROSS Impact Plume" <em>Remote Sensing</em> <strong>15</strong>, no. 1: 37. <a href="https://doi.org/10.3390/rs15010037">https://doi.org/10.3390/rs15010037</a></p> <p>This work was supported by NASA’s Lunar Data Analysis Program through grant number NNX15AP92G.</p>
AGILE 4.0 MBSE Ontology
<p>This resource contains the Model Based System Engineering (MBSE) ontology being developed within the context of the H2020 EU Project AGILE 4.0 (2019-2022), and published as open access.</p> <p>The available files represent the meta-models, rendered by OWL, supporting the development of complex systems.</p> <p>The domains addressed by the meta-models are expanded, revised and maintained during the project.</p> <p> </p> <p>The ontology uploaded onto this page has been developed to address the development of complex aeronautical systems investigated in AGILE 4.0 Project, but it can be used to address any other kind of system.</p> <p> </p> <p>Domains currently included in the ontology:</p> <ul> <li>April 2021: meta-model for the modeling of system requirements. Additional information can be found in the project deliverable D1.3 "Process definition A4F for Application Case definition" (open access).</li> <li>June 2023: meta-model for the modeling of the whole system development process, including modeling of requirements, architectures and system design and optimization. Additional information can be found in the project deliverable D3.3 "AGILE 4.0 operational and trade-off process" (open access).</li> </ul>
agilIS - agile Information Systems
<p>AgilIS combines Information Systems (IS) Planning, Development, Operation, Management, and Governance macro activities in an integrated manner, based on agile principles.</p>
Data from: Greater agility increases probability of survival in the endangered northern quoll
<p>Introduced predators combined with habitat loss and modification are threatening biodiversity worldwide, particularly the 'critical weight range' (CWR) mammals of Australia. In order to mitigate the impacts of invasive predators on native species in different landscapes, we must understand how the prey's morphology and performance determine their survival. Here we evaluate how phenotypic traits related to escape performance predict the probability of survival for an endangered CWR mammal, the northern quoll (<em>Dasyurus hallucatus</em>). We measured mass, body size, body shape, body condition, and age, as well as maximum sprint speed, acceleration, and agility of female quolls over two consecutive years. Those with higher body condition and agility around a 135° corner were more likely to survive their first 21 months of life but were not more likely to survive after this period. No other morphological or performance traits affected survival. Heavier second-year individuals were more agile than first-years but second-years experienced higher mortality rates throughout the year. Females with higher body condition and agility around a 135° corner tended to have shorter limbs and feet but larger heads. Our findings suggest that higher body condition and agility are advantageous for survival in female northern quolls. These results can be used to develop predictive models of predator-prey interactions based on performance capacities and how performance is affected by habitat, aiding conservation efforts to predict and manage the impacts of introduced predators on native species.</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>
Enhancing research informatics core user satisfaction through agile practices
<p><strong>Objective:</strong> The Huntsman Cancer Institute (HCI) Research Informatics Shared Resource (RISR), a software and database development core facility, sought to address a lack of published operational best practices for research informatics cores. It aimed to use those insights to enhance effectiveness after an increase in team size from 20 to 31 full-time equivalents coincided with a reduction in user satisfaction.</p> <p><strong>Materials and Methods:</strong> RISR migrated from a water-scrum-fall model of software development to agile software development practices, which emphasize iteration and collaboration. RISR's agile implementation emphasizes the product owner role, which is responsible for user engagement and may be particularly valuable in software development that requires close engagement with users like in science.</p> <p><strong>Results: </strong>All RISR's software development teams implemented agile practices in early 2020. All project teams are led by a product owner who serves as the voice of the user on the development team. Annual user survey scores for service quality and turnaround time recorded nine months after implementation increased by 17% and 11%, respectively.</p> <p><strong>Discussion:</strong> RISR is illustrative of the increasing size of research informatics cores and the need to identify best practices for maintaining high effectiveness. Agile practices may address concerns about the fit of software engineering practices in science. The study had one time point after implementing agile practices and one site, limiting its generalizability.</p> <p><strong>Conclusion:</strong> Agile software development may substantially increase a research informatics core facility's effectiveness and should be studied further as a potential best practice for how such cores are operated.</p>
Example data and scripts for the paper: Team maturity and reorganization during a very large-scale agile transformation in the automotive industry
<p>Example data and scripts for the paper: Team maturity and reorganization during a very large-scale agile transformation in the automotive industry. </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>
Agile Social Software Engineer: An Empirical Approach to Mitigate and Manage Social Debts in Agile Environments
<p>Replication package description:<br> "DataCollection.xlsx": Survey responses from Agile teams in weeks 1, 2, 3, 4 and 5.<br> <br> "DataAnalysis.xlsx": Analysis of the answers from the survey to answer the research questions proposed in this work.<br> Team-working issues that could lead to community smells can be found in TeamworkingIssues Tab.<br> The root causes of community smells in agile teams over weeks can be found in Rootcauses Tab.<br> Requests for Agile social guardian intervention can be found in Requestagileteams Tab.<br> Recurring needs and concerns in agile teams can be found in Needs_Concerns Tab.</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>
Agile Minds, Innovative Solutions, and Industry–Academia Collaboration: Lean R&D Meets Problem-based Learning in Software Engineering Education
<p>Supplementary materials of the paper "Agile Minds, Innovative Solutions, and Industry–Academia Collaboration: Lean R&D Meets Problem-based Learning in Software Engineering Education"</p>
Fig. 2 in Impacts of resource limitations on the reproduction behaviour in the Agile Frog (Rana dalmatina) on the territory of Natura park "Shumensko plato"
Fig. 2. Male and female Rana dalmatina in an artificial basin in amplexus for 12 days.
Fig. 1 in Impacts of resource limitations on the reproduction behaviour in the Agile Frog (Rana dalmatina) on the territory of Natura park "Shumensko plato"
Fig. 1. Registered egg-clutches out of the water near the ponds.
Artifacts: An Approach for Reviewing Security Related Apects in Agile Requirements Specifications of Web Applications
<p>Abstract—Defects in requirements specifications can have severe consequences during the software development lifecycle. Some of them result in overall project failure due to incorrect or missing quality characteristics. Security is one of those uality characteristics that need to be considered in early phases. There are several concerns that make security difficult to deal with; for instance, (1) when stakeholders discuss general requirements in (review) meetings, they are often not aware that they should also discuss security-related topics, and in the rather rare cases they are aware (2), they typically do not have sufficient security expertise. This picture is even more challenging in agile development contexts, where lightweight documentation are typically involved. To address these issues, we designed an approach that considers user stories and security specifications as input and relates those user stories to security properties via Natural Language Processing (NLP) techniques. Based on the related security properties, our approach then identifies high-level security requirements from the Open Web Application Security Project (OWASP) to be verified afterwards. In a last step, the verification of the generated security requirements is then conducted via a focused reading technique. We finally validate our approach via a controlled experiment comparing the effectiveness and efficiency of novice inspectors (we used two different groups of students) verifying security aspects in agile requirements using our generated reading techniques against using the complete list of OWASP high level security requirements and a the same list of defect types embedded in our technique. The (statistically significant) results indicate that using the reading technique has a positive impact (with large effect size) on the performance of inspectors in terms of effectiveness and efficiency. </p> <p>This repository also contains:</p> <p>Artifacts used and results of the experimental study of the paper entitled "An Approach for Reviewing Security Related Apects in Agile Requirements Specifications of Web Applications".</p>
Continuous Non-Functional Requirements: Practices, Opportunities, and Trade-offs for Small, Agile Organizations
<p>This data represents two artifacts from our research in evaluating how small, agile organizations manage non-functional requirements in conjunction with continuous practices. It includes our base interview questions and the resulting codebook.</p> <p>This page includes supplementary materials associated with our paper entitled "Continuous Non-Functional Requirements: Practices, Opportunities, and Trade-offs for Small, Agile Organizations".</p>
System Stability and Sustainability Data for 295 Agile Systems
<div><strong>Purpose</strong>: This data set is a collection of 295 "Agile Systems" performed by an European mid-tier software development consulting firm between June 2008 and August 2023. The systems were a mixture of Scrum, Kanban, LeSS, SAFe and other Agile-type approaches to work, including Agile In Name Only (AINO). The data set is the output from a script that analysed the raw data extracted from Jira with each Agile System corresponding to a Jira "Project".</div> <div> </div> <div>The script performed the following actions:</div> <div>1. Read the raw data for each system. (this is not included in this dataset)</div> <div>2. Remove Epics and Sub-tasks so all PBIs are approximately the same size.</div> <div>3. Remove any cancelled (and similar) PBIs so only PBIs analysed were done by a team.</div> <div>4A. Identify the Arrival rate (average rate at which PBIs were created over the duration of the system, Lambda) and the Service rate (average rate at which PBIs were moved to Done over the duration of the system, Mu). Also calculate the system size (total arrivals versus total services) at the end of the duration of the system. </div> <div>4B. Calcuate the Stability Metric (Mu / Lambda) and Inventory Days (Total System Size / Mu). </div> <div>4C. Classify the system to a Strategy:</div> <div>If Stability Metric < 1 and Inventory Days < 30, Strategy : Start-Up </div> <div>If Stability Metric >= 1 and Inventory Days < 30, Strategy : Plan-Up</div> <div>If Stability Metric >= 1 and Inventory Days >= 30, Strategy : Catch-Up</div> <div>If Stability Metric < 1 and Inventory Days >= 30, Strategy : Scale-Up</div> <div>4D. Identify when the first arrival, first service, last arrival and last service.</div> <div>4E. Calculate t0 - the time required for 5 PBIs to be completed. </div> <div>4F. Calculate the number of PBIs that occurred outside 6am to 6pm Mon-Fri. These arrivals and services were for our research purposes "Unsustainable".</div> <div>4G. This data is under the Timeset = "All" for each system.</div> <div>5. Repeat step 4 but for just for the time period leading up to t0. This data is under the Timeset = "0" for each system.</div> <div>6. Recursively repeat step 4 by incrementing the period under investigation after t0 by 7 days until the higher of last arrival and last service is reached. Each period is given an incremented timestep, 1,2,3 and so on. This data is under a numbered Timeset each system. </div> <div> </div> <div><strong>To use the data set: </strong></div> <div>We recommend importing this data into a tool that faciliates pivot tables.</div> <div>It is possible to compare across systems at each timepoint or review time histories across systems. </div>
Agile and the Long Crisis of Software (Audio Recording)
<p>From <a href="https://logicmag.io/clouds/agile-and-the-long-crisis-of-software/">the article</a>: "I began to explore the history of Agile. What I discovered was a long-running wrestling match between what managers want software development to be and what it really is, as practiced by the workers who write the code. Time and again, organizations have sought to contain software’s most troublesome tendencies—its habit of sprawling beyond timelines and measurable goals—by introducing new management styles. And for a time, it looked as though companies had found in Agile the solution to keeping developers happily on task while also working at a feverish pace. Recently, though, some signs are emerging that Agile’s power may be fading. A new moment of reckoning is in the making, one that may end up knocking Agile off its perch."</p>
Chytridiomycosis and climate change: exposure to Batrachochytrium dendrobatidis and mild winter conditions do not increase mortality in juvenile agile frogs during hibernation
<p>Datasets and analyses for "Chytridiomycosis and climate change: exposure to <em>Batrachochytrium dendrobatidis</em> and mild winter conditions do not increase mortality in juvenile agile frogs during hibernation" by Kásler A., Holly D., Herczeg D., Ujszegi J. and Hettyey A., published online on 22nd January 2023 in Animal Conservation.</p> <p><a href="https://doi.org/10.1111/acv.12851">https://doi.org/10.1111/acv.12851</a></p>
The Moderating Effect of Employee Agility on the Link between Employee Vitality, Digital Literacy and Transformational Leadership with Job Performance: An Empirical Study of HR Practitioners in the Manufacturing Sector of Northern Malaysia.
<p>This is a dataset for a study that examines the effects of employee vitality, digital literacy, and transformational leadership on job performance. Additionally, it investigates the moderating role of employee agility in these relationships. Data were collected from HR practitioners in manufacturing companies in the northern region of Malaysia for analysis. The results indicate that the job performance of HR practitioners is positively influenced by employee vitality, digital literacy and transformational leadership. </p>
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.