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.
-
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.
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
-
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
-
Content sponsored by Honeycomb
Why people are at the center of systems
Framing systems as both social and technical
Top Velocity videos
-
Running efficient, effective, and engaging retrospectives
Supercharging your team from one sprint to the next.
-
Taking risks in production
Being an engineer, we all have at least one common thread: We like to build things. That is why writing code and architecting platforms that scale for millions of customers is appealing.
-
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?
