Tutorials are an independent instruction on a self-contained topic of relevance to conference attendees. Tutorials should have “agile” development relevancy such as

• Methods: Adaptive, Crystal, DSDM, FDD, Lean, Scrum, Extreme Programming (XP)
• Techniques for software design, requirements, programming, prototyping, testing, UI design, team handling, project steering, or others.
• Use of tools important to agile software development: configuration management, distance communication, coordination, or others.

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 agile processes.

Three and a half hours are allotted for each Tutorial.

Tutorial proposals should be no more than 2 pages and should include:

• Tutorial title and summary (the wording to be used in advance program)
• 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. The tutorial program aims to fulfill a portfolio designed to attend to the various job roles present at the conference: executive, manager, UI designer, programmer, tester, facilitator, and attend to the various single and common techniques they use.

Additional considerations include: relevance, timeliness, importance, and audience appeal; suitability for presentation in a tutorial format; effectiveness of teaching methods; and qualifications of the instructor(s).

No commercial or sales-oriented presentation will be accepted.

Tutorial Compensation

One free registration plus $1,600 honorarium per tutorial ($2,600 honorarium for presenters traveling from outside North America). If two or more people are presenting the tutorial, they may divide the registration plus honorarium however they choose.

While registering, participants are asked to indicate their preferred sessions and it is possible that accepted tutorials may be withdrawn from the program if gathered data indicates attendance will be low.

Submit

Submissions are closed. Submitters can access the submission system here.

Key Dates:

Proposals due: January 5, 2004
Notification of acceptance: February 15, 2004
Final tutorials due: April 30, 2004

If you have questions regarding the Tutorial sessions, please contact us at tutorials@agiledevelopmentconference.com.

Selection Committee

• Rachel Davies, Independent consultant (Chair)
• Jennita Andrea, ClearStream Consulting
• Tracy Bialik, Pentad
• Mike Cohn, Fast401k
• Andrew Craddock, Radtac
• Lisa Crispin, Agile Tester
• Peter McBreen, Software Craftsmanship
• Jim Newkirk, Microsoft
• William Wake, Independent consultant