Conference
Presented by:

Peer to Peer

Steve Freeman
Peer to Peer Chair
peertopeer@agiledevelopmentconference.com

Peer to Peer sessions, a chance to learn from each other, will include typical and atypical formats.

Peer to Peer sessions should include learning, participation, concrete outcomes, and (not least) fun. Session leaders should provide an understanding of the topic and a structure to help the participants learn from each other. If your intention is mainly to present your hard-won knowledge, then a tutorial or experience report might be more appropriate. Sessions will be open to all conference participants. The session leader may impose an attendance limit in which case participants will be able to sign up during the conference. Position papers should not be required for participation.

Below are some examples of the session styles we're interested in. The conference that inspired this track, OT2003, may be of some assistance.

Workshop (90 or 180 minutes)
A Workshop is a structured session in which the participants explore a topic, guided by the organizers. The organizers are not expected to have all the answers, but they should have interesting questions and a clear process for getting to some results. Those results might, for example, be a set of patterns, proposals for research projects, or taxonomy of team structures.

Goldfish Bowl (90 minutes)
Goldfish Bowl is a technique for managing a discussion amongst a large group of people. It is suitable for topics where there will be a lively discussion with many different views and many people who want to participate. A small discussion group, typically 4 or 5 people, gets things underway, with the remaining participants seated around the group forming an audience. Spare places in the discussion group are available, and members of the audience may take up these places any time they feel they have a contribution to make. Members of the discussion group leave their places when they have had their say, making room for others.

Simulation (90 or 180 minutes)
Simulations and games help us to understand how to work within our organization, experiment with new approaches to working, and even visualize network protocols. A Simulation proposal must provide a clear summary of the purpose and rules of the game, and guidance for reflecting on what it teaches us about the real world.

Think Tank (90 minutes)
In a Think Tank, a small group of people meet to solve a particular problem or to find an agreed position on some issue. Think Tank sessions are intensive, focused and produce concrete output.

Proposal

Proposals should be for one specific session type. They should include:

  • Topic- The session must have a clear topic to be considered and specific is better than general. The topic must be in line with the scope of the conference.
  • Audience- Describe who would be interested in your session and what experience they should bring. Sessions where nobody knows anything about the topic are usually not rewarding.
  • Goal - The session must have clear objectives. What are participants going to get from it?
  • Process - The proposal must explain in detail how the session is to be run, with some indication of timing. If you wish to place a limit on the number of participants please state the limit and why you think it is necessary.
  • Deliverables - A good session should not only enlighten the participants, it should produce something that can be shared with the rest of the conference and wider community. Please state what outputs your session will have and how you will collect them.

Proposals must include the submitter's name, affiliation, and contact information. Please clearly state whether you want a 90 or 180-minute slot. If you have lead sessions of this kind before please give details.

A proposal may be made by one or more people, but at most two people will be eligible for the presenter's discount.

Submit

Submissions are closed.

Key Dates:

Proposals due: January 19, 2004
Notification of acceptance: February 15, 2004
Final manuscripts due: April 30, 2004

If you have questions regarding the Peer to Peer sessions, please contact us at peertopeer@agiledevelopmentconference.com.

Reviewer Committee

  • Laura Hill
  • John Daniels
  • Ellen Gottesdiener
  • Keith Braithwaite
  • Helen Sharp
  • Bob Evans
  • Rick Mugridge