In a recent LinkedIn post, 🌀 Luca Rossi challenges conventional metrics for software development speed, arguing that the true measure lies in the end-to-end delivery time experienced by the customer, not internal activity.
🌀 Luca Rossi begins by stating a core belief that speed and quality in software are not mutually exclusive. He posits that rapid shipping fosters a critical feedback loop, which in turn accelerates improvement and allows for quicker recovery from errors. This, he suggests, ultimately enhances both quality and stability.
“I have always believed there is no tradeoff between speed and quality in software. Shipping fast creates a tight feedback loop, which makes you improve faster and recover faster from mistakes.”
However, the crux of 🌀 Luca Rossi’s argument hinges on how speed is accurately measured. He contends that focusing on internal development activities like the number of commits, pull requests, or even deployments, provides a misleading picture of actual velocity. These metrics, while indicative of developer activity, do not necessarily translate to value delivered to the end-user.
Redefining Software Development Speed
🌀 Luca Rossi emphasizes that genuine speed in software development should be defined by the total time elapsed from the initial request for a feature or fix to its successful delivery and reception by the user. This holistic view, he argues, shifts the focus from internal processes to external impact.
“Speed is not the amount of commits you make, or the amount of PRs. It’s not even about the amount of deployments,” 🌀 Luca Rossi writes. “Speed ultimately means minimizing the wall-clock time between when someone asks for something, and when they get it.”
This perspective encourages teams to look beyond their internal workflows and consider the entire value stream. By focusing on the time it takes for a customer to receive what they need, organizations can identify bottlenecks and inefficiencies that might otherwise be overlooked when only tracking internal milestones.
The Customer’s Experience as the Ultimate Metric
The ultimate test of speed, according to 🌀 Luca Rossi, lies in the perception of those who use the software. He prompts readers to consider whether their customers would agree with their self-assessment of speed.
“It’s about what the outside world experiences. So, if you think you are fast, ask yourself: would your customers say the same?”
This customer-centric approach is vital for businesses aiming to remain competitive. In today’s market, the ability to respond quickly to customer needs and deliver value efficiently can be a significant differentiator. 🌀 Luca Rossi’s insights suggest that by aligning development speed metrics with customer experience, companies can build more responsive, agile, and ultimately, higher-quality software products.
🌀 Luca Rossi concludes his post by wishing readers a good start to the week, reinforcing a positive and collaborative approach to discussing these important software development principles.
📝 About This Content
This article is based on insights shared by 🌀 Luca Rossi on LinkedIn.
📅 Originally posted on January 12, 2026 | View original post on LinkedIn →