We apply an open, transparent, iterative session review, improvement and selection process. It consists of the following phases:

Sending in a proposal: send in your proposal(s) providing proposal details as mentioned. 

Open, interactive reviews and feedback, helping presenters develop their proposals, based on peer to peer feedback. Proposals are put on the wiki. You can give feedback on other people's proposals and improve your proposal based on the feedback you receive. The objective of this phase is to come to a set of quality session proposals in a transparent, community driven way.
  • use the PerfectionGame as the basic protocol for review & feedback
  • if you like, ask for a coach to help you develop your session
  • if you really want to develop your session in an agile way, do one or more trial runs during this phase, to develop your session idea based on concrete results
  • when you propose a session, we ask you to give feedback on other people's proposals 
Session selection where we ask for input from the community to vote for the sessions they would like to have in the conference. The program committee takes this information into the program meeting to compose a balanced program that fulfills the conference objectives. The objective of this phase is to get a program that fits in two days, which is supported by the community and which has added value for the community.

Session preparation. We can provide coaching for presenters, to help create an even better session. For new sessions, we strongly recommend doing one or more try-outs. The Dutch and Belgian agile communities will provide opportunities to do try outs. (and don't forget to prepare your OHMP - official half minute presentation).
To propose a session, please send in a description to sessions using the following template:
  • title
  • presenters - including bio & previous experience presenting sessions; we prefer sessions run by pair presenters.
  • abstract - inviting, clear, brief statement of what the session brings and why someone should participate
  • format & length - read more about different session formats
  • intended audience - including prerequisites, level, role - developer/manager/...
  • objectives & acceptance criteria - what is the focus of this session? What is the one idea you want to get across? When will you consider the session be a success?
  • benefits - what are the benefits for the participants? and the benefits for the presenters?
  • content, process & timetable
  • session history: has the session been run before? do you have try-out(s) scheduled?
  • materials, room requirements, session limitations, ...
Eventually, we need a sufficiently elaborated proposal to be able to do reviews and selection. Feel free however to start with a wild/rough idea and let it grow based on the feedback you receive (please state your intent in your proposal).

The session length is a multiple of 30 minutes :
  • 30 min. for presentations & experience reports
  • 60 & 90 min. for tutorials, workshops, hands-on sessions, etc.
We want to build an attractive program with high quality sessions. Keep in mind the ReviewCriteria and remember that the best way to get to a quality session is in our experience by actually trying it out and improving using real feedback. We expect you to do one or more trial runs of your session before the conference. We will help you by providing guidance and creating community based opportunities for try-outs, both during the session feedback process and after session acceptance.

Timeline
  • May - 15 July: propose sessions; reviewing & improving session proposals iteratively
  • 15 July - 8 August: final reviews
  • 8 August - 1 September: community voting
  • 1st week of September: Program Committee meeting
  • mid September: program is published
  • September-November: session preparation, including coaching & try-outs
  • 25-26 November: conference