A Time to Learn


eXtreme Programming
and
Agile Software Development

 

 

Call for Sessions
XP Day is a two day international conference about Agile Software Development for software developers, project leaders, IT managers, testers, architects, and coaches.

We encourage session proposals from experienced practitioners of agile software development methods, such as Adaptive, Crystal, DSDM, Feature-Driven Development, Lean, Scrum and Extreme Programming (XP).

XP Day provides a good opportunity for exchanging ideas and sharing experiences, and is suited both for experienced practitioners and those wanting an introduction Agile Software Development. The focus of this conference is on practical knowledge, real-world experience and active participation of all attendees.


Why Organise a Session?

Organising a session is the best way to learn from such a conference. It provides an opportunity to share your experiences, to get feedback on your ideas, and to try new session formats.
Session organisers will get free admission to the conference on the day that they present.

Session Format

We believe that the best way to learn is through hands-on experience and therefore value interaction and audience participation over PowerPoint presentations and papers. Successful sessions from previous years have been tutorials, workshops, simulations and games.
Sessions will be organised into three tracks over two days. Each session may be 45 minutes, 1½ hours or 3 hours in duration.
The broad areas we would like to cover are:
  • Introductory Material
  • Inter-personal Techniques
  • Advanced Practices

  • Possible session topics include, but are not limited to:

  • Agile processes from the perspective of the customer, manager or developer
  • Contracts for agile software projects
  • Continuous process improvement
  • Transitioning to an agile process
  • The economics of agile software development
  • Techniques to improve pairing
  • Scaling agile development processes
  • Agile free software and open source projects
  • Developing mission critical software
  • Agile project management
  • Tools and techniques

  • Review Criteria

  • Sessions must be relevant to agile software development and agile business processes.
  • We want to create a program that provides material ranging from introductory to advanced, and we will balance the topics accordingly.
  • We are open to submissions from experienced session organisers as well as novices.
  • We do not accept sponsored sessions or purely commercial sessions.
  • We prefer sessions organized by co-presenters.
  • You may submit more than one session.
  • Submission details

    For a session proposal, the following information is required (you may provide more information if you feel that's appropriate):
  • Title
  • Organiser(s), including a short biography (100 words max.) and contact information (e-mail address and phone number) for the principal organiser.
  • Session duration (45, 90, or 180 minutes)
  • Session type: simulation; game; workshop; interactive presentation;case study; interactive demonstration; goldfish bowl; panel discussion; clinic; other.
  • Session description: objectives, contents, process, timetable, benefits of attending, the way in which the audience is involved
  • Intended audience (e.g. customers, managers, developers, testers) and their experience level (e.g. apprentice, journeyman, master)
  • What does the organiser expect to learn from running his session?


  • Session proposals should be submitted before the submission deadline below to [email protected] in plain text, PDF, Postscript, or Microsoft Office or OpenOffice format.

    Submission Review and Acceptance Process

    The session proposal submission and acceptance process consists of 5 phases: submission, acceptance, re-working of conditionally accepted proposals, shepherding, and materials submission.
    Proposals that meet the minimal criteria mentioned above will be considered for acceptance. Each submission will be reviewed by 3 reviewers. All sessions will receive written feedback. Sessions will be accepted, rejected, or conditionally accepted.
    Sessions are conditionally accepted if the program committee thinks the session is of interest for the conference, but needs some (re)work. The criteria for acceptance will be explicitly stated and through assistance of a program committee member, the organisers will get a chance to work on the proposal. After conditional acceptance, the program committee will decide on final acceptance or rejection.
    When a session proposal has been accepted, it will enter the shepherding process. One of the reviewers of the submission will become your shepherd and will help you to further refine and improve the session. After that, organisers can submit materials if the session requires it.

    Important dates

  • Submission deadline: 9th August 2004
  • Notification of acceptance: 10th September 2004
  • XP Day Conference: 25th & 26th November 2004
  • Program Committee

  • Nat Pryce, ThoughtWorks Programme Chair
  • Tim Bacon, ThoughtWorks
  • Peter Brown, TristramSoftware
  • Rachel Davies, Agile Alliance
  • Steve Freeman, ThoughtWorks
  • Ivan Moore, ThoughtWorks
  • Duncan Pierce, Amarinda
  • Andy Pols, Pols Consulting