XP2017 will have a continuous open space during the main conference, but no explicitly planned session for Lightning talks. By the nature of the Open Space everyone may offer to host a Lightning Talk session during the marketplace.
If you do not have an existing Agile Alliance account: Here is how you create one ...
(1) Goto the Agile Alliance submission system
(2) When the login screen displays, click on "sign up" or alternatively use this direct link.
(3) At the membership signup page, click "Submit" (cost-free subscriber membership is selected by default).
(4) On the "Create profile" page, provide the required information and click "submit form".
(5) A subscriber account will be created for you and you will be taken to the submission system. The page that displays will look similar to this:
Start with a good title that is meaningful to the topic. This is your first opportunity to make a good impression.
The abstract is the marketing for your session. Design it to persuade people to attend. Many good abstracts begin with a startling statement or compelling question. Defining a problem statement and making a call to action can be an e ective technique. Great abstracts draw on readers’ emotions, such as appealing to a pain they are feeling or an idea about which they are excited.
To do this, you need to understand your primary audience. Communicating directly to them is key to a good submission. Although there is a dropdown to select audience level, include details here, like, "this session is targeted at senior managers inside the company who want to introduce XP and Scrum but are not sure how to get started."
It’s a good idea to reinforce your learning objectives in your abstract, because the learning objectives you list on the submission form aren’t read by attendees, only reviewers. Also, consider providing a description of your presentation format, exercises or activities you intend to include. This helps attendees understand what to expect at your session and decide whether it will be valuable to them.
Above all, ensure your abstract is well written and your ideas are clearly articulated. It should be free of grammatical and spelling mistakes.
This part of the submission form will only be seen by the reviewers and program team. It is your opportunity to speak directly to them. You don’t need to be formal in your language or writing style here.
This section should describe the mechanics of what you want to do in the session. It should include timings, outlines, exercises, etc - anything that helps the review team understand your thinking behind the session and how you will manage it.
For example, have you given this presentation before or is it new? If available, provide a link to a video or other information. If it's new, call that out.
A succinct list of clear learning outcomes is critical to a good submission. List what people will take away. For example, "Learn that e ective and e cient meetings are focused strategically, tactically or daily." Badly written learning outcomes say things like "Get an understanding of agile" or "Learn new coding techniques."
Tell your story with specifics. Help reviewers get a sense of your speaking style. Are you a seasoned speaker or are you new to presenting? Providing a link to a video clip of you presenting, even on another topic could be very helpful to the reviewers.
Draft submissions will not be reviewed by the review team, but the public can view and comment. Submitters can share the link and ask for feedback from friends and peers. Submitters use this state while working on their submissions.
Ask for Help means the submitter is requesting feedback from the track review team to improve the submission before evaluation. Reviewers try to give responses to help requests as early as possible.
Ready for Evaluation means a session is ready to be evaluated by the track review team. Submitters must move sessions into Ready for Evaluation by the date the submission system closes for edits. If this isn’t done, the session will not be considered for the program.
Everyone having a registration for the Agile Alliance submission system can post here. It is supposed to be the section for an on-going conversation on proposals, esp. in draft state.
This section is only accessible by reviewers. Here's where reviewers usually give their feedback on proposals that need help or have potential for further improvement.
Here is where reviewers document their votes and comments on proposals that are ready for evaluation.
The submission deadlines are based on Central European Timezone (CET).
Submissions are possible until midnight. But take care to push the submit button before midnight.
XP strives to be a community of equals. We want people to come to the conference because they want to. There will be no speaker badges, speaker rooms or speaker dinners. The conference is all-volunteer, not for profit.
The mission of the conference is to bring agile minds together. In practice those with the most restricted budgets are researchers and academics, so their fees are heavily subsidised by the rest of the conference participants. The ratio of presenters to attendees is very low, typically 1:2 or less. This makes it hard to balance the books if all presenters get free registrations
If your proposed session is accepted the relevant amount will be refunded, as laid out below:
Academics have a general 40% discount independent from their number of contributions (even zero).
For Industry & Practice speakers we have the following rules: