Creating Decision Guidance for Applying Agile System Engineering
Bibliographic record
Abstract
Abstract Systems teams, development projects, and organizations, who are involved in product development, are often faced with the question as to whether they should adapt agile systems practices into their programs and processes. In trying to answer this question these groups are almost immediately confronted with the problem of determining what is motivating the decision, where should agile principles be applied, and how much agility is necessary. There are several interrelated systems involved in this inquiry and the development of a proper understanding around these considerations is not a trivial exercise. A method of inquiry and decision making that is in itself agile and that can produce actionable results needs to guide the development of this understanding. The purpose of this paper is to present work accomplished to date on the definition, prototyping, and evaluation of a decision guidance system to help a development team or organization achieve a necessary understanding that can lead to useful actionable decisions regarding agile adoption.
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 imitationNot 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.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.025 | 0.067 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.004 | 0.001 |
| Science and technology studies | 0.002 | 0.002 |
| Scholarly communication | 0.007 | 0.006 |
| Open science | 0.002 | 0.005 |
| Research integrity | 0.003 | 0.003 |
| Insufficient payload (model declined to judge) | 0.006 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
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".