
Latest
-
New study suggests major productivity boost when using Cursor’s coding agent
Is this the massive productivity benefit we’ve been waiting for?
-
The unseen fixes that boost engineering performance
At the intersection of toil and operational risk lies “perilwork.”
-
In partnership with Uplevel
How to spot and unblock engineering bottlenecks
Learn how your team can identify and fix what’s really slowing them down.
-
In partnership with LaunchDarklyFrom code tsunami to controlled innovation: Launching software in the age of AI
How to harness the explosive speed of AI-driven development without losing control, compromising safety, or putting customer experience at risk.
Editor’s picks
Productivity isn’t always fast
It can often feel like we aren’t being productive unless we’re working at max speed. But slow productivity is here to subvert that idea.
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.
Maintain team performance during unexpected change
You’ll have to experience change management at least once in your career. Make sure your teams can maintain performance through it all.

Deadline: January 4, 2026
Call for Proposals for London 2026 is open!
Essential reading
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.
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 ??♀️
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.
More about Velocity
-
Using coaching to unlock the future of your distributed organization
Coaching tools and approaches for remote-first companies
-
Balancing delivery speed with engineering health
Keeping delivery times up without sacrificing quality
-
Why open source projects should embrace operational transparency
Communicating how your project operates will benefit everyone
-
Pandemic and purpose-built remote work are not the same thing
What we can learn from purpose-built remote companies
-
Seven ways to help your team connect when you’re apart
Building a sense of community in remote teams
Top Velocity videos
-
Designing effective OKRs
When they work well, OKRs have the potential to be a powerful tool that can clarify vision at all levels of the business, all while providing autonomy for smaller functions to set their own goals and objectives.
-
Strategies for Rapidly Pivoting to Remote Work
Over 74% of engineering teams now have team members who work remotely. And while remote work has the potential to bring many benefits, it also has unique points of tension that, if handled incorrectly, can damage the health of your team.
-
Building replicable dev environments with Docker
Maintaining different software environments to run multiple web projects is a time-consuming task. Have you ever returned to an old project, only to find that you have to reinstall older versions of software before even starting any work?
-
How performance is everyone’s job
As builders of the web, performance is our most important job, as it dictates a users happiness and willingness to use a product.
-
Adapting testing for engineers
Keeping up with a team of developers who release every day is a tough job, but someone’s got to do it! Gone are the long, relaxing days of manual testing for weeks on end. Here is how we are keeping the acceptance testing process at JUST EAT as lean as possible.
-
Dealing with culture divides on distributed teams
Having timezone issues, international flights, planning logistics, communication and dealing with different cultural norms, working with teams distributed across the world provides challenges to overcome and a great way to learn how to work in a different manner at times.
-
Working backwards from the customer
Amazon is built on top of fine grained services that have a strong ownership model – you build it, you run it. These services are created by small teams to make it very easy to innovate.
-
Creating processes that don’t impede autonomy
Many factors contribute to developer happiness. However, as engineers, we’re often singularly obsessed with the idea that our job satisfaction comes solely from solving only the most interesting technical challenges.

