AGILE2018

Submission Process

SUBMISSION PROCESS

Welcome, and thank you for your interest in submitting to the Agile2018 Conference.

To help make your experience as easy as possible, we’d like to explain how our process works, our timelines, constraints in the process, and the best ways to receive valuable feedback on your sessions.

If you have questions, please email the Conference Chair at chair2018@agilealliance.org.

UNDERSTANDING THE SUBMISSION PROCESS

We value honesty, openness, and respect, and the submission process is built around those very same values. Our goal is to provide the best program possible for Agile2018 by evaluating all sessions fairly, offering help and coaching when requested, and treating you as a valued contributor to the success of Agile2018.

Timeline

The submission system is open for a total of 12 weeks. You can add and edit sessions during the first 8 weeks. You can only edit existing submissions during the last 4 weeks.

Once the 13 weeks have elapsed, the Program Committee will review all sessions ready for evaluation and make program recommendations. The Program Chairs take the recommendations, combine them, and create the best overall program. We notify all submitters of outcomes of the submission process, and we proceed happily to the conference in August.

Here are those dates in a more concise format:

12/02/2017

Submission System Open

02/03/2018

Deadline to enter new session proposals.

Presenters can still edit existing session proposals.

02/28/2018

Deadline to edit session proposals. All session proposals must be in Submit for Evaluation by this date.

3/23/2018

Program finalized and scheduled

03/26/2018

Notifications sent

4/11/2018

Deadline to Accept

04/18/2018

Official Program Announced

08/06/2018

Conference Opens

Choosing the Best Track

Choosing the appropriate track is one of the most important decisions a submitter makes, as it directs your submission to the people most likely to understand and value your ideas. Agile2018 has 14 separate tracks to which you can submit, each having their own specific topic. To help you in choosing, each track has a charter that describes the purpose of that track and some questions the track is seeking to answer.

The Help and Evaluation Goals

The goals for the submission process are as follows:

  • Create the strongest program possible.
  • Provide rapid and actionable advice for submitters who request help.

The Submission Process

Submitters craft their sessions in the submission system, and may ask for help from the track review teams.

Sessions in the system are saved in one of three states:

  • Draft submissions will not be reviewed, 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 Feedback means the submitter is requesting feedback from the track review team to improve the submission before evaluation. Responses to help requests should arrive within 48 hours.
  • Submit for Evaluation means a session is ready to be evaluated by the track review team. If edits are needed, sessions should be moved back to a Draft state.

 

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.

Individuals may submit up to 4 sessions, regardless of whether they are the primary or secondary submitter. An individual will have no more than 2 submissions accepted into the program, however 10 minute lightning talk sessions do not count against this limit.

CREATING A GREAT SUBMISSION

Here is an example of an excellent submission provided for the Agile2018 conference. Thank you to the submitter for letting us repost their submission content.

Title:
Start with a good title that is meaningful to the topic. This is your first opportunity to make a good impression.

Abstract:
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 effective 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.

Information for the Program Team:
This part of the submission form is used to provide details that will help the reviewers and program team better understand your session. The details included in this area will not be published to the online schedule so you don’t need to be formal in your language or writing style.

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.

Learning Outcomes.
A succinct list of clear learning outcomes is critical to a good submission. List what people will take away. For example, "Learn that effective and efficient meetings are focused strategically, tactically or daily." Badly written learning outcomes say things like "Get an understanding of agile" or "Learn new coding techniques."

Presentation History
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.

SPEAKER HONORARIA

The Agile2018 Honorarium Package is as follows for ONE Speaker per session ONLY:

  • (1) Complimentary Conference Registration
  • (4) hotel nights at host hotel, Marriott Marquee San Diego

If a speaker is speaking more than once, monetary compensation of $500 will be offered for each additional session.

Please note the following:

  • For sessions in which there are (2) speakers, you will be given the opportunity at acceptance time to select which speaker will redeem the honorarium package.
  • Regretfully, we cannot offer splitting of honorarium packages.
  • Complimentary hotel nights and/or conference registrations can not be accumulated with multiple submission acceptances.
  • Complimentary hotel nights must be used during the conference. (August 5 - 10, 2018)

SUBMIT YOUR PROPOSAL

You can find the submission system at https://submissions.agilealliance.org/agile2018/.

Log in using your Agile Alliance account if you are a member or subscriber. If you are not, you can become a subscriber the first time you visit the submission system. Don't worry, it's easy and free.