Development Velocity

Or Azulay, Growth Product Manager, Nexar

Or provides tactics for velocity: • Simplify • Clarify & Excite • Run a Pre-Mortem • Prioritize Correctly • Identify Dependencies/Bottlenecks • Beat The Drum • Celebrate Speed of Execution • Hack Your Own Productivity

Chris Bell, Co-Founder, Knock

The first in moving step is to make sure you're talking to customers, trying to build the right solution for their problem, and ensuring those customers know about your product via distribution. After those steps are covered, you can focus on optimizing your development velocity by: 1. Using trunk-based development 2. Only shipping high quality product 3. Deploying without ceremony 4. Capturing changes in a changelog 5. Optimizing for developer autonomy

Smruti Patel, Engineering Manager, Stripe

Smruti defines engineering velocity "in terms of shipping software with precision, speed, quality and impact." She breaks the velocity debugging process down into: 1. Planning 2. Execution 3. Delivery.

Juan Pablo Buriticá, Head of Engineering, LatAm, Stripe

Juan advises teams to adopt metrics that measure engineering delivery: the phase that begins when code is committed and ends when code is running in production. Four effective metrics are delivery lead time, deployment frequency, mean time to restore, and change failure rate.