MétaCan
Menu
Back to cohort
Record W4252723093 · doi:10.1109/ctgdsd.2012.6226947

Teaching a globally distributed project course using Scrum practices

2012· article· en· W4252723093 on OpenAlexaffabout
Daniela Damian, Casper Lassenius, Maria Paasivaara, Arber Borici, Adrian Schröter

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Techniques and Practices
Canadian institutionsUniversity of Victoria
Fundersnot available
KeywordsScrumEngineering managementCurriculumWork (physics)Computer scienceCourse (navigation)Project management 2.0Project managementKnowledge managementProduct (mathematics)Software developmentSoftwareEngineeringSoftware engineeringProcess managementSystems engineeringProject management triangleOPM3PedagogySociology

Abstract

fetched live from OpenAlex

This paper describes the goals, design and initial challenges encountered in teaching a globally distributed software development course in collaboration between the University of Victoria, Canada and Aalto University, Finland. The project-driven collaboration course involved 16 students in Canada and nine students in Finland, divided into three globally distributed Scrum teams working on the same project. The teams worked on extending Agilefant, an open-source backlog management system, in direct interaction with its product owner. The collaborative development is based on the Scrum methodology. We describe how the Scrum methodology was implemented, and adapted to work in a distributed environment, as well as the infrastructure used to support collaboration, e.g. local war-rooms, and multiple communication tools. We conclude the paper with describing initial challenges encountered, including cultural, semester, course and curriculum differences, as well as technical and time-zone issues.

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.003
metaresearch head score (Gemma)0.004
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.009
Threshold uncertainty score0.032

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0030.004
Meta-epidemiology (narrow)0.0010.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0060.001
Scholarly communication0.0040.002
Open science0.0010.005
Research integrity0.0010.002
Insufficient payload (model declined to judge)0.0070.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.063
GPT teacher head0.373
Teacher spread0.310 · 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

Citations31
Published2012
Admission routes2
Has abstractyes

Explore more

Same topicSoftware Engineering Techniques and PracticesFrench-language works237,207