Agilistas talk about “velocity” as if that is the metric that matters.
It isn’t. What matters is how long it takes to create a reliable software product — how long it takes to get from Point A to Point B.
“Agile Vehicle Turns on a Dime,
Gets Nowhere Fast”
If the teams so-called “velocity” is high, but they are doing donuts in the parking lot and changing direction daily, constantly throwing out and rewriting code because they did the simplest thing possible, thinking only for today and not for tomorrow, they will and do take longer than a team that adopts a think first, code second approach.
Understanding the problem leads to a better overall solution — even if it takes time to understand the problem.
Consider flying from LA to Tokyo. Pretty much, Tokyo is directly west of Los Angeles. So, the so called “Agile” team would “do the simplest thing” which is, to fly directly west.
A more thoughtful team would realize that it takes more time and fuel to fly directly west than it does to fly a so called “Great Circle Route”.
The earth is narrower at the poles. Therefore, it is faster to fly northwest, towards Alaska, where the earth is a smaller diamater, then fly southwest, over Hokkaido. This is the shortest path between two points on a sphere.
The XP team would never have thought to even investigate such a beast. Next time you fly internationally, be thankful your airline didn’t use an “Agile” process to do your route planning. It would have added hours to your flight, while saving the XP team a few hours of coding. YAGNI? LMAO
The tortoise is indeed faster than the hare.
Slow Down. Think First. Understand the Problem Thoroughly. Then Code, Neo.
The Agents think they are Agile — but you’re faster than that.