This day has finally arrived and we’re all excited to let you know that the submission system for the Agile 2016 conference has opened! You should all rush out immediately and begin to submit the sessions you’ve been thinking about, considering, and generally obsessing over since the last conference.
For those of you who are first-time submitters, we have prepared some advice for you about the process and the expectations of reviewers that is available on the Agile2016 conference site. Much of this information will also be valuable to those who have submitted before, so please take a look.
And the information that everyone is most concerned with – the timeline:
December 17, 2015
- Submission system opens. Up to 4 submissions per person can be added.
February 7, 2016
- Last day new submissions can be added. After this, only edits are allowed.
February 28, 2016
- Last day sessions can be edited. After this, the submission system is closed.
March 27, 2016
- Notifications are sent to all submitters. Sessions are either accepted, put onto a wait list to replace sessions unable to be presented, or not in the program.
Brian Button is the conference chair for Agile2016. He is also the Software Engineering Director and Product Manager for Cloud Storage at CenturyLink Cloud's St. Louis Development Center. He leads the development of several customer-facing products and shares his Agile experiences with the teams around him.
Brian began his career 28 years ago as a hardcore C/C++ dev on SunOS, building and delivering solutions in many languages and operating systems. He has worked in embedded systems, navigation software, mission control applications for NASA, and other interesting areas. Eventually moving into Agile consulting and coaching, Brian traveled the Western world helping organizations learn better ways of developing software. He was instrumental in introducing Agile and Extreme Programming to St. Louis and has been an active leader in Agile and Extreme Programming conferences and communities in the U.S. since the early 2000s.
About the Author
This is an Agile Alliance community blog post. Opinions represented are personal and belong solely to the author. They do not represent opinion or policy of Agile Alliance.