Latest
-
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.
-
Content sponsored by Statsig
Unlock your engineering velocity with data
Breaking down the three phases of data maturity and how they help move your product forward.
-
Why you shouldn’t move fast and break things
It’s an oft-repeated motto within the industry – but a severely limited way to build good software.
-
Estimates as probabilities
This talk introduces a probability approach to estimations, aiming to transform delivery discussions into stress-free, trust-based conversations between tech teams and stakeholders.
Editor’s picks
Unleash impact using outcome-driven delivery
Delivering impact in today’s landscape is a loaded task.
Increase speed and reduce risk with these engineering strategies
Once upon a time…your product was small. And fast. How do you keep that feeling going?
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.
That’s a wrap for LeadDev Berlin 2024!
Watch all of the talk videos from an incredible two days with a digital pass.
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
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?
Overcoming security hurdles to push engineering velocity
How can you get your engineering teams to stop bypassing security requirements?
Keeping up momentum in remote teams
How can you increase your speed of delivery when managing remote engineering teams?
Moving quickly inside a large organization
Pablo Jablonski shares key learnings from building and shipping Spaces within Twitter, and how those learnings can be applied to any new team looking to move quickly within a larger organization.
Planning for success when scaling rapidly
Create goals, prioritize effectively, set expectations, and drive alignment.
That’s a wrap Berlin!
Catch-up on all the Lead Berlin 2024 talks with a digital pass.
More about Velocity
-
Debugging engineering velocity and leading high-performing teams
Looking beyond the speed of delivery to identify what’s really slowing your team down.
Top Velocity videos
-
Breaking down silos for better collaboration
Technology at Spotify is filled to the brim with talented, driven and passionate engineers, who together work to solve the challenges we face to reach our north star goals.
-
Driving architecture alignment across a fully-distributed engineering workforce
InVision started as a small startup several years ago with tens of engineers, small teams working independently as velocity was paramount. But as InVision grew to hundreds of engineers, all fully remote, we realized that this independence was actually slowing us down – teams resolving the same problems, inconsistent metrics, etc.
-
Crafting effective 1:1s for distributed engineering teams
Creating relationships with the individual humans on your distributed team is difficult since you rarely get to see them in person! But a team is much less likely to be effective and successful without a foundation of interpersonal relationships and trust.
-
Unlocking success: the components of high-performing teams
Do you have a great team & a great mission but don’t understand why the pace of delivery is so slow? Architecture & tech stack is only one part of the story.
-
Effective meeting facilitation techniques
We’ve all had that experience where we’ve planned the perfect discussion only to have it hijacked by a passionate side-person, lose focus halfway through, or produce the exact same takeaways as you had before you began the discussion.
-
Engaging your engineering team to achieve high performance faster
When bootstrapping new teams, they need to go through the standard process of forming, storming, norming and performing. And in the context of fast-growing companies, with their own level of uncertainty, how can we achieve high performance when teams and goals are constantly changing?
-
Taking a fresh look at setting objectives and key results for your engineering team
In 2013, Google famously published a leading reference for establishing Objectives and Key Results as a way to align teams and set short-term goals.
-
Guiding your engineering team to self-organisation
It’s all well and good for the agile manifesto to recommend self-organising teams, but what does that actually mean in practice? What’s the best way to do it, how far should you take it? Total anarchy is probably not the answer here… right?