Velocity: Is It Really the Key to Faster Product Development?

In the fast-paced world of product development, time is often considered the most valuable asset. The need to bring products to market faster has given rise to a growing emphasis on development velocity. Companies are investing in tools, methods, and practices to make their development cycles shorter. But is engineering velocity – speed in a given direction – really the panacea it’s often made out to be? Is it even a valid metric? Let’s take a closer look.

What is Engineering Velocity?

Engineering velocity refers to the speed at which a product team completes work items, such as features, bug fixes, or other deliverables. It’s often measured in terms of story points, completed deliverables, or other similar units within a given time frame.

The intention behind tracking this metric is clear: it’s a way to quantify progress and, ostensibly, efficiency. However, the pursuit of velocity for its own sake can lead to some serious pitfalls.

The Fallacy of Velocity as a Metric

Velocity as a metric has many shortcomings that make it not only pointless but sometimes even detrimental when it comes to product development.

1. Quality vs. Quantity: By focusing solely on the speed of development, there’s a real danger that quality can suffer. Cutting corners to increase velocity may lead to more bugs, technical debt, and products that don’t meet the needs of the Folks That Matter™.
2. Misleading Measurement: Velocity is often tracked using arbitrary units, like story points, which can vary greatly between teams and even within a single team over time. This lack of standardisation makes velocity an unreliable metric for comparison or prediction.
3. False Sense of Progress: High velocity may give a sense of progress, but it doesn’t necessarily mean that the right things are being built. Teams may rush to complete tasks that don’t align with strategic goals or the needs of the Folks That Matter™, leading to wasted effort and resources.
4. Impact on Team Morale: Emphasising velocity may lead to unnecessary pressure and stress within product teams, affecting collaboration and creativity. This can result in burnout and ultimately slow down the delivery process.

An Alternative Approach: Needs over Velocity

The key to successful product development isn’t necessarily moving faster; it’s moving smarter. Here’s what organisations might choose to do instead:

• Focus on the Needs of the Folks That Matter™: Prioritise features and deliverables that best attend to the needs of the Folks That Matter™. Regularly gather feedback from these consitituencies to ensure that development efforts are aligned with folks’ real-world needs.
• Emphasise Quality: Building quality products will lead to satisfaction and loyalty. Invest in e.g. ZeeDee and continuous improvement to ensure that quality is never sacrificed for speed. (Interestlingly, it’s a little appreciated fact that speed increases in proportion to improvements in quality).
• Leverage Self-organisation: Implementing Auftragstaktik-derived practices can help teams adapt quickly to changing requirements and focus on delivering value incrementally. Emphasising collaboration, adaptability, trust, and continuous improvement can lead to accelerated product development and delivery.
• Encourage a Healthy Culture: Foster an environment where team members feel supported and empowered. Recognise that creativity and innovation often take time and wilt under an overbearing stress on speed.

Conclusion

Engineering velocity might seem like a logical solution for bringing products to market faster, but it’s not a one-size-fits-all metric. In many cases, it’s misleading, counterproductive, and even harmful. Instead, companies might choose the smarter path:focusing on attending t folks’ needs, delivering value, ensuring quality, embracing adaptability, and building a positive team culture. By adopting these principles, organisations can develop products that not only reach the market more quickly but also resonate with the Folks That Matter™, stand the test of time, and ultimately contribute to long-term success.