Message from the Program Chairs
Bibliographic record
Abstract
Agile 2007 is the premier international conference on Agile Software Development. Looking back on the conference series shows that the agile community has come a long way. The first Agile Conference in North America was called XP Universe 2001 and was held in Raleigh. At that time, about 230 people attended the conference. For the following years, this conference was renamed XP Agile Universe. Growing slowly, it moved to different locations in North America: Chicago (2002), New Orleans (2003, about 250 participants), and Calgary (2004, about 320 participants). In 2003, a second North American conference started. The Agile Development Conference was held in Salt Lake City in 2003 and 2004. In 2005, both conference series were merged into the Agile 20xx conference series. Agile 2005 was held in Denver, Agile 2006 in Minneapolis, and Agile 2007 is now in Washington, DC. At the same time, Agile methods were taking off in the software industry and participation was exploding. For Agile 2007, we are now expecting 1100+ participants— making it the largest international conference on agile approaches to software development. This year, the program of the conference covers a wide spectrum of topics and provides high-quality sessions for all levels of expertise on agile topics as well as many different job roles. Nearly 20 concurrent sessions ensure that at any time participants have many interesting presentations, hands-on sessions, tutorials, and workshops from which to choose. Agile 2007 will be an exciting conference about techniques and technologies, attitudes and policies, research and experience, and the management and development sides of agile software development. The program was selected in a peer-review process from hundreds of submissions from world leading experts on agile methodologies. It contains introductory tutorials, advanced interactive sessions, cutting-edge research, and reports about the latest experiences. It will allow anyone to learn something new about the application of agile methods to real world software development problems.
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.003 | 0.012 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.004 | 0.001 |
| Scholarly communication | 0.006 | 0.005 |
| Open science | 0.002 | 0.005 |
| Research integrity | 0.009 | 0.019 |
| Insufficient payload (model declined to judge) | 0.142 | 0.074 |
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".