MétaCan
Menu
Back to cohort

Wiki for Agility

2017· book-chapter· en· W4238613926 on OpenAlexaff
Pankaj Kamthan

Bibliographic record

VenueIGI Global eBooks · 2017
Typebook-chapter
Languageen
FieldComputer Science
TopicSoftware Engineering Techniques and Practices
Canadian institutionsConcordia University
Fundersnot available
KeywordsAgile software developmentSoftware deploymentAgile usability engineeringKnowledge managementSoftware developmentWorld Wide WebComputer scienceContext (archaeology)Lean software developmentSoftwareEngineeringSoftware engineeringSoftware development process

Abstract

fetched live from OpenAlex

The movement towards agility is one of the most significant human-centered and socially oriented changes in industrial software engineering. In the practice of agile methodologies, there are different types of content (data, information, or knowledge) that are created, communicated, and consumed. It is imperative for an organization to manage such content, both during development and beyond deployment. This chapter proposes a conceptual model for understanding and exploring the use of Wiki as a vehicle for managing content in agile software development. In doing so, the parity between agile software development and Wiki is shown, human and social aspects of each are emphasized, the Social Web-Context of Wiki is demonstrated, illustrative examples are given, and the implications of committing to a Wiki are considered.

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 distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Other · Consensus signal: none
Teacher disagreement score0.501
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0020.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

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.034
GPT teacher head0.291
Teacher spread0.257 · 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 teacher head, not a consensus.

Study designTheoretical or conceptual
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

Citations0
Published2017
Admission routes1
Has abstractyes

Explore more

Same venueIGI Global eBooksSame topicSoftware Engineering Techniques and PracticesFrench-language works237,207