Loading ...
Sorry, an error occurred while loading the content.

XP Agile Universe 2003 - Call for submissions

Expand Messages
  • Frank Maurer
    We apologize if you receive this call for papers multiple times Frank Maurer (on behalf of the XP AU 2003 program committee)
    Message 1 of 1 , Feb 5, 2003
      We apologize if you receive this call for papers multiple times Frank Maurer
      (on behalf of the XP AU 2003 program committee)

      XP Agile Universe 2003: CALL FOR PAPERS
      August 10-13, 2003
      New Orleans

      Following the success of last year's conference, XP Agile Universe 2003 will
      bring together experts, practitioners and novices in the field of Extreme
      Programming and Agile Methods.
      High-quality, peer reviewed papers will provide an overview on the latest
      trends and will allow the industry practitioners to find out when and how
      these approaches can improve their software development processes. A large
      number of tutorials will prove helpful to those who desire greater insight
      into agile software processes. Technical workshops will be forums for
      discussing latest insights.

      February 28, 2003
      Deadlines for technical paper submissions, workshop proposals,
      educator symposium paper submissions, tutorials proposals

      Chairs: Frank Maurer (maurer@...) Don Wells
      We seek technical papers documenting research, experiences, and new
      approaches/practices in Extreme Programming and Agile Methods.
      Topics include, but are not limited to:
      . New Agile Methods and TechniquesAgile Modeling and Design
      . Scalability of Agile MethodsAgile Software Engineering
      . Dispersed Agile TeamsBeyond Extreme Programming
      . Ad Hoc and Hybrid MethodsPair Programming
      . Open Source and AgilityRefactoring
      . Tool Support for Agile MethodsAgile Testing and Quality Assurance
      . Adoption, Education, and TrainingIssues of Frequent Deployment
      . Agile ManagementTime-Constrained Requirements Engineering
      . Customers and ContractsKnowledge Management in Agile Processes
      . Lightweight PlanningLong Term Implications of Agile Methods
      . Adding Agility to an OrganizationEmpirical Results and Validation
      . Teamwork and CollaborationExperience Reports

      Papers must be original and not under consideration for publication
      elsewhere. Papers must be of high quality and well written. Papers may
      represent actual experience or fully researched ideas. Experience papers
      should be up to 6 pages. Papers reporting significant research results
      should be no more than 10 pages. Papers presenting opposing views are also
      strongly encouraged. All papers must be written in English. Papers will be
      peer-reviewed for originality, content, relevance, significance, and
      correctness when compared to current trends in the field.

      Each paper must include an title, author(s) address and email address,
      abstract, keyword list, body, summary or conclusion, acknowledgements, short
      author biography, and well-populated bibliography.
      Please send submission electronically to xpu@....
      PDF, Microsoft Word, or RTF formats are acceptable.

      Conference Proceedings will be published by Springer as part of the Lecture
      Notes in Computer Science. Final manuscripts need to be formatted according
      to the Springer Lecture Notes in Computer Science guidelines

      Chair: Don Reifer dreifer@...
      The Educators' Symposium brings educators and industry training experts
      together to share their experiences teaching agile methods. Educators can
      discuss their needs and how they plan to incorporate XP and agile methods
      into curriculum, courses and organizational training plans. Educators can
      also swap ideas and exchange course materials.
      Educators and trainers are encouraged to submit papers and panel proposals.
      Selection will be based on clarity, originality, educational merit, and most
      importantly, on relevance to XP and agile method educators and trainers.
      Accepted papers will be published in conference proceedings and must adhere
      to the conference formatting guidelines. Submissions may be made in any of
      the following three categories:

      1. Experience Paper
      Submissions in this category will describe how the challenge of introducing
      XP and agile methods and incorporating the technology into existing
      curricula or organizations was met with an emphasis on innovation. How the
      experience positively influenced education and training practice must be
      clearly explained. The final manuscript should be a full paper of up to 6

      2. Research Paper
      Submissions in this category will report on research that contributes to
      knowledge in the field of XP and agile methods training and education.
      Topics can range from new delivery methods to results of experiments. The
      final manuscript should be a full paper of up to 10 pages.

      3. Panel
      Submissions in this last category will focus on issues associated with XP
      and agile method education and training. Panels should be issues and
      answers oriented. Panelists should be selected to debate the issues from
      opposing sides. Panel proposals must identify the theme or topic to be
      discussed, the panelists and why they were chosen, the issues to be raised
      and why these issues (and of course the answers) are of interest and
      relevant to XP and agile methods educators and trainers. Please send all
      submissions electronically to Don Reifer (dreifer@...). PDF,
      Microsoft Word, or RTF formats are acceptable.

      Chair: Grigori Melnik(grigori.melnik@...)
      Workshops provide a forum for small groups to engage in intellectual
      discussions that aim to significantly advance the state of agile software
      development methods and/or provide insight into future research directions.
      Workshops also provide the opportunity for representatives of a technical
      community to coordinate efforts and to establish collective plans of action.

      We welcome proposals on any topic of interest to the Agile Community. We
      also encourage proposals involving neighbouring research areas.
      To foster dialog, the workshops will be kept small, with up to 20 invited
      participants (exceptions can be made). To ensure a sufficiently small group
      for effective interaction and discussion, workshop organizers can manage
      attendance based on a review of short position papers from potential
      attendees. The position papers need to be published on the Web prior to the
      workshop by the workshop organizers. Workshops are typically a half-day (3
      hours) in length. In exceptional cases, full day (6-hour) workshops will
      also be accepted. We particularly encourage proposals for novel,
      highly-interactive workshops. Each workshop must have at least two
      organizers, preferably from different organizations.
      If you want to organize a workshop, submit a proposal via e-mail to the
      Workshop Chair Grigori Melnik (grigori.melnik@...). We will accept PDF,
      HTML and MS Word files as proposals.

      Workshop proposals should include:
      . a workshop title
      . a half-page description (to be used in the Conference Program)
      . the name of the workshop primary contact
      . an outline of the theme and goals of the workshop (Please identify
      specific issues on which workshop will focus, as opposed to proposing broad
      discussion of a particular field of research. Discuss why the topic is of
      interest at this time)
      . a description of the proposed workshop format and proposed length
      (half-day or full-day)
      . a short description of the participant solicitation and selection
      process (Usually, the selection process is based on peer review)
      . a brief description of each organizer's background with contact

      The program committee will review each proposal. Acceptance will be based on
      the evaluation of the workshop potential to advance the state of agile
      methods, the expected level of interest in the topic, and the organizers'
      ability to lead a successful workshop.

      Workshop organizers will be responsible for:
      . submitting a workshop proposal
      . developing a Call for Position Papers for the workshop
      . setting up and maintaining a workshop Web site
      . inviting workshop participants
      . announcing the workshop in relevant newsgroups
      . distributing the Call for Position Papers to electronic mailing
      lists, and ensuring the workshop publicity;
      . soliciting papers from their colleagues;
      . managing position papers review process and notifying authors;
      . running the workshop.

      Chair: Brian Button (bbutton@...)
      The XP/Agile Universe Conference is now accepting proposals for the 2003
      tutorial sessions. As last year, the conference will cover all Agile
      Methods, including Extreme Programming. Tutorials for any Agile Method are
      acceptable and encouraged. Tutorials are an independent instruction on a
      self-contained topic of relevance to conference attendees. Therefore no
      commercial or sales-oriented presentations will be accepted. We encourage
      tutorial proposals that provide clear utility to practitioners, especially
      innovative tutorials, which depart from lecture style delivery, and
      tutorials on highly advanced topics in lightweight processes. Tutorials are
      presented in half-day (3-hour) or full-day sessions (6-hour). Accepted
      tutorials will run only if there is enough attendance.

      Submit proposals via e-mail to the tutorial chair Brian Button
      (bbutton@...). We will accept PDF, HTML and MS Word files as

      A tutorial proposal must be two pages and should include:
      . Tutorial title and summary (used in advance program)
      . Duration (full- or half-day), aims and audience
      . Content outline
      . Presenter resume with contact information
      . Examples of supporting material

      Each tutorial proposal will be evaluated on its anticipated benefit for
      prospective participants and its fit within the tutorial program as a whole.
      Factors to be considered also include: relevance, timeliness, importance,
      and audience appeal; suitability for presentation in a half- or full-day
      tutorial format; effectiveness of teaching methods; and qualifications of
      the instructor(s). Previous tutorial topics have included: Agile Data and
      Organizational Change
      Agile Business Practices
      Effective Java Testing
      Relationship of QA and XP
      Pair Programming
      Coaching XP

      [Non-text portions of this message have been removed]
    Your message has been successfully submitted and would be delivered to recipients shortly.