A homeless-services intake form rebuild uses eight-week iterations, and frontline caseworkers only see working software at the end of each cycle. What is the main drawback of that long cadence?
Select an answer to reveal the explanation.
Short Explanation
If you only taste the soup every two months, you burn a lot of ingredients before you know it needs salt. Long iterations push learning way out, so bad assumptions hang around. Shorter inspect-and-adapt loops catch that sooner.
Full Explanation
Iteration length trades off overhead against feedback speed. Very long cycles delay stakeholder review of working increments, allowing incorrect requirements or design choices to persist. CAPM depth emphasizes that a major con of overly long iterations is slower learning—not that Done disappears, standups become mandatory for eight weeks, or story points only work in one-day sprints.