XP Universe
July 23-25, 2001
Raleigh, NC

March 15, 2001 for all submissions.
May 1, 2001 for acceptance notification.
June 1, 2001 for final manuscript submission.

Technical Papers
Educators' Symposium Papers
Activity Sessions
How to Submit

Goal and Scope of Papers including Educators' Symposium Papers

Technical papers should offer significant contributions to the study and use of XP and other lightweight software development processes. Submissions should focus on experience-based accounts and other insights gathered from practical applications (the good, the bad, and the ugly are all worthwhile topics). Papers containing both research and experiential components are very much welcome.

Educator symposium papers should discuss experiences and/or results of introducing XP and lightweight methodologies into undergraduate and graduate courses.

Papers must be original and not under consideration for publication elsewhere. Authors must clearly explain the contribution of the work in terms of its theoretical and/or practical value and relationship to previous work.  Accepted papers will be presented in oral sessions.  

Submissions should carefully follow the format guidelines specified in the document XPUniverseFormatting.pdf.   Accepted papers will be published in the Conference Proceedings. The final manuscript should be a minimum five-page paper in PDF format, and adhere to the above mentioned format guidelines. There is a ten-page limit.

The Program Committee will evaluate all papers standards of originality, relevance, significance, generality, correctness, appropriate comparisons to related research, organization, and clarity.

Goal and Scope of Tutorials

The XP Universe tutorial program provides conference participants the opportunity to gain new insights, knowledge, and skills in topics related to XP and other lightweight software development processes. Participants may include venture capitalists, entrepreneurs, software developers, managers, teachers, researchers, and students.

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. Tutorial presenters will receive half of the revenue generated by the session.    

A tutorial proposal 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).

Goal and Scope of Workshops

Workshops provide a forum for a group of participants to exchange opinions and to advance the status of the art on topics in research and/or applications of XP and lightweight software development processes. Workshops also provide the opportunity for representatives of a technical community to coordinate efforts and to establish collective plans of action. To ensure a sufficiently small group for effective interaction, workshop organizers manage attendance based on a review of short position papers from potential attendees.

Workshops are typically half-day (3-hour) in length.  We particularly encourage proposals for novel, highly-interactive workshops.

This call for participation is for workshop organizers only. A later call will occur for workshop attendees. Each workshop must have at least two organizers, preferably from different organizations. The organizers will typically manage a workshop Web site and the whole workshop participation process.

A workshop proposal should include:

  • Workshop title and summary (used in advance program)
  • Outline of the theme and goals of the workshop
  • A description of the desired number of participants, the participant solicitation and selection process
  • A brief description of each organizer's background with contact information

Acceptance will be based on an evaluation of the workshop's potential for generating useful results, the timeliness and expected interest in the topic, and the organizers' ability to lead a successful workshop.

Goal and Scope of Panel and Activity Sessions

Panel sessions and activity sessions serve to stimulate discussion about ideas and issues of importance to the XP and lightweight software development processes community. They may emphasize technical issues, or they may provide an opportunity to air views and address controversies through informed debate.

Suitable topics for discussion include pressing issues in practice, emerging industrial trends and enabling technologies, and professional, organizational, and social issues.

A panel must present different viewpoints on an important subject.

An activity session may have various formats. Debates, "goldfish bowls", game show formats, courtroom simulations are among the kinds of sessions that raise important issues and encourage discussion in creative ways.

Panels and activity sessions should be informative and even fun. The best panelists include people with a variety of backgrounds and viewpoints. They do not have to be experts. Valuable insights can come from "gurus" as well as from those in the trenches of daily system development.

A panel or activity session proposal should include:

  • Panel or activity session title and summary (used in advance program)
  • Outline of the issues to be discussed, and their relevance to conference attendees
  • A description of the session format, stating how the session will be conducted and why the proposed format is suitable for the proposed topic
  • A list of the panelists and/or other players
  • A brief description of the organizer's background with contact information

Acceptance will be based on an evaluation of the session's potential for engaging the panelists and audience in lively and substantive discussions, the timeliness and expected interest in the topic, and the organizers' ability to lead a successful session. 

How to Submit
Unless extenuating circumstances occur, submissions should be submitted electronically as e-mail attachment in either Adobe Portable Document Format or HTML. 

Submit papers by e-mail to Don Wells.

Copyright @ 2001 Object Mentor, Incorporated

The XP logo is Copyright @ 2001 Ronald E. Jeffries

This site is powered by