Call for Papers


Continuous Lifecycle London returns from May 16 to 18, 2018. The event will focus on the lifecycle of software applications, paying special attention to processes and tools in areas such as Continuous Delivery, DevOps, and Containerisation. Continuous Lifecycle London will equip developers, software architects, system administrators, project leaders, and IT strategists with knowledge of the key aspects of agile software development and will examine the most important processes and tools for developing and deploying high-quality software.

The Register, the UK’s leading science and technology news site, and heise Developer, the online channel for software developers, have teamed up to bring you Continuous Lifecycle London and invite interested parties to submit proposals for talks (45 or 75 minutes) and training sessions (seven hours).

The deadline for proposals is October 20, 2017.

Proposals can include, but are not limited to, one or more of the following topics:


  • Automated and accelerated development processes with Continuous Delivery/Deployment
  • Cooperation between development and operations (DevOps) plus other stakeholders (DevSec, BizDevOps)
  • The organisational consequences of DevOps and Continuous Delivery in (agile) processes
  • Monitoring, logging and tracing
  • Securing Docker environments
  • Pitfalls and opportunities when developing with distributed teams
  • Quality assurance throughout the development process
  • Migration of delivery pipelines
  • Development of cloud native services


  • Revision control systems
  • Tools for continuous integration
  • Software for ticketing and bug tracking
  • Tools for reviews and tests
  • Build tools
  • Automation
  • Service Discovery
  • ChatOps
  • Infrastructure as Code
  • Configuration management
  • Operations and monitoring
  • Integrating tools for application lifecycle management
  • Cloud solutions for deployment and build (PaaS etc.)
  • Containerisation with Docker/moby, rkt and other alternatives
  • Orchestration, management and monitoring of containers

The emphasis will be hands-on introductions, conceptual decisions, live demos, or comparisons of different techniques. Presentations simply promoting a product or individual company will not be allowed.


  • Deployment of tools for agile ALM, within specific application fields or scenarios
  • Experiences of transitioning from classic operational patterns and organizations to DevOps, DevSec and BizDevOps
  • Lessons learned from using DevOps in on-going and completed projects
  • Interaction and integration of various tools
  • Real world development of cloud services
  • Integrating Docker into the deployment pipeline
  • Debugging complex, composite systems
  • Continuous Delivery with serverless computing and microservices
  • Developing Cloud Native Services
  • Cultural change when introducing containers and/or DevOps and/or Continuous Delivery

Please send a target-group-specific, precise and concise abstract (400-700 characters) of your proposed presentation. To help us assess your proposals, please list some keywords (e.g. your main topic, the tools you use, etc.), and include one sentence describing what your audience should already know and one sentence stating what they can expect to learn during the talk. The deadline for submissions is October. The complete schedule will be available online in December.

If you’re short on speaking experience and need help with your proposal, we’re happy to assist you via e-mail. Just contact us here and we’ll figure something out.

To secure objectivity, the review process is anonymised, which means that the editorial board doesn’t know a proposer’s name or company while discussing a proposal. Talks with the sole purpose of marketing your product aren’t eligible for the review process and you should contact our sponsorship team.

Speakers and instructors will get free entrance to both conference days and we may provide expenses and accommodation. If you would like to be considered for these reimbursements, please contact us here.

Entrants should be aware of our Code of Conduct and keep it in mind while drafting their proposals.