Development Velocity at Early Startups
Early stage startups face unique challenges in achieving development velocity due to limited resources, lack of established processes, and uncertainty around product-market fit. However, by prioritizing customer feedback, focusing on core features, and leveraging agile methodologies, startups can accelerate their development velocity and gain a competitive advantage.
- How to Speed Up Execution: A Tutorial for Impatient PMs and Entrepreneurs
Or provides tactics for velocity: • Simplify - by finding ways to reduce the amount of information your team needs to know • Clarify & Excite - by providing your team with a clear understanding of the project's goals and how it will benefit them • Run a Pre-Mortem - to anticipate potential issues and plan for a smooth execution • Prioritize Correctly • Identify Dependencies/Bottlenecks • Beat The Drum • Celebrate Speed of Execution • Hack Your Own Productivity
- How we work: moving fast to ship customer value
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
Development Velocity at Scaling Companies
As companies grow, maintaining development velocity becomes increasingly challenging due to organizational complexity, technical debt, and competing priorities. To overcome these obstacles, scaling companies must prioritize communication and collaboration, invest in automation and tooling, and continuously evaluate and optimize their processes. By doing so, they can sustain high levels of development velocity and drive innovation.
- Debugging engineering velocity and leading high-performing teams
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.
- A primer on engineering delivery metrics
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.