MétaCan
Menu
Back to cohort
Record W2897972231 · doi:10.1177/8756972818802713

A Research Agenda for Extending Agile Practices In Software Development and Additional Task Domains

2018· article· en· W2897972231 on OpenAlexaff
Fred Niederman, Thomas Lechler, Yvan Petit

Bibliographic record

VenueProject Management Journal · 2018
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Techniques and Practices
Canadian institutionsUniversité du Québec à Montréal
Fundersnot available
KeywordsAgile software developmentAgile Unified ProcessKnowledge managementTask (project management)Lean software developmentDomain (mathematical analysis)Extant taxonAgile usability engineeringComputer scienceWork (physics)Key (lock)Process managementSoftwareEngineering ethicsManagement scienceSoftware developmentEngineeringSoftware development processSystems engineeringSoftware engineering

Abstract

fetched live from OpenAlex

This article is intended to serve as an introduction to this special issue on agile practices. In doing so, we briefly survey a number of key issues that are emerging in the application of agile practices to software development (SWD) and, similarly, examine recent work on extending knowledge about these practices to other task domains. We note that the extant literature on agile practices has been criticized for lacking a theoretical basis and comment on various ways that a theory orientation can enhance the accumulation of knowledge in this area. We also address issues that expand our current understanding of agile practices as they apply to non-SWD tasks. We present a framework for surfacing and discussing some of these emergent issues. We comment on the articles in this special issue and situate them within the research framework. We discuss some of the topics we think are likely to become influential as agile practices move outside the SWD domain and, finally, we present some summarizing observations.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.054
metaresearch head score (Gemma)0.059
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.054
Threshold uncertainty score0.283

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0540.059
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.002
Bibliometrics0.0050.011
Science and technology studies0.0070.025
Scholarly communication0.0240.060
Open science0.0040.014
Research integrity0.0090.015
Insufficient payload (model declined to judge)0.0110.002

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.126
GPT teacher head0.410
Teacher spread0.285 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designTheoretical or conceptual
Domainnot available
GenreMethods

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations65
Published2018
Admission routes1
Has abstractyes

Explore more

Same venueProject Management JournalSame topicSoftware Engineering Techniques and PracticesFrench-language works237,207