MétaCan
Menu
Back to cohort
Record W2295764489 · doi:10.11575/prism/30639

An Evaluation of Low Fidelity Prototyping Techniques in Agile Release Planning for Collocated Teams

2008· article· en· W2295764489 on OpenAlexaff
Saul Greenberg, Yaser Ghanam, Xin Wang

Bibliographic record

VenueOpen MIND · 2008
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Techniques and Practices
Canadian institutionsUniversity of Calgary
Fundersnot available
KeywordsAgile software developmentWhiteboardComputer scienceScrumProcess (computing)Process managementUser storyRapid prototypingOnboardingFidelityReadabilityTechnicianKanbanSoftware engineeringEngineeringEngineering managementMultimediaSoftwareSoftware developmentArtificial intelligence

Abstract

fetched live from OpenAlex

In an Agile environment where the requirement elicitation is a continuous process, low-fidelity prototypes are increasingly important. Collocated Agile teams often use the traditional whiteboard to draw these prototypes and discuss it with the customer in the release planning meeting preceding each iteration. For the same purpose, SMART Boards are also being utilized by some Agile teams. A study to compares prototyping using both tools was conducted in an academic setting showing an equal preference for both tools with the whiteboard being perceived better in terms of readability and the SMART Board being deemed a better means of sharing. With tools having different pros and cons, it was suggested that both tools can be utilized in release planning meetings to do different kinds of tasks or to accommodate different room settings.

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.024
metaresearch head score (Gemma)0.100
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.024
Threshold uncertainty score0.127

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0240.100
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0020.001
Science and technology studies0.0010.001
Scholarly communication0.0020.002
Open science0.0020.002
Research integrity0.0010.001
Insufficient payload (model declined to judge)0.0030.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.092
GPT teacher head0.390
Teacher spread0.298 · 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 designObservational
Domainnot available
GenreEmpirical

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
Published2008
Admission routes1
Has abstractyes

Explore more

Same venueOpen MINDSame topicSoftware Engineering Techniques and PracticesFrench-language works237,207