Speaking at DevWeek 2015 – Friday, 27 March 2015 Monday, 23 March

Speaking at DevWeek 2015
Monday, 23 March – Friday, 27 March 2015
Presentation submission deadline: Friday, 24 October 2014
Scope
In its 18th year, DevWeek 2015 is a well-established conference for professional software developers,
DBAs and IT architects.
Venue
The conference will be held at Central Hall Westminster, London, UK
Submissions
We suggest that you submit a range of different breakout sessions and/or workshops to increase your
chance of being selected for DevWeek 2015. Furthermore, we want to provide delegates with the
most up-to-date information, so we are really looking for new and fresh content for the conference
agenda.
Themes
DevWeek 2015 would like to hear your ideas for original sessions and workshops on topics
including, but not limited to, the following:









Mobile / tablet computing
o Native Mobile development (C, C++, Java, OpenGL ES)
o Cross-platform Mobile development
o Mobile services provided by the cloud
Cloud
o Azure, AWS, Google Cloud Platform, etc
Production scalability / performance techniques
o Velocity, Memcached, MemcacheDB, Elasticsearch, Cassandra
Cloud messaging / inter-process communication/synchronization
o Message queues – RabbitMq, ZeroMQ, MSMQ
o Node.JS
Web technologies
o REST / WS-REST - C++ REST SDK “Casablanca"
o JavaScript and jQuery
o HTML5
o CSS3
Software reliability / testing
o TDD
o Unit testing
o Best practices on the use of tools for static analysis, code coverage and memory-leak
detection etc.
o Refactoring
Security
o Secure coding best practices
o OAuth 2.0
o Digital identity management
o Adapting defences to threats
Data
o Big data
o Business intelligence / visualisation
o SQL
o NoSQL
High-performance computing
o Mainstream in-memory computing
o Massively parallel computing (CUDA / OpenCL)
o Parallel programming language extension
o Intel Xeon Phi





Design/UX
o Responsive design
o Bootstrap 3
o Continuity across devices
Developer tools & techniques
Frameworks (open/closed source)
Patterns
Best practices or innovative case studies of products such SharePoint, Exchange, SQL
Server, Windows Server 2012 R2, Virtualisation
Submissions
There are four different sessions/workshops that you can make proposals for:
 40-minute keynote session
 90-minute technical breakout sessions
 All-day pre-conference workshops (9.30am to 5.30pm)
 All-day post-conference workshops (9.30am to 5.30pm)
Review process
The DevWeek Submissions Committee will review, rate and select submissions based on:
 Concept of presentation: the general idea and its relevance and timeliness to your audience
 Depth: the technical details offered to and insights to be learned by your audience
 Organisation of submission: clearly conveying what your presentation is about
 Your credentials and expertise in the subject matter
Vendor submissions
If your submission is focused on a service, technology or a new product your company is offering,
please contact us for information on sponsored sessions, exhibitor and sponsorship opportunities.
What we need from you
Please provide the following information no later than Friday, 24 October








A brief, up-to-date biography, including details of previous speaking experience
A title for each proposed session or workshop
An abstract for each session or workshop – for use on website and in printed programme
guide
An extended abstract, describing in more detail what your session is about and listing the
examples you will use. This extended abstract is to help the DevWeek Submissions
Committee choose the correct sessions. It is not meant for attendees to read, and will not be
used in the printed programme guide or website.
An indication of the assumed experience level and/or specific prerequisites for attendees
If you’re proposing more than one session, please list them in the optimum running order
A hi-res “mugshot”/ head & shoulders photo of you (JPEG or TIFF)
Your full contact information
What makes a successful submission?
The session title is critical in attracting the audience to read the session description. A clearly
articulated session title that has clear learning objectives will greatly increase the chance that
conference attendees will take an interest in your session.
The title should:
 Be USEFUL to the reader
 Provide the reader with a sense of URGENCY
 Convey the idea that there is a UNIQUE benefit to attending
 Be SPECIFIC
Session abstract
The first sentence should describe what the attendee can expect to learn from your presentation. Get
right to the point; avoid background your audience already knows. Subsequent sentences should offer
more details about what will be covered and why the reader should attend. In general, go for clarity
over cleverness.
Example openers for session descriptions:
 Learn how to…
 Explore new techniques in…
 Hear experts explain how…
 See the newest features in…
 Dive deep into the…
 Join industry experts for a discussion on…
 Get the latest information on…
PLEASE SEND YOUR SUBMISSIONS TO: [email protected]
If you have any questions, or need any further information about speaking at DevWeek 2015, please
send an email to the same address.