Berlin

November 4 & 5, 2024

New York

September 4 & 5, 2024

Velocity

Velocity

Supercharging your processes for faster software delivery

  • Culture, Clarity, Velocity

    This session explores how leaders can examine proposed changes and prepare their teams to move from a culture that impedes progress to one that enables strategic change.

The best AI coding assistants 2024

There’s more to life than just Copilot.

Streamline development processes with application templates

Increase efficiency, collaboration, and innovation.

How to speed up code reviews

Code reviews don’t have to be painful. Here’s how to embrace tools and more collaborative processes to raise the bar on your review cycle.

Managing the chaos of context switching

It’s time to examine the good, the bad, and the very ugly elements of context switching. Even better, we’ll take a look at some strategies for managing it.

Should the daily stand-up die?

Will the real agile developers please stand up? Please stand up. Please, stand up.

On our Velocity playlist

Engineering owns velocity

In this talk, I’ll explore what engineering leaders need to do to credibly own velocity and deeply align their work with the company strategy.

Launching a Gen AI powered travel companion: A case for tiger teams

Explore Booking.com’s journey in launching a Gen AI travel companion in 3 months, powered by a tiger team approach for rapid, focused product development and innovation.

Ben Murray

Goldilocks doesn’t need your story points or your t-shirts

Ben Murray believes there is only really one question you need to ask: is this task small enough?

How to drive pace in your team ??‍♀️

How to drive pace in your team ??‍♀️

Alicia Collymore delivers actionable advice that’ll help you to improve your teams’ delivery and pace without a data-first approach.

Planning for success when scaling rapidly

Create goals, prioritize effectively, set expectations, and drive alignment.

festival of engineering leadership

London • June 16 & 17, 2025

More about Velocity

Top Velocity videos

  • The power of visibility to unblock collaboration

    Fostering a culture where knowledge can be shared with everyone.

  • Landing projects successfully

    Getting projects across the finish line is a challenge, particularly for projects where you need other teams to do something – for example, to migrate to a new tool or a new version of an API. This talk will cover how to increase the likelihood that those teams will do what you need them to do, through a focus on clarity, communication, and empathy. It will cover some ideas for nudging behaviour too.

  • Sustaining and growing motivation across projects

    In this panel, we’ll explore how to sustain motivation across long projects, including how to celebrate victories but also how to quickly bounce-back from any obstacles that occur.

  • Avoid the Lake!

    Large programs are as much about bringing people, teams, and organizations together as much as it is about building and delivering technology. This talk is a brief overview of frequently overlooked steps in execution and proposes small changes to consider to significantly reduce friction during execution.

  • Iterating with a purpose

    In talk, we’ll be exploring what you need to think about when you start a new project. How do you decide and agree what your goals are and understand how you’ll measure their successes and failures.

  • Remote Inclusion in Distributed Engineering Teams

    Increasingly, companies in business centres like London are combining offshore with local developers. Maximising the effectiveness in a mixed team environment is therefore critical to business success.

  • Applying software engineering practices to improve people management

    As a new manager, your changed responsibility is not to build features, but to build systems to support the people building the features. It can be a challenge to figure out how to prioritise problems alongside the day to day pastoral care of your team.

  • Learning from incidents: from ‘what went wrong?’ to ‘what went right?’

    When things go wrong, we tend to focus on mistakes, miscalculations, and deficiencies in design. By limiting our investigations to the details of what went wrong, we ignore a far richer and more interesting source of learning: how things went right.