MétaCan
Menu
Back to cohort
Record W2811411709 · doi:10.1145/3195836.3195845

Myagile

2018· article· en· W2811411709 on OpenAlexaff
Robert Biddle, Andreas Meier, Martin Kropp, Craig Anslow

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Techniques and Practices
Canadian institutionsCarleton University
Fundersnot available
KeywordsAgile software developmentTransparency (behavior)Agile usability engineeringLean software developmentSoftwareKnowledge managementAgile Unified ProcessProcess managementSoftware developmentComputer scienceEngineeringSoftware development processSoftware engineeringComputer security

Abstract

fetched live from OpenAlex

Two main concepts in Agile software development are self-organized teams and direct contact with the customer or Product Owner. Additionally, constant feedback on different levels is considered to be of high importance. With constant feedback, transparency goes hand-in-hand. Compared to traditional software development, Agile approaches have much higher transparency, and this might be a problem for some people. What does it feel like to work in such an Agile team or organization for the individual? How do the software developers, testers or other team members experience this environment of high transparency and continuous feedback? In this paper we focus on a subset of the third Swiss Agile Study from 2016, a nationwide survey about software development, to shed some light on the sociological, cultural and cognitive aspects of Agile teams and their individual member. We found that despite the increased transparency, the majority of the participants reported working in an Agile environment, both on the individual and on the team level, as positive and satisfying. The analysis shows these positive influences have some strong correlations with certain Agile practices and with innovation and business aspects.

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.002
metaresearch head score (Gemma)0.007
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Other · Consensus signal: Other
Teacher disagreement score0.536
Threshold uncertainty score0.000

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0020.007
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0010.001
Science and technology studies0.0010.001
Scholarly communication0.0050.004
Open science0.0010.005
Research integrity0.0020.002
Insufficient payload (model declined to judge)0.5360.322

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.011
GPT teacher head0.257
Teacher spread0.246 · 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 designNot applicable
Domainnot available
GenreOther

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

Citations9
Published2018
Admission routes1
Has abstractyes

Explore more

Same topicSoftware Engineering Techniques and PracticesFrench-language works237,207