Call for Papers

Join us for the sixth Continuous Lifecycle London, online from May 10 to 12, 2021 (additional days for training sessions will probably take place in the week of May 18).

Our aim is to equip developers, software architects, system administrators, team leaders and CIOs with the knowledge necessary to develop and deploy high-quality software, and give them an event to exchange experiences with their peers.

Situation Publishing, the people behind The Register, the UK’s leading science and technology news site, and heise Developer, the German online channel for software developers, invite practitioners to submit proposals for talks (45 minutes) and training sessions (~seven hours) addressing processes and tools in areas such as Continuous Delivery and Integration, DevOps, Containerization and Microservices, cloud-native development, Reliability Engineering and more.

The call for papers is now closed. Thanks to everyone who submitted.

Speakers and instructors will get free access to the streams of all conference sessions.

Entrants should be aware of our Code of Conduct and keep it in mind while drafting their abstracts. (If you are not a speaker but would like to suggest a topic or someone who could give a presentation instead, let us know.)

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


  • Automating and accelerating development processes with Continuous Delivery/Deployment/Integration
  • Migration of delivery pipelines
  • Development of cloud native services
  • Integrating or switching to serverless functions
  • Monitoring, logging and tracing in distributed systems
  • Site/Service reliability engineering (including Chaos Engineering)
  • Containerization and security of container environments
  • Quality assurance and test automation throughout the development process
  • Cooperation between development and operations (DevOps) plus other stakeholders (DevSec, DevSecOps, BizDevOps)
  • Handling organisational consequences of DevOps and Continuous Delivery in (agile) processes
  • Collaborating and communicating in distributed teams


  • Cloud and on-premises solutions for deployment and build
  • Containerization with Docker/moby, rkt, Podman and other alternatives
  • Orchestration, management and monitoring of containers including, but not restricted to, Kubernetes, Helm, Prometheus, Istio, OpenTelemetry, fluentd, OpenShift, SUSE CaaS, and Rancher
  • Tools for Continuous Integration and Deployment
  • Process automation with Jenkins, Ansible, Chef, Argo, Puppet, GitLab etc
  • Serverless offerings (OpenWhisk, OpenFaaS, Fission, AWS Lambda, Azure Functions, Virtual Kubelet, kubeless, etc.)
  • Edge computing platforms
  • Revision control systems
  • Tools for reviews and test automation
  • Build tools
  • Service discovery
  • Service Meshes
  • Infrastructure as Code
  • Configuration and access management

The emphasis will be on 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
  • Process automation
  • Interaction and integration of various tools
  • Integrating tools for containers and microservices into the deployment pipeline
  • Debugging complex, composite systems
  • Continuous Delivery with Serverless Computing and microservices
  • Improving system security and observability
  • Developing Cloud Native Services and multi-cloud applications
  • 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
  • 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 November 30, 2020. 

If you’re short on speaking experience and need help with your proposal, we’re happy to assist you via email. Just contact us and we’ll figure it out together.

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